Proposals for enhancing Navidoc
PEGs should use the python reStructuredText markup language. Quick reference could be handy.
Pegboard
| Status | Name | Topic | Authors | Stakeholders | Files |
|---|---|---|---|---|---|
| Current | pegboard_format | PEG format and process | tjl | humppake | |
| Incomplete | structured_text | Paragraphs and other text structure in Gzz | benja | ||
| Incomplete | tests_output_cleanup | Cleaning Tests' Output | vegai | ||
| Accepted | bug_test_rst | Marking failing tests to use ReST | benja | ||
| Implemented | bug_test | Handling bugs | tjl |
Explanation of table:
- Status
The current status of the PEG.
- current
- Currently under active consideration for accepting or rejecting.
- revising
- After being rejected, being revised for another round.
- incomplete
- Not yet being considered; details still being worked out by author and stakeholders.
- undefined
- Status is not yet defined, or peg's syntax is broken.
- accepted
- Accepted for implementing.
- implemented
- The changes are currently in main CVS. This PEG is now frozen, no changes should be made to it any more.
- rejected
- Rejected through peer review in the consensus process. Can be revived by being revised.
- irrelevant
- seems to be superseded by later PEGs.
- Topic
- A brief description of the main purpose of the PEG.
- Authors
- The author(s) (owner[s]) of the PEG; only this person can edit the main text of the PEG.
- Stakeholders
- The people who consider this PEG important for their work and need to have their views represented. For instance, users of an API being considered, the designer of the parts that now require changing etc. Feel free to add yourself if you consider the change important.
- Files
- All files related with PEG.