https://discourse.nixos.org/t/much-ado-about-nothing/44236
Not directly related to this blog post but from NixOS discourse forum, a tl;dr from another person about the NixOS drama here :
If you’re looking for a TL;DR of the situation, here it is: Nix community had a governance crisis for years. While there has been progress on building explicit teams to govern the project, it continued to fundamentally rely on implicit authority and soft power Eelco Dolstra, as one of the biggest holders of this implicit authority and soft power, has continuously abused this authority to push his decisions, and to block decisions that he doesn’t like Crucially, he also used his implicit authority to block any progress on solving this governance crisis and establishing systems with explicit authority This has led uncountably many people to burn out over the issue, and culminated in writing an open letter to have Eelco resign from all formal positions in the project and take a 6 month break from any involvement in the community Eelco wrote a response that largely dismisses the issues brought up, and advertises his company’s community as a substitute for Nix community
We agree on that.
Nope.
CoC mean “Code of Conduct”. It dictates how the interperpersonal relations should be in the community, not the direction the project need to follow. Which means that if you make a request I should not answer with “fuck your request” but with some more appropriate “we have not the manpower/motivation/infrastructure/whatever reason to do it, but feel free to do it yourself and submit it for review” answer (that’s of course is a simple example, bear with me in this case) if I am not interested in your request or there are some real limitations.
True, but if you think that it is the CoC that produce this result, you are way wrong.
What produce this result is that people are willing to work on a feature even if they don’t need it and if there is enough request for that feature. If you are the only one person who ask for a feature you will get low priority even if you are deaf (just to keep up with your example).
What do you think you can do if I don’t want to work on your feature ? Use the CoC to compel me to do the work ? Do you think you can threaten me with a ban from the project ? Try it and you lose one developer (and probably others).
True, but it is simply the fact that the developers lowered the barrier to make a request on one side and on the other side someone made a good and motivated request.
The point is that this has nothing to do with the fact that a deaf person is in a leadership position.
Again, what you are asking for is to have a way to communicate with the developers and possibly a clear way that indicate how a request is handled.
But having a way for the community to communicate with the developers and the leadership of the project is not the same as having a CoC that mandate that the leadership must include members from minorities.
But in the end we are debating about nothing, the project was forked so I suppose that we just need to wait to see how it will end.