Page History

...

• Draft: This is the initial state of the RFC, before the author(s) have started the discussion and are still working on the proposal.
• Discussion: Once the [DISCUSS] email has been sent to the mailing list, the proposal should be transitioned to this state.
• Development: The deadline for comments on this RFC has passed and the authors have decided to go ahead with it. The work proposed by the RFC is being implemented right now.
• Active:  The RFC has been accepted and the implementation work is complete.
• Dropped: The authors have decided not to move forward with the changes proposed in this RFC. This might even happen after the proposal was approved.
• Superseded: The changes proposed on this RFC aren't in effect anymore, the document is kept for historical purposes and there is a new RFC that’s more current.

When a proposal transitions to Dropped or Superseded state it should be moved under the Older Specifications grouping.

Approval

The proposal should be posted with a date by which the author would like to see the approval decision to be made. How much time is given to comment depends on the size and complexity of the proposed changes. Anything between 1 week and 3 weeks seems like a reasonable timespan. Driving the actual decisions should follow the lazy majority approach. If a discussion is still going strong once it’s approaching the initially set date, the author(s) might consider extending the time for discussion. This should happen explicitly and be announced in the email that starts the [DISCUSS] thread.

...