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

Alexandre Oliva oliva@gnu.org
Mon Feb 9 17:35:34 GMT 2026


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

> because it requires us to make a determination who is
> part of the glibc community and who is not.  I would prefer if it didn't
> come to that.

Your wish is granted.  There's no such need, as far as SaaSS is
concerned.  I wonder where this notion even comes from.  Surely I've
failed in communicating the concept of SaaSS, or in overriding other
preconceived notions, but I wish I could at least get to understand how
that came to be so that this misconception can be avoided and corrected.


It matters not at all whether someone is a member of a community, to
determine whether the community's computing is done as SaaSS.

If we were to outsource our community computing to you (an active
member), me (an inactive member), or any random third party out there
(who's never been a member), so that the one controlling the computing
is the person running it, rather than the community through its
governance structure, then it is SaaSS.

Whereas if the community computing takes place under control of the
community, so that its autonomy is not curtailed by the person who
carries out the computing on our behalf, then it is not SaaSS.

-- 
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/


More information about the Libc-alpha mailing list