Working together and gaining trust

[Mark Wielaard]

Hi,

On Sat, Feb 07, 2026 at 11:07:27PM -0300, Alexandre Oliva wrote:
> On Feb  7, 2026, "Frank Ch. Eigler" <fche@elastic.org> wrote:
> >> Could we possibly run it on a machine under our control?
> 
> > Who is the "us" you are talking about?
>
> [...]
> Sourceware, a separate entity, seems to be doing our computing under
> its control, instead of our doing our computing under our control.

Please stop this "us" versus "them". And this is not just directed at
you. You and Carlos are glibc GNU package maintainers that are
supposed to help us reach consensus as a community, but instead you
both are creating division by manufacturing crisis, branding some
people in the community as "them" as if they are actively working
against the community's goals. This is such bullshit. From both sides.

The Sourceware Project Leadership Committee is Frank Ch. Eigler, Ian
Kelling, Ian Lance Taylor, Tom Tromey, Jon Turney, Mark J. Wielaard
and Elena Zannoni. https://sourceware.org/mission.html#plc

Both of you know these people, they have been part of our community
for decades, their dedication to community and Free Software is well
known. You should be able to trust these people to make sure that the
community will always be in control of their own computing.

These people are us. They took up responsibility for the long term
sustainability and funding of our infrastructure. Providing services
to projects that their communities control collectively. And guiding
hosted projects to follow secure practices and new cyber security
regulations where appropriate. If you don't trust them personally then
you can rely on the Fiscal Sponsorhip Agreement they all signed with
the SFC. https://sourceware.org/Conservancy-Sourceware-FSA.pdf

It makes sure to explicitly list our purpose as supporting/hosting
Free Software communities and that we use (and publish) as free
software the services provided.

For things like builder CI and the Forge this means there are
repositories containing the whole setup, so that you cannot just
replicate the service locally, but also you can control what "compute"
it does for the community as a whole (they operate just like other
projects, your patches get reviewed first).
https://sourceware.org/cgit/builder/
https://forge.sourceware.org/forge/

Lets see if we can expand "us". Zoe is talking to the LF/OpenSSF right
now. Lets give her some credit for defining what is acceptable for the
FSF. What would your requirements be for the CTI charter to accept
them as "us"? In which way would you want the LF support to come? How
do you see the collaboration of LF with Sourceware? What kind of
services would you feel comfortable LF providing? And in what way?

Cheers,

Mark