| … | |
… | |
| 117 | injected into the Gentoo Linux development work flow with an enhancement "bug" |
117 | injected into the Gentoo Linux development work flow with an enhancement "bug" |
| 118 | submitted to the Gentoo Linux bugzilla <a class="footnote-reference" href="#bugs" id="id5" name="id5">[6]</a>.</p> |
118 | submitted to the Gentoo Linux bugzilla <a class="footnote-reference" href="#bugs" id="id5" name="id5">[6]</a>.</p> |
| 119 | <p>The GLEP champion then emails the GLEP editors <<a class="reference" href="mailto:glep@gentoo.org">glep@gentoo.org</a>> with a |
119 | <p>The GLEP champion then emails the GLEP editors <<a class="reference" href="mailto:glep@gentoo.org">glep@gentoo.org</a>> with a |
| 120 | proposed title and a rough, but fleshed out, draft of the GLEP. This draft |
120 | proposed title and a rough, but fleshed out, draft of the GLEP. This draft |
| 121 | must be written in GLEP style as described below.</p> |
121 | must be written in GLEP style as described below.</p> |
| 122 | <p>If the GLEP editor approves, he will assign the GLEP a number, label it |
122 | <p>If the GLEP editor accepts the GLEP, he will assign the GLEP a number, label |
| 123 | as Standards Track (a better name would be nice here -- suggestions?) |
123 | it as Standards Track (a better name would be nice here -- suggestions?) or |
| 124 | or Informational, give it status "Draft", and |
124 | Informational, give it status "Draft", and create and check-in the initial |
| 125 | create and check-in the initial draft of the GLEP. The GLEP editors will |
125 | draft of the GLEP. The GLEP editors will not unreasonably deny a GLEP. |
| 126 | not unreasonably deny a GLEP. Reasons for denying GLEP status include |
126 | Reasons for denying GLEP status include duplication of effort, being |
| 127 | duplication of effort, being technically unsound, not providing proper |
127 | technically unsound, not providing proper motivation or addressing backwards |
| 128 | motivation or addressing backwards compatibility, or not in keeping |
128 | compatibility, or not in keeping with Gentoo Linux philosophy.</p> |
| 129 | with Gentoo Linux philosophy.</p> |
|
|
| 130 | <p>If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the |
129 | <p>If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the |
| 131 | <a class="reference" href="mailto:gentoo-dev@gentoo.org">gentoo-dev@gentoo.org</a> mailing list to help flesh it out, gain feedback and |
130 | <a class="reference" href="mailto:gentoo-dev@gentoo.org">gentoo-dev@gentoo.org</a> mailing list to help flesh it out, gain feedback and |
| 132 | consensus from the community at large, and improve the GLEP for re-submission.</p> |
131 | consensus from the community at large, and improve the GLEP for re-submission.</p> |
| 133 | <p>The author of the GLEP is then responsible for posting the GLEP to the |
132 | <p>The author of the GLEP is then responsible for posting the GLEP to the |
| 134 | gentoo-dev mailing list and to the Gentoo Linux forums <a class="footnote-reference" href="#forums" id="id6" name="id6">[7]</a>, and |
133 | gentoo-dev mailing list and to the Gentoo Linux forums <a class="footnote-reference" href="#forums" id="id6" name="id6">[7]</a>, and |
| … | |
… | |
| 148 | include setting up a specific forums thread for the topic, having the GLEP |
147 | include setting up a specific forums thread for the topic, having the GLEP |
| 149 | author accept private comments in the early design phases, etc. GLEP authors |
148 | author accept private comments in the early design phases, etc. GLEP authors |
| 150 | should use their discretion here.</p> |
149 | should use their discretion here.</p> |
| 151 | <p>Once the authors have completed a GLEP, they must inform the GLEP editors that |
150 | <p>Once the authors have completed a GLEP, they must inform the GLEP editors that |
| 152 | it is ready for review. GLEPs are reviewed by the appropriate Gentoo |
151 | it is ready for review. GLEPs are reviewed by the appropriate Gentoo |
| 153 | Manager <a class="footnote-reference" href="#manager" id="id8" name="id8">[8]</a>, who may accept or reject a GLEP outright, or |
152 | Manager <a class="footnote-reference" href="#manager" id="id8" name="id8">[8]</a>, who may approve or reject a GLEP outright, or |
| 154 | send it back to the author(s) for revision. For a GLEP that is pre-determined |
153 | send it back to the author(s) for revision. For a GLEP that is pre-determined |
| 155 | to be acceptable (e.g., it is an obvious win as-is and/or its implementation |
154 | to be approvable (e.g., it is an obvious win as-is and/or its implementation |
| 156 | has already been checked in) the appropriate Gentoo Manager <a class="footnote-reference" href="#manager" id="id9" name="id9">[8]</a> |
155 | has already been checked in) the appropriate Gentoo Manager <a class="footnote-reference" href="#manager" id="id9" name="id9">[8]</a> |
| 157 | may also initiate a GLEP review, first notifying the GLEP author(s) and giving |
156 | may also initiate a GLEP review, first notifying the GLEP author(s) and giving |
| 158 | them a chance to make revisions.</p> |
157 | them a chance to make revisions.</p> |
| 159 | <p>For a GLEP to be accepted it must meet certain minimum criteria. It must be a |
158 | <p>For a GLEP to be approved it must meet certain minimum criteria. It must be a |
| 160 | clear and complete description of the proposed enhancement. The enhancement |
159 | clear and complete description of the proposed enhancement. The enhancement |
| 161 | must represent a net improvement. The proposed implementation, if applicable, |
160 | must represent a net improvement. The proposed implementation, if applicable, |
| 162 | must be solid and must not complicate the distribution unduly. Finally, a |
161 | must be solid and must not complicate the distribution unduly. Finally, a |
| 163 | proposed enhancement must satisfy the philosophy of Gentoo Linux.</p> |
162 | proposed enhancement must satisfy the philosophy of Gentoo Linux.</p> |
| 164 | <p>Once a GLEP has been accepted, the reference implementation must be completed. |
163 | <p>Once a GLEP has been accepted, the reference implementation must be completed. |
| … | |
… | |
| 419 | </div> |
418 | </div> |
| 420 | |
419 | |
| 421 | <hr class="footer"/> |
420 | <hr class="footer"/> |
| 422 | <div class="footer"> |
421 | <div class="footer"> |
| 423 | <a class="reference" href="glep-0001.txt">View document source</a>. |
422 | <a class="reference" href="glep-0001.txt">View document source</a>. |
| 424 | Generated on: 2003-07-29 00:12 UTC. |
423 | Generated on: 2004-04-04 23:05 UTC. |
| 425 | Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
424 | Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
| 426 | </div> |
425 | </div> |
| 427 | </body> |
426 | </body> |
| 428 | </html> |
427 | </html> |
| 429 | |
428 | |
Parent Directory
| 
Revision Log
| 
Patch