A formal process for proposing and reviewing substantial changes to the Nix ecosystem, including Nix and Nixpkgs.
Nix RFCs is the formal Request for Comments process for the Nix ecosystem. It is a structured mechanism for proposing, discussing, and approving substantial changes to Nix, Nixpkgs, and related projects. The process ensures that major modifications undergo community review and consensus before implementation.
Nix ecosystem contributors, maintainers, and community members who are proposing or reviewing significant changes to the language, package sets, or project interfaces.
It provides a transparent, community-driven governance model that prevents hasty changes and ensures broad stakeholder alignment. The shepherd team system and Final Comment Period offer balanced oversight while maintaining an open collaborative environment.
The Nix community RFCs
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The formal workflow from Draft to Merged ensures thorough design review and consensus, as detailed in the process diagram and lifecycle states, preventing hasty changes.
Each RFC is guided by a team of 3-4 community experts appointed by the Steering Committee, providing balanced decision-making and facilitating constructive discussion, as specified in the terminology.
With defined states like Final Comment Period and clear handling for inactive proposals, the lifecycle is openly documented, reducing ambiguity and fostering accountability.
RFCs serve as snapshots of decisions at a point in time, similar to Matrix Spec Proposals, preserving context for future reference rather than as permanent specifications.
The README note about decreased activity and transition to an on-demand workflow indicates that the process can become inactive, leading to delays or abandonment of proposals.
Requirements like shepherd team formation, unanimous decisions, and a mandatory 10-day Final Comment Period add significant time and coordination effort, slowing down innovation.
RFCs can be closed due to lack of interest if no shepherds volunteer, as described in the 'Can't Find Shepherds' section, making success reliant on community engagement.