Hi Andreas, On Wed, Sep 30, 2026 at 12:01:21PM +0200, Andreas K. Huettel wrote: > > things nobody will use or worse create a fork and split the community: > > Please stop that. > > And before you argue further, go into your git clone and compare > > * who is contributing how much code *recently* to glibc > * who is *recently* doing regular patch review > * and who is making loud noise on the mailing list > > This is what the decision should be based on.
I admit it is very unlikely I'll fork any project where my code contributions are just two patches a year. So sorry if you thought that was a silly threat, you are right. But I don't think decisions should be based on just the volume of code (that would skew toward corporate backed hackers and push out volunteers), nor that people who make the loudest noise should get the final say. But I do think it is a waste of time if you don't listen to everyone and try to get to consensus with the whole community. And that does includes the small time hackers, or someone who triages bugzilla, or someone who just reviews CVEs, or a GNU package maintainer, or the FSF or someone like me who admins some services that glibc uses. > Beyond that, my own opinion doesn't really count. Of course your opinion as Release Manager counts! My point was not the threat of a fork, but the threat of a broken community. Cheers, Mark
