@monsieuricon
That 50% is a little skewed. It's the people who are already familiar and using this system.
Maybe if you migrate to a better process, the number of new contributers turn that 50% to a way higher ratio?! Maybe.
@monsieuricon I suggest we get the maintainers together in two teams and fight to the death to resolve the debate once and for all. In the mean time I’m thinking about the same problems for Yocto (handily, also on LF infra) so I’m following your account closely!
@monsieuricon aye, I’ve been in enough of these arguments to have started towards the opinion that at some point the maintainer just has to pick and everyone else deals with it.
@monsieuricon although surely a self-hosted open source forge thing mitigates some of the fears of the modern? There are several options.
@monsieuricon it's truly bizarre to see LF argue in favor of moving to centralized forges after SFC's Give Up GitHub initiative last year, wow
@monsieuricon as an occasional kernel contributor, b4 has been by far the best tooling improvement in 2023 for me. Thanks for making it!
@drewdevault @gregkh @monsieuricon A friend of mine has been making this argument for a long time.
Many subsystems already operate this way and it works fine. git is distributed, after all.
I know this wasn't the point you were making - nor my friend, but one can obviously take the sourcehut model as well. Forge as a ~frontend to MLs can help a lot.