1 |
============================================================= |
============================================================= |
2 |
PEG 201: META: PEG format |
PEG 201: META: PEG format and process |
3 |
============================================================= |
============================================================= |
4 |
|
|
5 |
:Authors: Tuomas Lukka |
:Authors: Tuomas Lukka |
36 |
|
|
37 |
- Do we need the Scope and Type fields? |
- Do we need the Scope and Type fields? |
38 |
|
|
39 |
|
Process |
40 |
|
------- |
41 |
|
|
42 |
|
Anyone may start a new PEG in the Incomplete state (becoming |
43 |
|
one of the PEG's authors). The authors have control over the contents of the PEG. |
44 |
|
|
45 |
|
When the PEG seems ready for review, it should be made Current and |
46 |
|
posted to gzz-dev. At this point, the PEG may still be edited |
47 |
|
in response to comments from the list. |
48 |
|
|
49 |
|
At some point after this, the architect (tjl) will make a decision |
50 |
|
to either accept, force revision, declare rejected, or declare |
51 |
|
irrelevant (e.g. other PEGs superceded the current one). No-one |
52 |
|
else may change the status of the PEGs to any of these categories. |
53 |
|
|
54 |
|
If the PEG was accepted, rejected or declared irrelevant, it may not |
55 |
|
be edited any more, except for the architect declaring it implemented or |
56 |
|
partly implemented. |
57 |
|
|
58 |
|
A PEG int the Revising state is editable by the authors, similarly to |
59 |
|
an incomplete PEG. |
60 |
|
|
61 |
|
|
62 |
|
|
63 |
Names |
Names |
64 |
----- |
----- |
65 |
|
|
99 |
Authors |
Authors |
100 |
Comma-separated list of author names or handles |
Comma-separated list of author names or handles |
101 |
|
|
|
Stakeholders |
|
|
Comma-separated list of stakeholder names or handles |
|
|
|
|
102 |
Date |
Date |
103 |
CVS date tag |
CVS date tag |
104 |
|
|
108 |
Status |
Status |
109 |
The PEG status |
The PEG status |
110 |
|
|
111 |
Date-Created |
and may **optionally** also contain the following fields: |
112 |
The date when the PEG was created, for sorting |
|
113 |
|
Stakeholders |
114 |
|
Comma-separated list of stakeholder names or handles |
115 |
|
|
116 |
Scope |
Scope |
117 |
How large the effects of this PEG are: |
How large the effects of this PEG are: |
128 |
Type |
Type |
129 |
The type of the PEG |
The type of the PEG |
130 |
|
|
131 |
|
META |
132 |
|
PEG about PEGs |
133 |
|
Policy |
134 |
|
Setting goals, overall ideas; e.g. ``styled_text--benja`` |
135 |
Architecture |
Architecture |
136 |
Large-scale architecture |
Architectural changes; e.g. ``1005`` |
137 |
Feature |
Feature |
138 |
A new feature |
A new feature; e.g. ``vobcoorder_isactive--tjl`` |
139 |
Interface |
Interface |
140 |
An adjustment of one or more interfaces |
An adjustment of one or more interfaces; e.g. ``1017`` |
141 |
Implementation |
Implementation |
142 |
An adjustment of how an implementation does something |
An adjustment of how an implementation does something |
143 |
|
|