How it Works
Design Process entries (Request for Comment) can be created by anyone. Each entry goes through several stages until it’s accepted (or rejected). All our RfC entries are filed here, either in the RfC accepted section, or as pending RfC or as RfC dropped.
-
Every proposal starts out as *Idea*, allowing other people to review and comment on it, while still working out details.
-
When the Idea is in a proper shape and worked out in most details it becomes a *Draft*. This Draft need to be carefully reviewed, commented, perhaps corrected and rated by the other Developers.
-
We decide on some proposals to talk about that another time, these get a *Parked* state.
-
At some point we may decide that a *Draft* becomes a *Final*. Usually, this happens in our monthly developers meetings.
-
Sometimes proposals will become dropped for some reason, this is indicated by changing their state to *Dropped*, they still stay in the system for further reference.
Generally you should refrain from editing someone others proposals (except for typo and grammar fixes) when this is not acknowledged with the original author. Rather only add comments to the pages and please care to sign your comments in order to make it easier to find out who is the contact person for some note.
What qualifies as an RfC proposal
|
to be written |
Handling of RfC entries in practice
-
Check if there is no similar proposal below! If yes, contact it’s author and contribute to that one.
-
Think of a good/descriptive Name-ID for the Proposal. It will be used to create a RfC sub-page, so no embedded spaces please.
-
Use the ./admin/rfc.sh helper script to maintain the RFC’s. Check out its documentation.