forge vs gitolite (Re: CTI - Making a decision for glibc.)

[Alexandre Oliva]

On Feb  6, 2026, Florian Weimer <fweimer@redhat.com> wrote:

> * Alexandre Oliva via Overseers:
>> We're not doing our computing on Sourceware.  The services we're using
>> aren't SaaSS, to the best of my knowledge, they're publishing and
>> communication, which aren't our computing, so relying on a third party
>> for them doesn't affect our control over our computing.

> We have buildbots for post-commit CI on Sourceware.

Ugh.  That sucks.  Thanks for bringing this problem to my attention!

Can we please make it a priority to fix this?

Could we possibly run it on a machine under our control?  Even a rented
virtual machine would do.  Could we use OpenSSF money, or the GNU
Toolchain funds, to rent a VPS?  Could we use OpenSSF money to pay for
LF personnel to help us set it up and to maintain in, but in such a way
that it remains under our control?

Now, CI specifically doesn't even have to be our own computing.  If
someone else were to run it, and then share the results with us, that
would make it their computing, not ours.  It could even be multiple
"someone else"s, each targeting a different arch or something.  These
would be useful and valuable contributions to the project, without
making them SaaSS for us.


> The pre-commit CI through Patchwork has builders, too, but they do not
> run on Sourceware infrastructure AFAIK.

Could someone who knows please confirm whether or not this is indeed the
case?

-- 
Alexandre Oliva, happy hacker            https://blog.lx.oliva.nom.br/
Free Software Activist     FSFLA co-founder     GNU Toolchain Engineer
Learn the truth about Richard Stallman at https://stallmansupport.org/