conv.

All stories

Nixpkgs core team disbands amid governance tensions

Two core team members step down, citing unsustainable workload and organizational friction within the Nix ecosystem.

Conversation activity · last 3 days peak 8/hr

Peak 8 items in one hour at Aug 7, 10 PM; 24 items over 3 days Aug 7, 9 PM — 2 itemsAug 7, 10 PM — 8 itemsAug 7, 11 PM — no itemsAug 8, 12 AM — no itemsAug 8, 1 AM — 1 itemAug 8, 2 AM — 1 itemAug 8, 3 AM — 2 itemsAug 8, 4 AM — no itemsAug 8, 5 AM — 1 itemAug 8, 6 AM — no itemsAug 8, 7 AM — no itemsAug 8, 8 AM — 1 itemAug 8, 9 AM — 1 itemAug 8, 10 AM — no itemsAug 8, 11 AM — no itemsAug 8, 12 PM — no itemsAug 8, 1 PM — 2 itemsAug 8, 2 PM — no itemsAug 8, 3 PM — 1 itemAug 8, 4 PM — 1 itemAug 8, 5 PM — no itemsAug 8, 6 PM — no itemsAug 8, 7 PM — no itemsAug 8, 8 PM — no itemsAug 8, 9 PM — no itemsAug 8, 10 PM — no itemsAug 8, 11 PM — no itemsAug 9, 12 AM — no itemsAug 9, 1 AM — no itemsAug 9, 2 AM — 1 itemAug 9, 3 AM — no itemsAug 9, 4 AM — no itemsAug 9, 5 AM — no itemsAug 9, 6 AM — no itemsAug 9, 7 AM — no itemsAug 9, 8 AM — 1 itemAug 9, 9 AM — no itemsAug 9, 10 AM — no itemsAug 9, 11 AM — 1 itemAug 9, 12 PM — no itemsAug 9, 1 PM — no itemsAug 9, 2 PM — no itemsAug 9, 3 PM — no itemsAug 9, 4 PM — no itemsAug 9, 5 PM — no itemsAug 9, 6 PM — no itemsAug 9, 7 PM — no itemsAug 9, 8 PM — no itemsAug 9, 9 PM — no itemsAug 9, 10 PM — no itemsAug 9, 11 PM — no itemsAug 10, 12 AM — no itemsAug 10, 1 AM — no itemsAug 10, 2 AM — no itemsAug 10, 3 AM — no itemsAug 10, 4 AM — no itemsAug 10, 5 AM — no itemsAug 10, 6 AM — no itemsAug 10, 7 AM — no itemsAug 10, 8 AM — no itemsAug 10, 9 AM — no itemsAug 10, 10 AM — no items 8 items · 10 PM
Aug 8Aug 9Aug 10

Summary, timeline and people extracted by Claude from 24 items across 2 sources · 22h ago. Quotes are verbatim.

The Nixpkgs core team has disbanded, with members explicitly stepping down and citing that the leadership role proved incompatible with active technical contribution. The departure reflects ongoing tensions between multiple governance bodies (Steering Committee, Foundation Board, Core Team) and volunteer burnout, though community members praise the transparency of the resignation.

  • Nixpkgs core team explicitly disbanded, citing the role as incompatible with active technical contribution despite original hopes it would be lightweight.
  • Community praised the transparency of the resignation, contrasting it with abandoned FOSS positions that fade silently.
  • Structural governance tensions between multiple bodies (Steering Committee, Foundation Board, Core Team) contributed to the decision, with observers comparing the dysfunction to bureaucratic gridlock.
  • The departure reflects a broader pattern of volunteer burnout in open-source projects with insufficient organizational clarity and excessive expectations.

How it unfolded

  1. Reaction Comparative project stability discussion

    Ongoing discussion compared Nix's governance turmoil unfavorably to Debian, with hayalci noting Debian has 'never been mass resignations or teams disbanding.'

  2. Analysis Burnout cycle identified

    Commenters identified a self-fulfilling cycle where individual contributors burn out before critical mass is reached, with phaer noting those who remain either face burnout or 'learn to live with the status quo.'

  3. Analysis Structural governance concerns emerge

    Discussion highlighted friction between multiple bodies (Steering Committee, Foundation Board, Core Team), with nemin drawing parallels to organizational dysfunction and noting Nix's 'bureaucracy around it always felt like something to avoid with a ten foot pole.'

  4. Reaction Community praise for transparency

    Commenters acknowledged the team's explicit step-down as commendable compared to abandoned FOSS positions, with viraptor noting: 'it's awesome to see when people acknowledge they can't commit to the role.'

  5. Report Story circulates on tech forums

    The news spread to Lobsters and Hacker News, where it garnered significant discussion (396 points on HN, 103 on Lobsters) about governance challenges in the Nix ecosystem.

  6. Event Core team disbandment announced

    The Nixpkgs core team officially disbanded, with the announcement posted to the NixOS Discourse forum. Members cited unsustainable workload and inability to balance the leadership role with active technical contribution.

