From 7b2e5393e90aa3fa192b60c3da67a9cb5c9af01f Mon Sep 17 00:00:00 2001 From: zimbatm Date: Wed, 8 Mar 2017 19:53:55 +0000 Subject: [PATCH] Describe the process a bit better --- rfcs/0000-rfc-process.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/rfcs/0000-rfc-process.md b/rfcs/0000-rfc-process.md index 6bfa0ce..02d1b65 100644 --- a/rfcs/0000-rfc-process.md +++ b/rfcs/0000-rfc-process.md @@ -80,6 +80,12 @@ 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 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 +wider community review. And the review process happens. + +After the review process has settled a decision is taken by community vote, +with @edolstra as a BDFL that can override any decision. + Whomever merges the RFC should do the following: * Create a corresponding issue on the appropriate repo (NixOS/nix,