August 7, 2026
Package manager, people mismanager
The Nixpkgs core team has disbanded
Nix loses its cleanup crew as commenters ask if the whole house is on fire
TLDR: The team overseeing a key part of Nix has disbanded, saying the role became unhealthy and leadership above them made progress painfully hard. Commenters turned it into a referendum on the whole community, with jokes about “dependency hell for humans” and blunt claims that nonstop drama drove people away.
The big news is simple: the volunteer team helping run Nixpkgs — a major part of the Nix software ecosystem — has quit, saying the job became too exhausting and messy to continue. But in the comments, people barely paused before turning this into a full-blown community autopsy. The loudest reaction wasn’t shock, it was "of course this happened". One confused outsider asked the most relatable question of all: will the software still get updates? That set the tone: regular people trying to figure out whether this is a boring committee change or a sign the kitchen is actively burning down.
And then came the hot takes. One commenter flat-out asked why the Nix community is such a "dumpster fire," while another delivered the line of the thread: Nix can solve dependency hell for computers, but apparently not for humans. Ouch. Others blamed recent elections, saying the wrong people got power and everyone saw disaster coming. Another longtime contributor pushed back on the official "systemic problem" framing, arguing the real issue is more recent: specific drama-causing personalities arrived, longtime contributors got worn down, and the vibe collapsed.
So yes, there’s real governance trouble here — disagreements over control, communication, and burnout — but the community reaction is the real spectacle: equal parts gallows humor, blame game, and anxious spectators asking whether the project still functions while the adults argue in the group chat
Key Points
- •The Nixpkgs core team announced it is disbanding after concluding the role was unsustainable and incompatible with members’ health and active technical contribution.
- •Over roughly 10 months, the team says it reformed the committer delegation process, onboarded 19 new committers, extended the merge bot, secured a GitHub Enterprise Cloud upgrade, handled security-related issues, and created an initial automation/AI policy.
- •The team says recruitment was insufficient to sustain the group, with only one active applicant responding to its call for new members.
- •The article argues that the Steering Committee’s delegation, communication, and coordination problems hindered the core team’s ability to operate effectively.
- •The team says its own consensus-based governance model produced constructive outcomes and points to strong approval of the initial automation/AI policy as evidence.