What people are saying verbatim

“it has sadly not turned out to be the lightweight role compatible with active technical contribution that we had originally hoped it would be”

Nixpkgs core team, Project leadership · NixOS Discourse

“There being a Steering Committee, a Foundation Board, (until now) a Core Team, and probably other stuff I don't even know about, and these being in constant beef with each other really evokes the image of The Life of Brian in my mind.”

nemin, Lobsters commenter · Lobsters

“it's awesome to see when people acknowledge they can't commit to the role (or don't see the role as functioning well anymore) and point to the next official decision maker”

viraptor, Lobsters commenter · Lobsters

“Individual members who push things forward often burn out before reaching a critical mass, those who remain are either next in line for the burnout, or learn to live with the status quo and slowly start to normalise it.”

phaer, Lobsters commenter · Lobsters

“I'm glad they are open about it.”

cryptix, Lobsters commenter · Lobsters

Voices from the web unedited

  • There being a Steering Committee, a Foundation Board, (until now) a Core Team, and probably other stuff I don't even know about, and these being in constant beef with each other really evokes the image of The Life of Brian in my mind. Nix as a technology is astounding, but the bureaucracy around it always felt like something to avoid with a ten…

    neminnix2d ago52▲view on Lobsters ↗
  • There was a sweet spot in like 2024 when it seemed like everything was possible with Nix, but now it seems like everything “experimental” is permanently so (like flakes), packages I care about are not as fresh as I want, I have no mental recall for Nix commands…Meanwhile, my company is using Nix for everything heavily internally. Everyone gets…

    klodolphHacker News2d agoview on Hacker News ↗
  • While it's sad to see there were various issues that led to this, I'm at least happy that they explicitly stepped down. There are many abandoned projects and positions that just go quiet in both FOSS and corporations. (I'm guilty of this too) It's awesome to see when people acknowledge they can't commit to the role (or don't see the role as…

    viraptornix2d ago37▲view on Lobsters ↗
  • For anyone reading this and jumping to a broader conclusion: the Nixpkgs core team disbanding does not mean Nixpkgs or Nix is dying. It does mean that this particular structure was not sustainable, very important contributors burnt out and we need to do better, faster. We need to continue learning from this and continue building a stronger…

    ronefHacker News2d agoview on Hacker News ↗
  • The saddest thing about this perception is that's it a self-fulfilling one, at least to a degree. Individual members who push things forward often burn out before reaching a critical mass, those who remain are either next in line for the burnout, or learn to live with the status quo and slowly start to normalise it. Structured governance came very…

    phaernix2d ago17▲view on Lobsters ↗
  • “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.”This is an almost poetic description of micromanagement. I really like Nix and have been running it…

    stingraycharlesHacker News2d agoview on Hacker News ↗
  • I'm erring on the side of posting this due to long-running interest on lobste.rs in Nix and its success, at risk of low topicality due to it being a potentially contentious forum post and not a step-removed article about it.

    kevincnix2d ago17▲view on Lobsters ↗
  • I really don't think these issues are necessarily "systemic" in the sense that they've been ongoing for the last decade. I _was_ a long-time contributor until about two years ago when certain actors came into the community and started making a bunch of unnecessary drama. Since then I've seen some long-time friends in the community either slowly…

    aliasxneoHacker News2d agoview on Hacker News ↗
  • > it has sadly not turned out to be the lightweight role compatible with active technical contribution that we had originally hoped it would be I heard variants of this story from a lot of people wanting to become team leads in their companies, for example…. That being said, I’m glad they are open about it.

    cryptixnix2d ago8▲view on Lobsters ↗
  • I dunno about all this hullabaloo. I'm at https://nix.vegas/ having fun and using Nix.

    setheronHacker News2d agoview on Hacker News ↗