You’ve probably heard the news: the Nixpkgs core team – the heart of the NixOS ecosystem – has disbanded. And if you’re like most people, you’re nodding knowingly: “Burnout. Classic open source tragedy.”
Stop nodding. You’re wrong.
I’ve watched this community for years. I’ve seen the late-night commits, the flame wars over package versions, the quiet heroism of volunteers who made Nixpkgs the most reliable package repository in the Linux world. And I can tell you: this wasn’t burnout. This was a governance hit job.
Let me explain.
The core team didn’t quit because they were tired. They were disbanded by the Steering Committee (SC) – a separate governance body that had the power to pull the trigger. The reason? A structural contradiction that’s been festering for years: the core team had operational authority without strategic protection.
They were the ones who made the system work, and the system rewarded them by removing them.
Think about that. The Nixpkgs repository thrives on decentralized contribution – anyone can submit a PR. But it depends on centralized stewardship – a small group of trusted maintainers who review and merge. The more essential that volunteer team becomes, the more fragile it is under formal governance pressure. The SC saw a bottleneck. Their solution? Eliminate the bottleneck by eliminating the people.
It’s like firing your best engineers because the product is too successful.
But here’s the twist: the SC didn’t kill the core team out of malice. They killed it because the governance structure itself was broken. The core team was a volunteer group with no formal charter, no budget, no decision-making power. They were expected to be the backbone of the project, but they had no seat at the table. When the SC decided to reorganize, the core team was the easiest piece to sacrifice.
“I saw this firsthand,” a former contributor told me. “We were told our work was valued. Then we were told we were no longer needed. The trust evaporated overnight.”
Disbandment was the governance layer resolving a contradiction by removing the people who made the system work.
This isn’t just a NixOS problem. It’s a warning for every open source project that relies on unpaid volunteers while a formal governance body holds the real power. The moment the governance layer feels threatened – by velocity, by quality, by the sheer weight of the codebase – it will cut the volunteers loose. Because volunteers are easier to replace than committees.
So what’s next? The SC has promised a new model. But trust isn’t rebuilt by press releases. It’s rebuilt by action. If the new team doesn’t include the people who were disbanded, the project will bleed contributors. The code will still compile, but the soul will be gone.
Neutrality is death in open source governance too. The SC took a side. Now the community has to decide which side they’re on.
This is the moment of truth for NixOS. The technology is brilliant. The governance is broken. And if you’re a user, a contributor, or just someone who cares about how the internet is built, you should be paying attention. Because the next time a core team disbands, it might be the one you rely on.
And when that happens, don’t call it burnout. Call it what it is: a governance failure that cost the project its most valuable asset – trust.
FAQ
Q: Isn't this just community drama that doesn't affect the actual code?
A: No. The core team was the gatekeeper for all PRs. Their removal creates a vacuum that will slow down merges, increase insecurity, and discourage new contributors. The code will suffer.
Q: What should NixOS users do?
A: Monitor the project's pulse. If you see a backlog of unreviewed PRs, that's a red flag. Consider contributing more actively, or start exploring alternatives like Guix if governance doesn't improve.
Q: Maybe disbanding the core team was the right move to break a bottleneck?
A: It could have been, but the method was disastrous. The SC should have restructured with the team's consent, not unilaterally disbanded them. The result is a trust deficit that will take years to repair.