The Nixpkgs Core Team Announces Its Own Dissolution

Translated by a model; the original is in Russian.

· Linux and open source
After roughly ten months of work, the Nixpkgs core team has decided to disband, citing burnout and systemic governance problems within the project.

cover.svg

The core team of Nixpkgs — the package repository for the NixOS distribution and the Nix package manager — has announced that it is ceasing operations. The corresponding message on behalf of the team was posted by members going by the handles @alyssais and @emilazy on the community forum.

Over the roughly ten months of its existence, the team, by its own assessment, managed to reform the process of delegating committer rights and admit 19 new members, expand the capabilities of the bot that automatically merges changes, re-establish contact with GitHub and secure a sponsored migration to Enterprise Cloud, take part in the investigation of the GHSA-67f2-674w-6g63 vulnerability and its associated risks, and adopt an initial policy on automation and AI.

Why the team is leaving

The authors stress that the decision was prompted not by a single incident but by systemic problems that had built up over time. The role they had expected to be light and compatible with active technical work turned out to be nothing of the sort. About two weeks ago, the members concluded that stepping down was necessary for the sake of their own health. Finding new people proved impossible: only one person responded to the call, and keeping the team in working order became unfeasible.

The authors direct their main criticism at the higher body — the Steering Committee. In their words, the committee lacks the instinct for delegation envisioned by the project's “constitution,” while at the same time it is not engaged enough to handle matters at this level on its own. This resulted in the micromanagement of subordinate teams, a chronic shortage of clear communication, and uncertainty over whether the team was trusted to make decisions within its own area of responsibility. As a result, initiatives on GSoC, grants, AI policy, moderation, and the reform of the GitHub organization's owners all stalled.

Betting on consensus

The authors go out of their way to defend their governance model, which is built on high trust and the pursuit of consensus, contrasting it with majority voting at the top. As proof that it works, they point to the approval of the AI policy by people with diametrically opposed views.

At the same time, the message also voices a broader thought about the culture of the community: a general distrust of governance gives rise to a confrontational, “zero-sum-game” approach that only accelerates the burnout of those who try to engage in good faith. Such dynamics, the authors warn, reward those least inclined to listen and entrench the historical pattern of making decisions through deadlock and attrition.

Both members intend to scale back their involvement in Nixpkgs and do not plan to run for the Steering Committee, whose elections are due to take place shortly. The matters that were under their purview are left without a direct owner — the “last line of defense” is the committee itself. In the discussion under the post, other members of the community thanked the team for the work it had done and expressed regret over the burnout.


Source: Hacker News

Comments

Sign in, to comment.

  • No comments yet.