--- xml/htdocs/proj/en/glep/glep-0001.html 2003/07/29 00:14:27 1.7 +++ xml/htdocs/proj/en/glep/glep-0001.html 2004/04/04 23:05:35 1.8 @@ -119,14 +119,13 @@

The GLEP champion then emails the GLEP editors <glep@gentoo.org> with a proposed title and a rough, but fleshed out, draft of the GLEP. This draft must be written in GLEP style as described below.

-

If the GLEP editor approves, he will assign the GLEP a number, label it -as Standards Track (a better name would be nice here -- suggestions?) -or Informational, give it status "Draft", and -create and check-in the initial draft of the GLEP. The GLEP editors will -not unreasonably deny a GLEP. Reasons for denying GLEP status include -duplication of effort, being technically unsound, not providing proper -motivation or addressing backwards compatibility, or not in keeping -with Gentoo Linux philosophy.

+

If the GLEP editor accepts the GLEP, he will assign the GLEP a number, label +it as Standards Track (a better name would be nice here -- suggestions?) or +Informational, give it status "Draft", and create and check-in the initial +draft of the GLEP. The GLEP editors will not unreasonably deny a GLEP. +Reasons for denying GLEP status include duplication of effort, being +technically unsound, not providing proper motivation or addressing backwards +compatibility, or not in keeping with Gentoo Linux philosophy.

If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the gentoo-dev@gentoo.org mailing list to help flesh it out, gain feedback and consensus from the community at large, and improve the GLEP for re-submission.

@@ -150,13 +149,13 @@ should use their discretion here.

Once the authors have completed a GLEP, they must inform the GLEP editors that it is ready for review. GLEPs are reviewed by the appropriate Gentoo -Manager [8], who may accept or reject a GLEP outright, or +Manager [8], who may approve or reject a GLEP outright, or send it back to the author(s) for revision. For a GLEP that is pre-determined -to be acceptable (e.g., it is an obvious win as-is and/or its implementation +to be approvable (e.g., it is an obvious win as-is and/or its implementation has already been checked in) the appropriate Gentoo Manager [8] may also initiate a GLEP review, first notifying the GLEP author(s) and giving them a chance to make revisions.

-

For a GLEP to be accepted it must meet certain minimum criteria. It must be a +

For a GLEP to be approved it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the distribution unduly. Finally, a @@ -421,7 +420,7 @@