Much ado about "nothing" - Xe Iaso
xeiaso.net

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
  • gian English
    -1•21 days ago

    I think people like you really don’t understand what OSS software is.

    What you don’t understand is that OSS let you do what you want with the software I (an possibly others) created but not let you to dictate to me how I must run the project or what direction the project need to go.
    We can discuss of course, and maybe sometimes I agree with you and sometimes not (and the contrary) but in the end I am the maintainer so I have the last word.

    So no, if I create an OSS project and have a vision for it, if you don’t agree I am fully entaitled to say “ok, just make your own, fork mine if you like” to you.

    • verassol
      1•21 days ago

      I guess it can be simple like that when you are the maintainer. It is definetly not as simple when there are many of them. Of course you can run it like that and many do, but the whole mentality is pretty limited.

      My statement is not that you have to do whatever anyone asks in your project that you maintain. My statement is that a community that contributes towards a project has a say in it. You might want to ignore it, handle it BDFL-style, politely and cynically decline, whatever.

      Not really about what is the absolute correct answer. Our values are clearly different. More like what I believe works best in the long term.

      • gian English
        2•21 days ago

        I guess it can be simple like that when you are the maintainer. It is definetly not as simple when there are many of them. Of course you can run it like that and many do, but the whole mentality is pretty limited.

        Why limited ?. In the end I am pursuing my vision for the project.

        Not really about what is the absolute correct answer. Our values are clearly different. More like what I believe works best in the long term.

        I just acknowledge that at some point the vision of the author(s) and the vision of the community (or part of it) can differ and that at this point it is better for everyone to follow their vision.

        • verassol
          1•21 days ago

          If pursuing your own vision is the sole purpose intended, it would not be limited at all.