this post was submitted on 21 Apr 2024
2 points (75.0% liked)

FreeAssembly

75 readers
1 users here now

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 @[email protected])

founded 7 months ago
MODERATORS
 

this thread fucking sucks for me to have to post, but the linked open letter is an important read. none of the systemic issues pertaining to marginalized folks and commercial/military-industrial interests in the Nix community I’ve previously written about on TechTakes have been solved; in fact, they’ve gotten worse to the point where the Nix community moderation team is essentially in the process of quitting. that’s the beginning to an awful end for a project I like a whole lot.

even if you don’t give a fuck about Nix, the open letter is an important read because the toxicity, conflicts of interest, and underhanded tactics detailed in it are incredibly common in the open source space. this letter could have been written about a multitude of infamously toxic open source projects; Nix is lucky that it has marginalized folks involved who care about the direction of the project and want to make things better, but those people are actively leaving, after being burnt out by the toxic people and structures entrenched in Nix’s community. that’s a fucking tragedy.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 6 months ago

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.