20
an open letter to the NixOS foundation
(save-nix-together.org)
this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.
in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.
some posting guidelines apply in addition to the typical awful.systems stuff:
(logo credit, with modifications by @dgerard@awful.systems)
Eelco posted another non-apology and stepped down from the NixOS Foundation board. here’s the Aux take on it which I think has a bit more value than the original post alone did.
in essence: this is a good step, but it’s important to remember that Eelco and friends have made concessions like this in the past, and it hasn’t mattered to their (informal but very real) entrenched positions of power. specifically, Eelco hasn’t stepped down from the Nix evaluator team or promised he’d change any of his behavior there (and the evaluator is key to Nix, and to commercializing the project against the community’s wishes), and there’s no clarity on how the Nix governance changes will impact bad actors (which specifically includes Anduril). there’s still a very good place for Aux and any other Nix fork to exist as long as Eelco and company haven’t committed to taking actions that will remedy the most crucially broken parts of the Nix community.
There's some bitter irony to the fact that I've been getting nonstop notices about commits to the infamous "lazy trees" branch, the thing that is supposed to make flakes usable with monorepos (but in practice has yet to do so). Watching those notifications the last couple of days has told me all I needed to know.
oops all eelco and he really ain’t doing much in these commits, is he? between that and the recent commits to the Nix evaluator it’s pretty obvious he’s keeping near-exclusive control over what gets into the evaluator and how it’s developed
it’s very likely that Eelco and Determinate Systems have employed an old strikebreaking technique: they’ve agreed to concessions that don’t inconvenience them and weren’t really what was demanded. Eelco has lost a board position he didn’t want, but maintains a position that’ll ensure he and his friends can commercialize improvements to Nix by controlling what goes into the evaluator, ensuring that only Determinate Systems can implement an improved version of Nix with a working version of flakes.