nixos/rfcs
1
0
Fork 0
mirror of https://github.com/NixOS/rfcs.git synced 2025-11-08 19:46:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Refine description of the process

Browse source
This commit is contained in:
zimbatm 2017-03-11 19:20:50 +00:00
parent fb723ea242
commit c28db71a17
1 changed files with 9 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

15
rfcs/0000-rfc-process.md
View file

@ -78,11 +78,14 @@ At this point, the person submitting the RFC should find at least one "co-author
that will help them bring the RFC to completion. The goal is to improve the that will help them bring the RFC to completion. The goal is to improve the
chances that the RFC is both desired and likely to be implemented. chances that the RFC is both desired and likely to be implemented.
Once the author is happy with the state of the RFC, he tells it's ready for Once the author is happy with the state of the RFC, she/he should seek for
wider community review. And the review process happens. wider community review by stating the readyness of the work. Advertisement on
the mailing-list and IRC is an acceptable way of doing that.
After the review process has settled a decision is taken by community vote, After a number of rounds of review the discussion should settle and a general
with @edolstra as a BDFL that can override any decision. consensus should emerge. This bit is left intentionnaly vague and should be
refined in the future. We don't have a technical commitee so controversial
changes will be rejected by default.
Whoever merges the RFC should do the following: Whoever merges the RFC should do the following:
@ -93,8 +96,8 @@ Whoever merges the RFC should do the following:
* Commit everything. * Commit everything.
Once an RFC becomes active then authors may implement it and submit the Once an RFC becomes active then authors may implement it and submit the
feature as a pull request to the Nix or nixpkgs repo. An 'active' RFC is not a feature as a pull request to the Nix or nixpkgs repo. An 'accepted' RFC is not
rubber stamp, and in particular still does not mean the feature will a rubber stamp, and in particular still does not mean the feature will
ultimately be merged; it does mean that in principle all the major ultimately be merged; it does mean that in principle all the major
stakeholders have agreed to the feature and are amenable to merging it. stakeholders have agreed to the feature and are amenable to merging it.