Nixpkgs core team dissolves, blaming Steering Committee dysfunction and burnout

The team that spent the past ten months leading day-to-day governance of Nixpkgs — the package collection behind NixOS — has stepped down and disbanded. Over its tenure it reworked the committer delegation process, added 19 new committers, extended the automated merge bot, restored a working relationship with GitHub (including a sponsored Enterprise Cloud upgrade), helped handle a security advisory, and pushed through an initial policy on automation and AI. Despite those wins, the members say the role never became the lightweight commitment they expected, and two weeks ago concluded that continuing was unsustainable for their health. Attrition and a near-total lack of interest in their recruitment call — just one active applicant — made keeping the team staffed untenable.

Much of the departing team’s statement is a pointed critique of the NixOS Steering Committee. They argue the SC neither trusts subordinate teams enough to delegate cleanly nor stays engaged enough to make those decisions itself, producing micromanagement, muddled communication about who speaks for whom, and slow or absent responses. The result, they say, was stalled progress on moderation, GitHub org-owner reform, grants, GSoC, and AI policy, plus persistent uncertainty over whether the team was actually trusted to act within its mandate. They frame this as a systemic problem rather than the fault of any individual, and contrast their own consensus-based model favorably against the SC’s majority-vote approach.

The members also tie the collapse to the broader culture around Nix governance, where deep community divides and a history of distrust have encouraged combative, zero-sum tactics that wear down leaders trying to engage in good faith. They stress the decision follows long-running patterns, not a single blow-up. With the team gone, its responsibilities now have no direct owner and fall back to the SC — which faces an imminent election — and neither departing member intends to run. The timing highlights how fragile volunteer-run governance can be in a large, contentious open-source project.