| 1 | GLEP: 1 |
1 | GLEP: 1 |
| 2 | Title: GLEP Purpose and Guidelines |
2 | Title: GLEP Purpose and Guidelines |
| 3 | Version: $Revision: 1.6 $ |
3 | Version: $Revision: 1.10 $ |
| 4 | Last-Modified: $Date: 2003/07/17 14:26:18 $ |
4 | Last-Modified: $Date: 2008/01/05 03:05:07 $ |
| 5 | Author: Grant Goodyear <g2boojum@gentoo.org> |
5 | Author: Grant Goodyear <g2boojum@gentoo.org> |
| 6 | Status: Draft |
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 |
10 | Post-History: 1-Jun-2003, 2-Jul-2003 |
| 11 | |
11 | |
| … | |
… | |
| 71 | |
71 | |
| 72 | The GLEP champion then emails the GLEP editors <glep@gentoo.org> with a |
72 | The GLEP champion then emails the GLEP editors <glep@gentoo.org> with a |
| 73 | proposed title and a rough, but fleshed out, draft of the GLEP. This draft |
73 | proposed title and a rough, but fleshed out, draft of the GLEP. This draft |
| 74 | must be written in GLEP style as described below. |
74 | must be written in GLEP style as described below. |
| 75 | |
75 | |
| 76 | If the GLEP editor approves, he will assign the GLEP a number, label it |
76 | If the GLEP editor accepts the GLEP, he will assign the GLEP a number, label |
| 77 | as Standards Track (a better name would be nice here -- suggestions?) |
77 | it as Standards Track (a better name would be nice here -- suggestions?) or |
| 78 | or Informational, give it status "Draft", and |
78 | Informational, give it status "Draft", and create and check-in the initial |
| 79 | create and check-in the initial draft of the GLEP. The GLEP editors will |
79 | draft of the GLEP. The GLEP editors will not unreasonably deny a GLEP. |
| 80 | not unreasonably deny a GLEP. Reasons for denying GLEP status include |
80 | Reasons for denying GLEP status include duplication of effort, being |
| 81 | duplication of effort, being technically unsound, not providing proper |
81 | technically unsound, not providing proper motivation or addressing backwards |
| 82 | motivation or addressing backwards compatibility, or not in keeping |
82 | compatibility, or not in keeping with Gentoo Linux philosophy. |
| 83 | with Gentoo Linux philosophy. |
|
|
| 84 | |
83 | |
| 85 | If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the |
84 | If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the |
| 86 | gentoo-dev@gentoo.org mailing list to help flesh it out, gain feedback and |
85 | gentoo-dev@gentoo.org mailing list to help flesh it out, gain feedback and |
| 87 | consensus from the community at large, and improve the GLEP for re-submission. |
86 | consensus from the community at large, and improve the GLEP for re-submission. |
| 88 | |
87 | |
| … | |
… | |
| 107 | author accept private comments in the early design phases, etc. GLEP authors |
106 | author accept private comments in the early design phases, etc. GLEP authors |
| 108 | should use their discretion here. |
107 | should use their discretion here. |
| 109 | |
108 | |
| 110 | Once the authors have completed a GLEP, they must inform the GLEP editors that |
109 | Once the authors have completed a GLEP, they must inform the GLEP editors that |
| 111 | it is ready for review. GLEPs are reviewed by the appropriate Gentoo |
110 | it is ready for review. GLEPs are reviewed by the appropriate Gentoo |
| 112 | Manager [#MANAGER]_, who may accept or reject a GLEP outright, or |
111 | Manager [#MANAGER]_, who may approve or reject a GLEP outright, or |
| 113 | send it back to the author(s) for revision. For a GLEP that is pre-determined |
112 | send it back to the author(s) for revision. For a GLEP that is pre-determined |
| 114 | to be acceptable (e.g., it is an obvious win as-is and/or its implementation |
113 | to be approvable (e.g., it is an obvious win as-is and/or its implementation |
| 115 | has already been checked in) the appropriate Gentoo Manager [#MANAGER]_ |
114 | has already been checked in) the appropriate Gentoo Manager [#MANAGER]_ |
| 116 | may also initiate a GLEP review, first notifying the GLEP author(s) and giving |
115 | may also initiate a GLEP review, first notifying the GLEP author(s) and giving |
| 117 | them a chance to make revisions. |
116 | them a chance to make revisions. |
| 118 | |
117 | |
| 119 | For a GLEP to be accepted it must meet certain minimum criteria. It must be a |
118 | For a GLEP to be approved it must meet certain minimum criteria. It must be a |
| 120 | clear and complete description of the proposed enhancement. The enhancement |
119 | clear and complete description of the proposed enhancement. The enhancement |
| 121 | must represent a net improvement. The proposed implementation, if applicable, |
120 | must represent a net improvement. The proposed implementation, if applicable, |
| 122 | must be solid and must not complicate the distribution unduly. Finally, a |
121 | must be solid and must not complicate the distribution unduly. Finally, a |
| 123 | proposed enhancement must satisfy the philosophy of Gentoo Linux. |
122 | proposed enhancement must satisfy the philosophy of Gentoo Linux. |
| 124 | |
123 | |
Parent Directory
| 
Revision Log
| 
Patch