One Applicant
The Nixpkgs core team has disbanded. Ten months old, consensus-driven, genuinely productive — and gone, because the people on it were doing work that was eating them alive.
The detail that gets me is buried in the middle of the announcement: when they put out a call for new members, exactly one person applied.
One.
For a project that runs a good chunk of the world’s reproducible builds. For a team that onboarded 19 new committers, extended the merge bot, helped triage a security advisory, and wrote an automation/AI policy that people with “highly divergent views” actually agreed on. In a community famous for fighting about everything, that last one is a small miracle.
They listed their wins like a foreman handing over the keys. Then they explained why they’re leaving: the role was supposed to be “lightweight” and “compatible with active technical contribution.” Instead it became a health decision. Two weeks ago they concluded that stepping down was “necessary for our health.” That sentence is doing a lot of work. Nobody writes it unless the job has turned into a slow extraction of everything they liked about the work.
Their diagnosis of the structure above them is precise. The Steering Committee, they write, “lacks a native instinct for the delegation envisioned by the constitution,” while also not being “sufficiently engaged and cohesive” to handle decisions itself. Let me translate: it micromanages what it doesn’t understand and doesn’t decide what it should. The worst of both worlds — a committee that neither delegates nor leads. Just hovers.
Now the counterarguments, because they’re real.
First: the packages keep building. The maintainers stay on, individual contributions continue, the tree doesn’t rot overnight. True. But what dies is the coordination layer — the place escalations went, the place disputes got resolved, the place cross-cutting calls got made. That’s the unglamorous plumbing. You only notice it when it’s gone, and it’s gone. Both members are reducing their involvement. Neither will run for the Steering Committee. The most experienced people aren’t just leaving the team; they’re leaving the building.
Second: Nix governance has been a mess for years; maybe a ten-month-old team was just a failed experiment. Fair — young teams fail. But read the failure mode. It’s not Nix-specific. It’s the universal recipe of unpaid critical infrastructure plus zero-sum conflict plus no succession. The xz backdoor, Redis, log4j — same story, different package manager. The announcement even names the mechanism: combative tactics “may work to effect change despite a leadership vacuum,” but they burn out the people engaging in good faith — and “that outcome only rewards those who don’t care to listen.” The system isn’t broken by accident. It’s broken in a direction that rewards the loudest, and it converts everyone else into exiles.
Which brings me back to the one applicant. That’s the real number. That’s the supply curve for open source governance in 2026: everyone watches, one person raises a hand, and the people who raised theirs last time are now telling you it cost them their health.
Nix can rebuild any environment from source. It can’t rebuild the people who made the environment worth having. That was always the fragile part.
Sources: The Nixpkgs core team has disbanded (NixOS Discourse) · HN discussion · via The Brutalist Report