/[gentoo]/xml/htdocs/proj/en/glep/glep-0001.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0001.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

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

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.10

  ViewVC Help
Powered by ViewVC 1.1.20