2010-11-16 04:55:46 +01:00
|
|
|
Design Process
|
|
|
|
|
==============
|
|
|
|
|
|
2012-10-07 08:06:30 +02:00
|
|
|
//Menu: include rfc
|
2012-09-18 02:31:44 +02:00
|
|
|
//Menu: include rfc_final
|
2011-02-27 21:42:12 +01:00
|
|
|
//Menu: include rfc_pending
|
2012-09-18 02:31:44 +02:00
|
|
|
//Menu: include rfc_parked
|
2011-02-27 21:42:12 +01:00
|
|
|
//Menu: include rfc_dropped
|
|
|
|
|
|
2012-09-18 02:31:44 +02:00
|
|
|
//Menu: put child 'rfc_dropped' after 'rfc_final'
|
2012-10-07 08:06:30 +02:00
|
|
|
//Menu: attach child 'rfc'
|
2012-09-18 02:31:44 +02:00
|
|
|
|
2011-02-27 21:42:12 +01:00
|
|
|
|
2011-02-12 19:36:09 +01:00
|
|
|
How it Works
|
|
|
|
|
------------
|
2011-04-14 19:22:04 +02:00
|
|
|
Design Process entries (Request for Comment) can be created by anyone.
|
2011-02-27 21:42:12 +01:00
|
|
|
Each entry goes through several stages until it's accepted (or rejected).
|
2012-09-18 02:31:44 +02:00
|
|
|
All our RfC entries are filed here, either in the link:rfc_final/index.html[RfC accepted] section,
|
2011-02-27 21:42:12 +01:00
|
|
|
or as link:rfc_pending/index.html[pending RfC] or as link:rfc_dropped/index.html[RfC dropped].
|
2011-02-12 19:36:09 +01:00
|
|
|
|
|
|
|
|
* Every proposal starts out as _*Idea*_, allowing other people to review and comment on it, while still working out details.
|
2011-02-27 21:42:12 +01:00
|
|
|
* 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.
|
2011-02-12 19:36:09 +01:00
|
|
|
* We decide on some proposals to talk about that another time, these get a _*Parked*_ state.
|
2011-02-27 21:42:12 +01:00
|
|
|
* At some point we may decide that a _*Draft*_ becomes a _*Final*_.
|
|
|
|
|
Usually, this happens in our link:/devs-vault/meeting/index.html[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
|
|
|
|
|
---------------------------------
|
|
|
|
|
CAUTION: to be written
|
2011-02-12 19:36:09 +01:00
|
|
|
|
2011-02-27 21:42:12 +01:00
|
|
|
Handling of RfC entries in practice
|
|
|
|
|
-----------------------------------
|
2011-02-12 19:36:09 +01:00
|
|
|
|
2011-02-27 21:42:12 +01:00
|
|
|
.Adding a new Proposal:
|
|
|
|
|
. 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.
|
2011-04-14 19:22:04 +02:00
|
|
|
. Use the './admin/rfc.sh' helper script to maintain the RFC's. Check out its link:../technical/infra/rfcsh.html[documentation].
|
2011-02-12 19:36:09 +01:00
|
|
|
|
2010-11-16 04:55:46 +01:00
|
|
|
|
