The Nixpkgs core team has disbanded after ten months

A ten-month experiment ends

On August 7, 2026, a NixOS contributor writing as qyliss announced on the NixOS Discourse that the Nixpkgs core team has decided to disband. The team was formed roughly ten months earlier to lead "bottom-up, consensus-focused governance" for Nixpkgs, the package collection at the heart of the Nix ecosystem.

What the team accomplished

In its farewell post, the team lists an unusual set of achievements for a volunteer body: reforming the committer delegation process and onboarding 19 new committers, extending the merge bot to give maintainers more authority, re-establishing contact with GitHub and securing a sponsored Enterprise Cloud upgrade, helping triage advisory GHSA-67f2-674w-6g63 and track the GitHub security risks it exposed, and establishing an initial policy on automation and AI. The team also resolved many incidents that were escalated to it.

Why it stepped down

The role, the post says, never became the "lightweight" job compatible with active technical contribution that members had hoped for; two weeks before the announcement the team concluded that stepping down was necessary for its health. Attrition had already thinned the group, only one person answered the call for new members, and targeted outreach met a mixed response. With a Steering Committee election due imminently, the team judged it untenable to recruit enough people to keep things healthy.

A critique of the Steering Committee

Much of the post targets the Steering Committee itself. The team argues that the committee lacks "a native instinct for the delegation envisioned by the constitution" and is not sufficiently engaged or cohesive to take decisions at the level of individual teams. It describes unnecessary micromanagement, chronically poor communication, unclear signals about when members speak for themselves or for the committee, and matters arriving with the desired outcome already attached. Coordination on GSoC, grants and AI policy suffered, work on moderation and ownership of the GitHub organisation moved slowly, and teams remained uncertain whether they were trusted to decide within their remit. The team stresses that this is a systemic problem rather than the fault of any single member.