ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix navigation for RfCs

Browse source
This commit is contained in:
Fischlurch 2012-09-18 02:31:44 +02:00
parent 61e5a6a47b
commit d1558bbe95
3 changed files with 14 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/devel/rfc.txt
View file

@ -1,18 +1,19 @@
Design Process
==============
//Menu: include rfc
//Menu: include rfc_parked
//Menu: include rfc_final
//Menu: include rfc_pending
//Menu: include rfc_parked
//Menu: include rfc_dropped
//Menu: put child 'rfc_dropped' after 'rfc'
//Menu: put child 'rfc_dropped' after 'rfc_final'
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 link:rfc/index.html[RfC accepted] section,
All our RfC entries are filed here, either in the link:rfc_final/index.html[RfC accepted] section,
or as link:rfc_pending/index.html[pending RfC] or as link:rfc_dropped/index.html[RfC dropped].
* Every proposal starts out as _*Idea*_, allowing other people to review and comment on it, while still working out details.

7
doc/devel/rfc/index.txt
View file

@ -1,10 +1,13 @@
Design Proposal Pool
====================
//Menu: off
//Menu: discard
//Menu: sort children
-> read link:../rfc.html[more about Lumiera RfC] and the Design Process
This is the poll where all Design Proposals are stored.
This is the pool where all Design Proposals are stored.
According to the current state of each RfC (pending, final, dropped, parked),
there is also a symlink from the respective subdirectory to the actual document
stored here.

6
doc/devel/rfc_final/index.txt
View file

@ -6,6 +6,8 @@ Accepted Design Proposals
-> read link:../rfc.html[more about Lumiera RfC] and the Design Process
The RfC entries listed here where discussed, maybe modified and finally agreed upon
during some developers meeting in the past. So they represent design decisions taken.
The RfC entries listed here where discussed, modified and finally agreed upon
during some developers meeting in the past.
So they represent design decisions taken and can be considered binding.