(uncharitably paraphrased) “No we're not attempting to take over the project” and later “join our discord where we are attempting to take over the project”.
@samueldr The discord link is completely tonedeaf and detracts from the message.
What stood out to me was: Fourth, the NixOS Foundation in no way controls or governs the Nix community, which has, since its inception, demonstrated its ability to self-govern very well.
This used to be true until it got involved with NixCon.
Maybe it should just go back to its core responsibility of managing the infrastructure?
@samueldr Can confirm "Second, I am just one member of the five-member Nix team and hold no more formal authority than the others in determining the direction of the team."
We respect each member's input, and obviously Eelco has brought a lot of experience.
@Di4na@samueldr
Would you ignore or listen to the most experienced developer on the team?
I you may overestimate the quality of the notes, as well as the time we have available, and underestimate the tech debt and the time that is needed to become familiar with a code base with such highly specific requirements as well as low level aspects. At a volunteer pace.
Nixpkgs got rid of the final bit of DocBook tooling.
It's a bit sad for scriptability actually, because I have yet to bring back the options table of contents...
I might redo it, in Nixpkgs this time, after the markdown anchor support is merged.
I see a problematic tendency in the #nixos ecosystem. The bad discoverability and loose typing of Nix pushes people into relying on the module system for more and more things.
Sadly the module system is a very questionable ad-hoc solution because it breaks laziness. I hope we find a better solution than introducing this big amount of complexity into all our code.