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

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

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

Revision 1.2 Revision 1.5
… …
31<tbody valign="top"> 31<tbody valign="top">
32<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">1</td> 32<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">1</td>
33</tr> 33</tr>
34<tr class="field"><th class="field-name">Title:</th><td class="field-body">GLEP Purpose and Guidelines</td> 34<tr class="field"><th class="field-name">Title:</th><td class="field-body">GLEP Purpose and Guidelines</td>
35</tr> 35</tr>
36<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</td> 36<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.4</td>
37</tr> 37</tr>
38<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0001.txt">2003/06/02 17:37:47</a></td> 38<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0001.txt">2003/06/10 17:33:02</a></td>
39</tr> 39</tr>
40<tr class="field"><th class="field-name">Author:</th><td class="field-body">Grant Goodyear &lt;g2boojum&#32;&#97;t&#32;gentoo.org&gt;</td> 40<tr class="field"><th class="field-name">Author:</th><td class="field-body">Grant Goodyear &lt;g2boojum&#32;&#97;t&#32;gentoo.org&gt;</td>
41</tr> 41</tr>
42<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td> 42<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
43</tr> 43</tr>
44<tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td> 44<tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td>
45</tr> 45</tr>
46<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td> 46<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td>
47</tr> 47</tr>
48<tr class="field"><th class="field-name">Created:</th><td class="field-body">31 May 2003</td> 48<tr class="field"><th class="field-name">Created:</th><td class="field-body">31-May-2003</td>
49</tr> 49</tr>
50<tr class="field"><th class="field-name">Post-History:</th><td class="field-body"></td> 50<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">1-Jun-2003, 2-Jul-2003</td>
51</tr> 51</tr>
52</tbody> 52</tbody>
53</table> 53</table>
54<hr /> 54<hr />
55<div class="contents topic" id="contents"> 55<div class="contents topic" id="contents">
56<p class="topic-title"><a name="contents">Contents</a></p> 56<p class="topic-title"><a name="contents">Contents</a></p>
57<ul class="simple"> 57<ul class="simple">
58<li><a class="reference" href="#credits" id="id14" name="id14">Credits</a></li> 58<li><a class="reference" href="#credits" id="id17" name="id17">Credits</a></li>
59<li><a class="reference" href="#what-is-a-glep" id="id15" name="id15">What is a GLEP?</a></li> 59<li><a class="reference" href="#what-is-a-glep" id="id18" name="id18">What is a GLEP?</a></li>
60<li><a class="reference" href="#kinds-of-gleps" id="id16" name="id16">Kinds of GLEPs</a></li> 60<li><a class="reference" href="#kinds-of-gleps" id="id19" name="id19">Kinds of GLEPs</a></li>
61<li><a class="reference" href="#glep-work-flow" id="id17" name="id17">GLEP Work Flow</a></li> 61<li><a class="reference" href="#glep-work-flow" id="id20" name="id20">GLEP Work Flow</a></li>
62<li><a class="reference" href="#what-belongs-in-a-successful-glep" id="id18" name="id18">What belongs in a successful GLEP?</a></li> 62<li><a class="reference" href="#what-belongs-in-a-successful-glep" id="id21" name="id21">What belongs in a successful GLEP?</a></li>
63<li><a class="reference" href="#glep-formating-and-template" id="id19" name="id19">GLEP Formating and Template</a></li> 63<li><a class="reference" href="#glep-formating-and-template" id="id22" name="id22">GLEP Formating and Template</a></li>
64<li><a class="reference" href="#glep-header-preamble" id="id20" name="id20">GLEP Header Preamble</a></li> 64<li><a class="reference" href="#glep-header-preamble" id="id23" name="id23">GLEP Header Preamble</a></li>
65<li><a class="reference" href="#reporting-glep-bugs-or-submitting-glep-updates" id="id21" name="id21">Reporting GLEP Bugs, or Submitting GLEP Updates</a></li> 65<li><a class="reference" href="#reporting-glep-bugs-or-submitting-glep-updates" id="id24" name="id24">Reporting GLEP Bugs, or Submitting GLEP Updates</a></li>
66<li><a class="reference" href="#transferring-glep-ownership" id="id22" name="id22">Transferring GLEP Ownership</a></li> 66<li><a class="reference" href="#transferring-glep-ownership" id="id25" name="id25">Transferring GLEP Ownership</a></li>
67<li><a class="reference" href="#references-and-footnotes" id="id23" name="id23">References and Footnotes</a></li> 67<li><a class="reference" href="#references-and-footnotes" id="id26" name="id26">References and Footnotes</a></li>
68<li><a class="reference" href="#copyright" id="id24" name="id24">Copyright</a></li> 68<li><a class="reference" href="#copyright" id="id27" name="id27">Copyright</a></li>
69</ul> 69</ul>
70</div> 70</div>
71<div class="section" id="credits"> 71<div class="section" id="credits">
72<h1><a class="toc-backref" href="#id14" name="credits">Credits</a></h1> 72<h1><a class="toc-backref" href="#id17" name="credits">Credits</a></h1>
73<p>The GLEP concept, and, in fact, much of the text of this document, 73<p>The GLEP concept, and, in fact, much of the text of this document,
74is liberally stolen from Python's <a class="footnote-reference" href="#python" id="id1" name="id1">[1]</a> PEPs 74is liberally stolen from Python's <a class="footnote-reference" href="#python" id="id1" name="id1">[1]</a> PEPs
75<a class="footnote-reference" href="#peps" id="id2" name="id2">[2]</a>, especially 75<a class="footnote-reference" href="#peps" id="id2" name="id2">[2]</a>, especially
76PEP-0001 <a class="footnote-reference" href="#pep1" id="id3" name="id3">[3]</a> by Barry A. Warsaw, Jeremy Hylton, and David Goodger.</p> 76PEP-0001 <a class="footnote-reference" href="#pep1" id="id3" name="id3">[3]</a> by Barry A. Warsaw, Jeremy Hylton, and David Goodger.</p>
77</div> 77</div>
78<div class="section" id="what-is-a-glep"> 78<div class="section" id="what-is-a-glep">
79<h1><a class="toc-backref" href="#id15" name="what-is-a-glep">What is a GLEP?</a></h1> 79<h1><a class="toc-backref" href="#id18" name="what-is-a-glep">What is a GLEP?</a></h1>
80<p>GLEP stands for &quot;Gentoo Linux Enhancement Proposal&quot;. A GLEP is a design 80<p>GLEP stands for &quot;Gentoo Linux Enhancement Proposal&quot;. A GLEP is a design
81document providing information to the Gentoo Linux community, or describing 81document providing information to the Gentoo Linux community, or describing
82a new feature for Gentoo Linux. The GLEP should provide a concise technical 82a new feature for Gentoo Linux. The GLEP should provide a concise technical
83specification of the feature and rationale for the feature.</p> 83specification of the feature and rationale for the feature.</p>
84<p>We intend GLEPs to be the primary mechanisms for proposing <em>significant</em> new 84<p>We intend GLEPs to be the primary mechanisms for proposing <em>significant</em> new
… …
89<p>Because the GLEPs are maintained as text files under CVS control, their 89<p>Because the GLEPs are maintained as text files under CVS control, their
90revision history is the historical record of the feature proposal 90revision history is the historical record of the feature proposal
91<a class="footnote-reference" href="#cvs" id="id4" name="id4">[4]</a>.</p> 91<a class="footnote-reference" href="#cvs" id="id4" name="id4">[4]</a>.</p>
92</div> 92</div>
93<div class="section" id="kinds-of-gleps"> 93<div class="section" id="kinds-of-gleps">
94<h1><a class="toc-backref" href="#id16" name="kinds-of-gleps">Kinds of GLEPs</a></h1> 94<h1><a class="toc-backref" href="#id19" name="kinds-of-gleps">Kinds of GLEPs</a></h1>
95<p>There are two kinds of GLEPs. A Standards Track GLEP describes a new feature 95<p>There are two kinds of GLEPs. A Standards Track GLEP describes a new feature
96or implementation for Gentoo Linux. An Informational GLEP describes provides 96or implementation for Gentoo Linux. An Informational GLEP describes provides
97general guidelines or information to the Gentoo Linux community, but does not 97general guidelines or information to the Gentoo Linux community, but does not
98propose a new feature. Informational GLEPs do not necessarily represent a 98propose a new feature. Informational GLEPs do not necessarily represent a
99Gentoo Linux community consensus or recommendation, so users and implementors 99Gentoo Linux community consensus or recommendation, so users and implementors
100are free to ignore Informational GLEPs or follow their advice.</p> 100are free to ignore Informational GLEPs or follow their advice.</p>
101</div> 101</div>
102<div class="section" id="glep-work-flow"> 102<div class="section" id="glep-work-flow">
103<h1><a class="toc-backref" href="#id17" name="glep-work-flow">GLEP Work Flow</a></h1> 103<h1><a class="toc-backref" href="#id20" name="glep-work-flow">GLEP Work Flow</a></h1>
104<p>The GLEP editors assign GLEP numbers and change their status. The current 104<p>The GLEP editors assign GLEP numbers and change their status. The current
105GLEP editors are Grant Goodyear and hopefully somebody else. Please send all 105GLEP editors are Grant Goodyear and Alastair Tse. Please send all
106GLEP-related email to &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;.</p> 106GLEP-related email to &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;.</p>
107<p>The GLEP process begins with a new idea for Gentoo Linux. It is highly 107<p>The GLEP process begins with a new idea for Gentoo Linux. It is highly
108recommended that a single GLEP contain a single key proposal or new idea. The 108recommended that a single GLEP contain a single key proposal or new idea. The
109more focussed the GLEP, the more successful it tends to be. The GLEP editors 109more focussed the GLEP, the more successful it tends to be. The GLEP editors
110reserve the right to reject GLEP proposals if they appear too unfocussed or 110reserve the right to reject GLEP proposals if they appear too unfocussed or
… …
114forums, and attempts to build community consensus around the idea. The GLEP 114forums, and attempts to build community consensus around the idea. The GLEP
115champion (a.k.a. Author) should first attempt to ascertain whether the idea is 115champion (a.k.a. Author) should first attempt to ascertain whether the idea is
116GLEP-able. Small enhancements or patches often don't need a GLEP and can be 116GLEP-able. Small enhancements or patches often don't need a GLEP and can be
117injected into the Gentoo Linux development work flow with an enhancement &quot;bug&quot; 117injected into the Gentoo Linux development work flow with an enhancement &quot;bug&quot;
118submitted to the Gentoo Linux bugzilla <a class="footnote-reference" href="#bugs" id="id5" name="id5">[6]</a>.</p> 118submitted 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 editor &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt; with a 119<p>The GLEP champion then emails the GLEP editors &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt; with a
120proposed title and a rough, but fleshed out, draft of the GLEP. This draft 120proposed title and a rough, but fleshed out, draft of the GLEP. This draft
121must be written in GLEP style as described below.</p> 121must 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 approves, he will assign the GLEP a number, label it
123as Standards Track (a better name would be nice here -- suggestions?) 123as Standards Track (a better name would be nice here -- suggestions?)
124or Informational, give it status &quot;Draft&quot;, and 124or Informational, give it status &quot;Draft&quot;, and
… …
147mailing lists should be avoided. Strategies to keep the discussions efficient 147mailing lists should be avoided. Strategies to keep the discussions efficient
148include setting up a specific forums thread for the topic, having the GLEP 148include setting up a specific forums thread for the topic, having the GLEP
149author accept private comments in the early design phases, etc. GLEP authors 149author accept private comments in the early design phases, etc. GLEP authors
150should use their discretion here.</p> 150should use their discretion here.</p>
151<p>Once the authors have completed a GLEP, they must inform the GLEP editors that 151<p>Once the authors have completed a GLEP, they must inform the GLEP editors that
152it is ready for review. GLEPs are reviewed by the Gentoo Linux Chief 152it is ready for review. GLEPs are reviewed by the appropriate Gentoo
153Architect or Development Manager, who may accept or reject a GLEP outright, or 153Manager <a class="footnote-reference" href="#manager" id="id8" name="id8">[8]</a>, who may accept or reject a GLEP outright, or
154send it back to the author(s) for revision. For a GLEP that is pre-determined 154send it back to the author(s) for revision. For a GLEP that is pre-determined
155to be acceptable (e.g., it is an obvious win as-is and/or its implementation 155to be acceptable (e.g., it is an obvious win as-is and/or its implementation
156has already been checked in) the Chief Architect or the Development Manager 156has already been checked in) the appropriate Gentoo Manager <a class="footnote-reference" href="#manager" id="id9" name="id9">[8]</a>
157may also initiate a GLEP review, first notifying the GLEP author(s) and giving 157may also initiate a GLEP review, first notifying the GLEP author(s) and giving
158them a chance to make revisions.</p> 158them a chance to make revisions.</p>
159<p>For a GLEP to be accepted it must meet certain minimum criteria. It must be a 159<p>For a GLEP to be accepted it must meet certain minimum criteria. It must be a
160clear and complete description of the proposed enhancement. The enhancement 160clear and complete description of the proposed enhancement. The enhancement
161must represent a net improvement. The proposed implementation, if applicable, 161must represent a net improvement. The proposed implementation, if applicable,
… …
181</pre> 181</pre>
182<p>Some Informational GLEPs may also have a status of &quot;Active&quot; if they are never 182<p>Some Informational GLEPs may also have a status of &quot;Active&quot; if they are never
183meant to be completed. E.g. GLEP 1 (this GLEP).</p> 183meant to be completed. E.g. GLEP 1 (this GLEP).</p>
184</div> 184</div>
185<div class="section" id="what-belongs-in-a-successful-glep"> 185<div class="section" id="what-belongs-in-a-successful-glep">
186<h1><a class="toc-backref" href="#id18" name="what-belongs-in-a-successful-glep">What belongs in a successful GLEP?</a></h1> 186<h1><a class="toc-backref" href="#id21" name="what-belongs-in-a-successful-glep">What belongs in a successful GLEP?</a></h1>
187<p>Each GLEP should have the following parts:</p> 187<p>Each GLEP should have the following parts:</p>
188<ol class="arabic"> 188<ol class="arabic">
189<li><p class="first">Preamble -- <a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> style headers containing meta-data about the 189<li><p class="first">Preamble -- <a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> style headers containing meta-data about the
190GLEP, including the GLEP number, a short descriptive title (limited 190GLEP, including the GLEP number, a short descriptive title (limited
191to a maximum of 44 characters), the names, and optionally the 191to a maximum of 44 characters), the names, and optionally the
… …
193</li> 193</li>
194<li><p class="first">Abstract -- a short (~200 word) description of the technical issue 194<li><p class="first">Abstract -- a short (~200 word) description of the technical issue
195being addressed.</p> 195being addressed.</p>
196</li> 196</li>
197<li><p class="first">Motivation -- The motivation is critical for GLEPs that want to 197<li><p class="first">Motivation -- The motivation is critical for GLEPs that want to
198change the Gentoo Linux functionality. It should clearly explain why the 198modify Gentoo Linux functionality. It should clearly explain why the
199existing functionality or policy is inadequate to address the problem that 199existing functionality or policy is inadequate to address the problem that
200the GLEP solves. GLEP submissions without sufficient motivation may be 200the GLEP solves. GLEP submissions without sufficient motivation may be
201rejected outright.</p> 201rejected outright.</p>
202</li> 202</li>
203<li><p class="first">Specification -- The technical specification should describe the 203<li><p class="first">Specification -- The technical specification should describe the
… …
230licensed under the Open Publication License [#OPL].</p> 230licensed under the Open Publication License [#OPL].</p>
231</li> 231</li>
232</ol> 232</ol>
233</div> 233</div>
234<div class="section" id="glep-formating-and-template"> 234<div class="section" id="glep-formating-and-template">
235<h1><a class="toc-backref" href="#id19" name="glep-formating-and-template">GLEP Formating and Template</a></h1> 235<h1><a class="toc-backref" href="#id22" name="glep-formating-and-template">GLEP Formating and Template</a></h1>
236<p>GLEPs are written either in Gentoo Linux Guide-XML <a class="footnote-reference" href="#guidexml" id="id10" name="id10">[11]</a> or in
236<p>GLEPs are written in a just-barely-marked-up version of plain ASCII text 237a just-barely-marked-up version of plain ASCII text
237called ReStructuredText <a class="footnote-reference" href="#resthome" id="id8" name="id8">[9]</a> that is then converted to HTML using 238called ReStructuredText <a class="footnote-reference" href="#resthome" id="id11" name="id11">[10]</a> that is then converted to HTML using
238Docutils <a class="footnote-reference" href="#docutils" id="id9" name="id9">[11]</a>. Using ReStructuredText GLEPs allows for rich markup 239Docutils <a class="footnote-reference" href="#docutils" id="id12" name="id12">[12]</a>. Using ReStructuredText GLEPs allows for rich markup
239that is still quite easy to read, but results in much better-looking and more 240that is still quite easy to read, but results in much better-looking and more
240functional HTML. Moreover, it should be straightforward to convert GLEPs to 241functional HTML. Moreover, it should be straightforward to convert GLEPs to
241Gentoo Linux guide xml <a class="footnote-reference" href="#guidexml" id="id10" name="id10">[10]</a> if needed. GLEP 2 contains a boilerplate 242Gentoo Linux guide xml <a class="footnote-reference" href="#guidexml" id="id13" name="id13">[11]</a> if needed. GLEP 2 contains a boilerplate
242template <a class="footnote-reference" href="#rest" id="id11" name="id11">[5]</a> for use with ReStructuredText GLEPs.</p> 243template <a class="footnote-reference" href="#rest" id="id14" name="id14">[5]</a> for use with ReStructuredText GLEPs.</p>
243</div> 244</div>
244<div class="section" id="glep-header-preamble"> 245<div class="section" id="glep-header-preamble">
245<h1><a class="toc-backref" href="#id20" name="glep-header-preamble">GLEP Header Preamble</a></h1> 246<h1><a class="toc-backref" href="#id23" name="glep-header-preamble">GLEP Header Preamble</a></h1>
246<p>Each GLEP must begin with an <a class="reference" href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> style header preamble. The headers 247<p>Each GLEP must begin with an <a class="reference" href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> style header preamble. The headers
247must appear in the following order. Headers marked with &quot;*&quot; are 248must appear in the following order. Headers marked with &quot;*&quot; are
248optional and are described below. All other headers are required.</p> 249optional and are described below. All other headers are required.</p>
249<pre class="literal-block"> 250<pre class="literal-block">
250 GLEP: &lt;glep number&gt; 251 GLEP: &lt;glep number&gt;
… …
282GLEP is being discussed privately with the author, or on the gentoo-dev 283GLEP is being discussed privately with the author, or on the gentoo-dev
283mailing list. Note that email addresses in the Discussions-To header will not 284mailing list. Note that email addresses in the Discussions-To header will not
284be obscured.</p> 285be obscured.</p>
285<p>The Type header specifies the type of GLEP: Informational or Standards 286<p>The Type header specifies the type of GLEP: Informational or Standards
286Track.</p> 287Track.</p>
287<p>The format of a GLEP is specified with a Content-Type header, which for now 288<p>The format of a GLEP is specified with a Content-Type header, which
289should read &quot;text/xml&quot; for Gentoo Guide XML or
288should always read &quot;text/x-rst&quot; for ReStructuredText GLEPs (see GLEP 2 290&quot;text/x-rst&quot; for ReStructuredText GLEPs (see GLEP 2
289<a class="footnote-reference" href="#rest" id="id12" name="id12">[5]</a>).</p> 291<a class="footnote-reference" href="#rest" id="id15" name="id15">[5]</a>).</p>
290<p>The Created header records the date that the GLEP was assigned a number, while 292<p>The Created header records the date that the GLEP was assigned a number, while
291Post-History is used to record the dates of when new versions of the GLEP are 293Post-History is used to record the dates of when new versions of the GLEP are
292posted to gentoo-dev. Both headers should be in dd-mmm-yyyy format, e.g. 294posted to gentoo-dev. Both headers should be in dd-mmm-yyyy format, e.g.
29314-Aug-2001.</p> 29514-Aug-2001.</p>
294<p>GLEPs may have a Requires header, indicating the GLEP numbers that this GLEP 296<p>GLEPs may have a Requires header, indicating the GLEP numbers that this GLEP
… …
297rendered obsolete by a later document; the value is the number of the GLEP 299rendered obsolete by a later document; the value is the number of the GLEP
298that replaces the current document. The newer GLEP must have a Replaces 300that replaces the current document. The newer GLEP must have a Replaces
299header containing the number of the GLEP that it rendered obsolete.</p> 301header containing the number of the GLEP that it rendered obsolete.</p>
300</div> 302</div>
301<div class="section" id="reporting-glep-bugs-or-submitting-glep-updates"> 303<div class="section" id="reporting-glep-bugs-or-submitting-glep-updates">
302<h1><a class="toc-backref" href="#id21" name="reporting-glep-bugs-or-submitting-glep-updates">Reporting GLEP Bugs, or Submitting GLEP Updates</a></h1> 304<h1><a class="toc-backref" href="#id24" name="reporting-glep-bugs-or-submitting-glep-updates">Reporting GLEP Bugs, or Submitting GLEP Updates</a></h1>
303<p>How you report a bug, or submit a GLEP update depends on several factors, such 305<p>How you report a bug, or submit a GLEP update depends on several factors, such
304as the maturity of the GLEP, the preferences of the GLEP author, and the 306as the maturity of the GLEP, the preferences of the GLEP author, and the
305nature of your comments. For the early draft stages of the GLEP, it's 307nature of your comments. For the early draft stages of the GLEP, it's
306probably best to send your comments and changes directly to the GLEP author. 308probably best to send your comments and changes directly to the GLEP author.
307For more mature, or finished GLEPs you may want to submit corrections to the 309For more mature, or finished GLEPs you may want to submit corrections to the
308Gentoo Linux bugzilla <a class="footnote-reference" href="#bugs" id="id13" name="id13">[6]</a> so that your changes don't get lost. If the GLEP 310Gentoo Linux bugzilla <a class="footnote-reference" href="#bugs" id="id16" name="id16">[6]</a> so that your changes don't get lost. If the GLEP
309author is a Gentoo Linux developer, assign the bug/patch to him, otherwise 311author is a Gentoo Linux developer, assign the bug/patch to him, otherwise
310assign it to the GLEP editors.</p> 312assign it to the GLEP editors.</p>
311<p>When in doubt about where to send your changes, please check first with the 313<p>When in doubt about where to send your changes, please check first with the
312GLEP author and/or GLEP editors.</p> 314GLEP author and/or GLEP editors.</p>
313<p>GLEP authors who are also Gentoo Linux developers can update the GLEPs 315<p>GLEP authors who are also Gentoo Linux developers can update the GLEPs
314themselves by using &quot;cvs commit&quot; to commit their changes.</p> 316themselves by using &quot;cvs commit&quot; to commit their changes.</p>
315</div> 317</div>
316<div class="section" id="transferring-glep-ownership"> 318<div class="section" id="transferring-glep-ownership">
317<h1><a class="toc-backref" href="#id22" name="transferring-glep-ownership">Transferring GLEP Ownership</a></h1> 319<h1><a class="toc-backref" href="#id25" name="transferring-glep-ownership">Transferring GLEP Ownership</a></h1>
318<p>It occasionally becomes necessary to transfer ownership of GLEPs to a new 320<p>It occasionally becomes necessary to transfer ownership of GLEPs to a new
319champion. In general, we'd like to retain the original author as a co-author 321champion. In general, we'd like to retain the original author as a co-author
320of the transferred GLEP, but that's really up to the original author. A good 322of the transferred GLEP, but that's really up to the original author. A good
321reason to transfer ownership is because the original author no longer has the 323reason to transfer ownership is because the original author no longer has the
322time or interest in updating it or following through with the GLEP process, or 324time or interest in updating it or following through with the GLEP process, or
… …
329&lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;. If the original author doesn't respond to email in a 331&lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;. If the original author doesn't respond to email in a
330timely manner, the GLEP editors will make a unilateral decision (it's not like 332timely manner, the GLEP editors will make a unilateral decision (it's not like
331such decisions can't be reversed :).</p> 333such decisions can't be reversed :).</p>
332</div> 334</div>
333<div class="section" id="references-and-footnotes"> 335<div class="section" id="references-and-footnotes">
334<h1><a class="toc-backref" href="#id23" name="references-and-footnotes">References and Footnotes</a></h1> 336<h1><a class="toc-backref" href="#id26" name="references-and-footnotes">References and Footnotes</a></h1>
335<table class="footnote" frame="void" id="python" rules="none"> 337<table class="footnote" frame="void" id="python" rules="none">
336<colgroup><col class="label" /><col /></colgroup> 338<colgroup><col class="label" /><col /></colgroup>
337<tbody valign="top"> 339<tbody valign="top">
338<tr><td class="label"><a class="fn-backref" href="#id1" name="python">[1]</a></td><td><a class="reference" href="http://www.python.org">http://www.python.org</a></td></tr> 340<tr><td class="label"><a class="fn-backref" href="#id1" name="python">[1]</a></td><td><a class="reference" href="http://www.python.org">http://www.python.org</a></td></tr>
339</tbody> 341</tbody>
… …
355<tbody valign="top"> 357<tbody valign="top">
356<tr><td class="label"><a class="fn-backref" href="#id4" name="cvs">[4]</a></td><td>This historical record is available by the normal CVS commands 358<tr><td class="label"><a class="fn-backref" href="#id4" name="cvs">[4]</a></td><td>This historical record is available by the normal CVS commands
357for retrieving older revisions. For those without direct access to the CVS 359for retrieving older revisions. For those without direct access to the CVS
358tree, you can browse the current and past GLEP revisions via the Gentoo 360tree, you can browse the current and past GLEP revisions via the Gentoo
359Linux viewcvs web site at 361Linux viewcvs web site at
360<a class="reference" href="http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/">http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/</a></td></tr> 362<a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/">http://www.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/</a></td></tr>
361</tbody> 363</tbody>
362</table> 364</table>
363<table class="footnote" frame="void" id="rest" rules="none"> 365<table class="footnote" frame="void" id="rest" rules="none">
364<colgroup><col class="label" /><col /></colgroup> 366<colgroup><col class="label" /><col /></colgroup>
365<tbody valign="top"> 367<tbody valign="top">
366<tr><td class="label"><a name="rest">[5]</a></td><td><em>(<a class="fn-backref" href="#id11">1</a>, <a class="fn-backref" href="#id12">2</a>)</em> GLEP 2, Sample ReStructuredText GLEP Template, 368<tr><td class="label"><a name="rest">[5]</a></td><td><em>(<a class="fn-backref" href="#id14">1</a>, <a class="fn-backref" href="#id15">2</a>)</em> GLEP 2, Sample ReStructuredText GLEP Template,
367(<a class="reference" href="http://glep.gentoo.org/glep-0002.html">http://glep.gentoo.org/glep-0002.html</a>)</td></tr> 369(<a class="reference" href="http://glep.gentoo.org/glep-0002.html">http://glep.gentoo.org/glep-0002.html</a>)</td></tr>
368</tbody> 370</tbody>
369</table> 371</table>
370<table class="footnote" frame="void" id="bugs" rules="none"> 372<table class="footnote" frame="void" id="bugs" rules="none">
371<colgroup><col class="label" /><col /></colgroup> 373<colgroup><col class="label" /><col /></colgroup>
372<tbody valign="top"> 374<tbody valign="top">
373<tr><td class="label"><a name="bugs">[6]</a></td><td><em>(<a class="fn-backref" href="#id5">1</a>, <a class="fn-backref" href="#id13">2</a>)</em> <a class="reference" href="http://bugs.gentoo.org">http://bugs.gentoo.org</a></td></tr> 375<tr><td class="label"><a name="bugs">[6]</a></td><td><em>(<a class="fn-backref" href="#id5">1</a>, <a class="fn-backref" href="#id16">2</a>)</em> <a class="reference" href="http://bugs.gentoo.org">http://bugs.gentoo.org</a></td></tr>
374</tbody> 376</tbody>
375</table> 377</table>
376<table class="footnote" frame="void" id="forums" rules="none"> 378<table class="footnote" frame="void" id="forums" rules="none">
377<colgroup><col class="label" /><col /></colgroup> 379<colgroup><col class="label" /><col /></colgroup>
378<tbody valign="top"> 380<tbody valign="top">
379<tr><td class="label"><a name="forums">[7]</a></td><td><em>(<a class="fn-backref" href="#id6">1</a>, <a class="fn-backref" href="#id7">2</a>)</em> <a class="reference" href="http://forums.gentoo.org">http://forums.gentoo.org</a></td></tr> 381<tr><td class="label"><a name="forums">[7]</a></td><td><em>(<a class="fn-backref" href="#id6">1</a>, <a class="fn-backref" href="#id7">2</a>)</em> <a class="reference" href="http://forums.gentoo.org">http://forums.gentoo.org</a></td></tr>
380</tbody> 382</tbody>
381</table> 383</table>
384<table class="footnote" frame="void" id="manager" rules="none">
385<colgroup><col class="label" /><col /></colgroup>
386<tbody valign="top">
387<tr><td class="label"><a name="manager">[8]</a></td><td><em>(<a class="fn-backref" href="#id8">1</a>, <a class="fn-backref" href="#id9">2</a>)</em> <a class="reference" href="http://www.gentoo.org/doc/en/management-structure.xml">http://www.gentoo.org/doc/en/management-structure.xml</a></td></tr>
388</tbody>
389</table>
382<table class="footnote" frame="void" id="opl" rules="none"> 390<table class="footnote" frame="void" id="opl" rules="none">
383<colgroup><col class="label" /><col /></colgroup> 391<colgroup><col class="label" /><col /></colgroup>
384<tbody valign="top"> 392<tbody valign="top">
385<tr><td class="label"><a name="opl">[8]</a></td><td><a class="reference" href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a></td></tr> 393<tr><td class="label"><a name="opl">[9]</a></td><td><a class="reference" href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a></td></tr>
386</tbody> 394</tbody>
387</table> 395</table>
388<table class="footnote" frame="void" id="resthome" rules="none"> 396<table class="footnote" frame="void" id="resthome" rules="none">
389<colgroup><col class="label" /><col /></colgroup> 397<colgroup><col class="label" /><col /></colgroup>
390<tbody valign="top"> 398<tbody valign="top">
391<tr><td class="label"><a class="fn-backref" href="#id8" name="resthome">[9]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/rst.html">http://docutils.sourceforge.net/rst.html</a></td></tr> 399<tr><td class="label"><a class="fn-backref" href="#id11" name="resthome">[10]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/rst.html">http://docutils.sourceforge.net/rst.html</a></td></tr>
392</tbody> 400</tbody>
393</table> 401</table>
394<table class="footnote" frame="void" id="guidexml" rules="none"> 402<table class="footnote" frame="void" id="guidexml" rules="none">
395<colgroup><col class="label" /><col /></colgroup> 403<colgroup><col class="label" /><col /></colgroup>
396<tbody valign="top"> 404<tbody valign="top">
397<tr><td class="label"><a class="fn-backref" href="#id10" name="guidexml">[10]</a></td><td><a class="reference" href="http://www.gentoo.org/doc/en/xml-guide.xml">http://www.gentoo.org/doc/en/xml-guide.xml</a></td></tr> 405<tr><td class="label"><a name="guidexml">[11]</a></td><td><em>(<a class="fn-backref" href="#id10">1</a>, <a class="fn-backref" href="#id13">2</a>)</em> <a class="reference" href="http://www.gentoo.org/doc/en/xml-guide.xml">http://www.gentoo.org/doc/en/xml-guide.xml</a></td></tr>
398</tbody> 406</tbody>
399</table> 407</table>
400<table class="footnote" frame="void" id="docutils" rules="none"> 408<table class="footnote" frame="void" id="docutils" rules="none">
401<colgroup><col class="label" /><col /></colgroup> 409<colgroup><col class="label" /><col /></colgroup>
402<tbody valign="top"> 410<tbody valign="top">
403<tr><td class="label"><a class="fn-backref" href="#id9" name="docutils">[11]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/">http://docutils.sourceforge.net/</a></td></tr> 411<tr><td class="label"><a class="fn-backref" href="#id12" name="docutils">[12]</a></td><td><a class="reference" href="http://docutils.sourceforge.net/">http://docutils.sourceforge.net/</a></td></tr>
404</tbody> 412</tbody>
405</table> 413</table>
406</div> 414</div>
407<div class="section" id="copyright"> 415<div class="section" id="copyright">
408<h1><a class="toc-backref" href="#id24" name="copyright">Copyright</a></h1> 416<h1><a class="toc-backref" href="#id27" name="copyright">Copyright</a></h1>
409<p>This document has been placed in the public domain.</p> 417<p>This document has been placed in the public domain.</p>
410</div> 418</div>
411</div> 419</div>
412 420
413<hr class="footer"/> 421<hr class="footer"/>
414<div class="footer"> 422<div class="footer">
415<a class="reference" href="glep-0001.txt">View document source</a>. 423<a class="reference" href="glep-0001.txt">View document source</a>.
416Generated on: 2003-06-04 19:48 UTC. 424Generated on: 2003-07-02 20:02 UTC.
417Generated 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. 425Generated 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.
418</div> 426</div>
419</body> 427</body>
420</html> 428</html>
421 429
Legend:
Removed from v.1.2  
changed lines
  Added in v.1.5
  ViewVC Help
Powered by ViewVC 1.1.20