> without warning/notice
The whole thread was full of warnings. Warnings don't have to be individually tailored. Moderators are often developers too and have better things to do with their time than to give a non-contributor extreme benefit of doubt. Or even to have rigorous due process. Every second these people have to waste on this nonsense is time they're not fixing the next CVE.
Not sure you guys realize how arrogant, snobbish and elitist this comes across.
"Shut up and dribble you plebs! The Pros will handle this. This is Devs-only business!"
You *will* the support of the user base, if such important changes are just pushed through by a handful of ppl - while other changes (which you may not like) are filibustered for yearz.
And snarly sentiment a la "Good luck with your fork" just confirms this. Disappointing.
Are you aware that you *could* in fact become one of this handful of ppl, or not?
Wut? No, you can't just become a Core maintainer on your own. You first need permissions of others.
Even counting as a contributor requires other people to actually have your PR merged
And that is good, lest every bozo starts contributing code that may or may not work, or even wreak havoc. In other words, you need competence. Competence that you don't just attribute yourself with, but that is recognized by a group of people who have been showing high degrees of competence themselves. I.e. core maintainers.
And that is exactly the status quo.
I don't see what's difficult about this to understand.
