Introduction
On August 7, 2026, an announcement shook the community of developers and users of Nixpkgs: the Nixpkgs core team decided to disband. This decision, though unexpected, reflects internal and structural challenges that have made their role increasingly unsustainable. But what does this mean for the future of Nixpkgs and the many companies and developers relying on this open-source infrastructure?
Achievements of the Core Team
Before delving into the reasons for this dissolution, it's important to acknowledge the accomplishments of this team. Over the past ten months, the core team has successfully:
- Reformed the committer delegation process and onboarded 19 new contributors.
- Empowered maintainers by extending the merge bot's capabilities.
- Re-established contact with GitHub and secured a sponsored Enterprise Cloud upgrade.
- Actively participated in resolving security incidents like GHSA-67f2-674w-6g63.
- Established an initial automation and AI policy.
These efforts not only improved Nixpkgs' internal structure but also enhanced the project's security and efficiency.
Reasons for the Disbanding
Despite their successes, the core team found the role increasingly demanding, incompatible with active technical contributions. The lack of candidates to join the team and mixed responses to outreach efforts led to the conclusion that continuing as is was untenable.
The team also highlighted systemic issues with the Steering Committee, including:
- A tendency towards unnecessary micromanagement.
- Chronically poor communications, with confusion over who represented which position.
- Delays and insufficient responses to raised concerns.
These issues hindered initiatives such as coordination for Google Summer of Code, GitHub organization owner reforms, and AI policy development.
The Future of Nixpkgs
With a Steering Committee election imminent, the disbanding of the core team leaves a void in Nixpkgs governance. However, it also paves the way for a reevaluation of governance structures. The community will need to rethink its approach to avoid similar pitfalls in the future.
Companies using Nixpkgs should remain vigilant and actively engage in community discussions to positively influence the project's future direction.
Conclusion
The disbanding of the Nixpkgs core team is a reminder of the challenges inherent in managing large-scale open-source projects. For businesses and developers, it underscores the importance of community engagement and flexibility in adapting to changes. Let's discuss your project in 15 minutes to see how to adapt to this new era of Nixpkgs.