NixOS’ influence and importance at pushing Linux forward into the (previously) unexplored landscape of configuring your complete system through a single config file is undeniable. It’s been a wild ride, but it was well worth it.

And although it has only been relatively recently that it has lost its niche status, the recent influx of so-called ‘immutable’ distros springing up like mushrooms is undeniably linked to and inspired by NixOS.

However, unfortunately, while this should have been very exciting times for what’s yet to come, the recent drama surrounding the project has definitely tarnished how the project is perceived.

NixOS’ ideas will definitely live on regardless. But how do you envision NixOS’ own future? Any ETA’s for when this drama will end? Which lessons have we learned (so far) from this drama? Are there any winners as a result of this drama? Could something like this happen to any distro?

In case you’re out of the loop. Though, there’s a lot that has transpired since but which hasn’t been rigorously documented at a single place; like how 4 out of 5 NixOS board members have quit over the last 2 months or so.

  • bsergay@discuss.onlineOP
    2·
    4 months ago

    Thank you for your input! I would love to read more on this. Do you happen to know a good source wherein Eelco Dolstra’s leadership is discussed (as fair as possible)?

    • BitSound@lemmy.world
      2·
      4 months ago

      Unfortunately there isn’t one easy source that I’ve found. This is based on reading the stuff you linked to, as well as discourse/matrix discussions linked to from those sources. I compare it mentally to Guido van Rossum as BDFL of Python (though not any longer). He did a much better job of communicating expectations, like here

      It made some people unhappy that there was no Python 2.8, but everybody knew what was happening. The core Python team also wasn’t surprised by that announcement, unlike with stuff like Anduril or flakes for the nix devs.

      There was also a failure to communicate with stuff like the PR that would switch to Meson. The PR author should have known if Eelco broadly agreed with it before opening it. If there was a process that the PR author just ignored, the PR should have been closed with “Follow this process and try again”. That process can be as simple as “See if Eelco likes it”, since he was BDFL, but the process needs to be very clear to everyone.