1 | GLEP: 1 |
1 | GLEP: 1 |
2 | Title: GLEP Purpose and Guidelines |
2 | Title: GLEP Purpose and Guidelines |
3 | Version: $Revision: 1.12 $ |
3 | Version: $Revision: 1.13 $ |
4 | Last-Modified: $Date: 2008/06/05 06:05:32 $ |
4 | Last-Modified: $Date: 2011/03/10 20:53:02 $ |
5 | Author: Grant Goodyear <g2boojum@gentoo.org> |
5 | Author: Grant Goodyear <g2boojum@gentoo.org> |
6 | Status: Active |
6 | Status: Active |
7 | Type: Informational |
7 | Type: Informational |
8 | Content-Type: text/x-rst |
8 | Content-Type: text/x-rst |
9 | Created: 31-May-2003 |
9 | Created: 31-May-2003 |
10 | Post-History: 1-Jun-2003, 2-Jul-2003, 19-Jan-2008, 05-Jun-2008 |
10 | Post-History: 1-Jun-2003, 2-Jul-2003, 19-Jan-2008, 05-Jun-2008, 09-Mar-2011 |
11 | |
11 | |
12 | Credits |
12 | Credits |
13 | ======= |
13 | ======= |
14 | |
14 | |
15 | The GLEP concept, and, in fact, much of the text of this document, |
15 | The GLEP concept, and, in fact, much of the text of this document, |
… | |
… | |
83 | If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the |
83 | If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the |
84 | gentoo-dev@gentoo.org mailing list to help flesh it out, gain feedback and |
84 | gentoo-dev@gentoo.org mailing list to help flesh it out, gain feedback and |
85 | consensus from the community at large, and improve the GLEP for re-submission. |
85 | consensus from the community at large, and improve the GLEP for re-submission. |
86 | |
86 | |
87 | The author of the GLEP is then responsible for posting the GLEP to the |
87 | The author of the GLEP is then responsible for posting the GLEP to the |
88 | gentoo-dev mailing list and to the Gentoo Linux forums [#FORUMS]_, and |
88 | gentoo-dev mailing list (and additionally to the Gentoo Linux forums [#FORUMS]_ |
89 | marshaling community support for it. As updates are necessary, the GLEP |
89 | if they so desire), and marshaling community support for it. As updates are |
90 | author can check in new versions if they have CVS commit permissions, or can |
90 | necessary, the GLEP author may check in new versions directly, or forward to |
91 | email new GLEP versions to the GLEP editors for committing. |
91 | a Gentoo developer with commit access. |
92 | |
92 | |
93 | Standards Track GLEPs consist of two parts, a design document and a reference |
93 | Standards Track GLEPs consist of two parts, a design document and a reference |
94 | implementation. The GLEP should be reviewed and accepted before a reference |
94 | implementation. The GLEP should be reviewed and accepted before a reference |
95 | implementation is begun, unless a reference implementation will aid people in |
95 | implementation is begun, unless a reference implementation will aid people in |
96 | studying the GLEP. Standards Track GLEPs must include an implementation -- in |
96 | studying the GLEP. Standards Track GLEPs must include an implementation -- in |
97 | the form of code, patch, or URL to same -- before it can be considered Final. |
97 | the form of code, patch, or URL to same -- before it can be considered Final. |
98 | |
98 | |
99 | GLEP authors are responsible for collecting community feedback on a GLEP |
99 | GLEP authors are responsible for collecting community feedback on a GLEP |
100 | before submitting it for review. A GLEP that has not been discussed on |
100 | before submitting it for review. A GLEP that has not been discussed on |
101 | gentoo-dev@gentoo.org and/or the Gentoo Linux forums [#FORUMS]_ will not be |
101 | gentoo-dev@gentoo.org and the Gentoo Linux forums [#FORUMS]_ will not be |
102 | accepted. However, wherever possible, long open-ended discussions on public |
102 | accepted. However, wherever possible, long open-ended discussions on public |
103 | mailing lists should be avoided. Strategies to keep the discussions efficient |
103 | mailing lists should be avoided. Strategies to keep the discussions efficient |
104 | include setting up a specific forums thread for the topic, having the GLEP |
104 | include setting up a specific forums thread for the topic, having the GLEP |
105 | author accept private comments in the early design phases, etc. GLEP authors |
105 | author accept private comments in the early design phases, etc. GLEP authors |
106 | should use their discretion here. |
106 | should use their discretion here. |
107 | |
107 | |
108 | Once the authors have completed a GLEP, they must inform the GLEP editors that |
108 | Once the authors have completed a GLEP, they must inform the Gentoo Council |
109 | it is ready for review. GLEPs are reviewed by the appropriate Gentoo |
109 | [#COUNCIL]_ that it is ready for review by way of the gentoo-dev mailing |
110 | Manager [#MANAGER]_, who may approve or reject a GLEP outright, or |
110 | list. GLEPs are then reviewed at a Council meeting where the may be approved |
111 | send it back to the author(s) for revision. For a GLEP that is pre-determined |
111 | or rejected outright, or sent back to the author(s) for revision. This |
112 | to be approvable (e.g., it is an obvious win as-is and/or its implementation |
112 | generally should be done a few weeks in advance of the actual review so as to |
113 | has already been checked in) the appropriate Gentoo Manager [#MANAGER]_ |
113 | avoid the appearance of "slipping" a GLEP in without proper public review |
114 | may also initiate a GLEP review, first notifying the GLEP author(s) and giving |
114 | by the Gentoo developer community. |
115 | them a chance to make revisions. |
|
|
116 | |
115 | |
117 | For a GLEP to be approved it must meet certain minimum criteria. It must be a |
116 | For a GLEP to be approved it must meet certain minimum criteria. It must be a |
118 | clear and complete description of the proposed enhancement. The enhancement |
117 | clear and complete description of the proposed enhancement. The enhancement |
119 | must represent a net improvement. The proposed implementation, if applicable, |
118 | must represent a net improvement. The proposed implementation, if applicable, |
120 | must be solid and must not complicate the distribution unduly. Finally, a |
119 | must be solid and must not complicate the distribution unduly. Finally, a |
… | |
… | |
336 | |
335 | |
337 | .. [#BUGS] http://bugs.gentoo.org |
336 | .. [#BUGS] http://bugs.gentoo.org |
338 | |
337 | |
339 | .. [#FORUMS] http://forums.gentoo.org |
338 | .. [#FORUMS] http://forums.gentoo.org |
340 | |
339 | |
341 | .. [#MANAGER] http://www.gentoo.org/doc/en/management-structure.xml |
340 | .. [#COUNCIL] http://www.gentoo.org/proj/en/glep/glep-0039.html |
342 | |
341 | |
343 | .. [#OPL] http://www.opencontent.org/openpub/ |
342 | .. [#OPL] http://www.opencontent.org/openpub/ |
344 | |
343 | |
345 | .. [#ReSTHOME] http://docutils.sourceforge.net/rst.html |
344 | .. [#ReSTHOME] http://docutils.sourceforge.net/rst.html |
346 | |
345 | |