Nixpkgs Core Team Dissolves, Leaving Governance Duties Without a Direct Owner

The Nixpkgs Core Team has disbanded after only 10 months, citing burnout, poor delegation, and persistent governance problems within NixOS.

The Nixpkgs Core Team officially disbanded about 10 months after its creation, with remaining members citing burnout, difficulties attracting new contributors, and ongoing governance problems within the wider NixOS project.

In an announcement on the NixOS Discourse forum, the team said what was meant to be a lightweight governance role, compatible with hands-on technical work, became much more demanding than expected.

The announcement said the situation had become unsustainable. The remaining members concluded about two weeks earlier that stepping down was necessary for their health. Previous attrition had already shown how difficult the workload was.

Attempts to replenish the group did little to improve the outlook. Only one person applied after a recent call for new members, and personal outreach received mixed responses. The team concluded recruiting enough people to maintain a healthy, sustainable structure was unlikely.

However, burnout is only part of the explanation given for the decision. A significant portion of the announcement is devoted to problems the Core Team says it experienced while working with the NixOS Steering Committee, the project’s top-level governance body.

“Our experience is that the Steering Committee as an institution lacks a native instinct for the delegation envisioned by the constitution, while also not being sufficiently engaged and cohesive to handle individual decisions at those levels itself.”

The departing team contends the Steering Committee has struggled with the delegation envisioned by the NixOS constitution. This led to unnecessary interference in delegated areas, poor communication, uncertainty over whether statements from individual members were personal or official, and slow responses to concerns.

More broadly, the team says the situation created uncertainty about whether it actually had the autonomy to make decisions within its assigned responsibilities.

Moreover, the announcement stressed that these were not isolated disagreements with one Steering Committee member. Instead, the Core Team describes them as systemic problems that persisted despite repeated attempts to discuss them.

The announcement also highlights a difference in decision-making philosophy between the two groups. The Core Team favored a consensus-oriented model that it says worked particularly well for resolving contentious issues, while the Steering Committee generally operates by majority vote.

Still, the Core Team says repeatedly stepping into difficult community disputes took its toll. It assesses that long-standing distrust of governance in parts of the NixOS community has encouraged a more confrontational approach to disagreements. This increases the risk of burnout among those trying to resolve conflicts through consultation and consensus.

Expectably, not everyone within NixOS leadership agrees with that assessment. Steering Committee member John Ericson publicly disputed the characterization of the committee as micromanaging the Core Team.

He said the Core Team had barely appeared on the Steering Committee’s agenda and described its approach toward the group as essentially one of delegating responsibility rather than interfering with it. He explicitly rejected the micromanagement accusation as “objectively false.”

Importantly, let’s make it clear: for users, none of this means that Nixpkgs itself is shutting down or that development of the NixOS package collection has stopped. The repository continues to be maintained by its large contributor community. What has disappeared is a dedicated governance layer responsible for handling a range of decisions and escalations related to Nixpkgs.

The Core Team says the areas previously under its jurisdiction currently have no direct owner, with the Steering Committee as the final backstop. The two remaining members plan to reduce their involvement with Nixpkgs and do not intend to run in the upcoming Steering Committee election.

Whether another structure eventually takes its place will now depend on how the project responds to those concerns and, potentially, on what changes emerge from the forthcoming Steering Committee election. For now, the experiment has ended much earlier than expected, as after only about 10 months, Nixpkgs lost its governance team.

Bobby Borisov

Bobby Borisov

Bobby, an editor-in-chief at Linuxiac, is a Linux professional with over 20 years of experience. With a strong focus on Linux and open-source software, he has worked as a Senior Linux System Administrator, Software Developer, and DevOps Engineer for small and large multinational companies.

One comment

  1. Anonymous

    Ongoing governance probs.
    All is said…

Leave a Reply

Your email address will not be published. Required fields are marked *