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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.12 - (hide annotations) (download) (as text)
Sun Jan 20 02:56:39 2008 UTC (6 years, 6 months ago) by antarus
Branch: MAIN
Changes since 1.11: +6 -4 lines
File MIME type: text/html
Mark glep 39 as replacing glep 1, per Betelgeuse

1 g2boojum 1.1 <?xml version="1.0" encoding="utf-8" ?>
2     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3     <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 antarus 1.11
5 g2boojum 1.1 <head>
6     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
7 g2boojum 1.9 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
8 g2boojum 1.1 <title>GLEP 1 -- GLEP Purpose and Guidelines</title>
9 antarus 1.11 <link rel="stylesheet" href="tools/glep.css" type="text/css" />
10 g2boojum 1.1 </head>
11     <body bgcolor="white">
12     <table class="navigation" cellpadding="0" cellspacing="0"
13     width="100%" border="0">
14     <tr><td class="navicon" width="150" height="35">
15     <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
16     <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
17     border="0" width="150" height="35" /></a></td>
18     <td class="textlinks" align="left">
19     [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
20 antarus 1.11 [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
21 g2boojum 1.2 [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0001.txt">GLEP Source</a></b>]
22 g2boojum 1.1 </td></tr></table>
23 g2boojum 1.9 <table class="rfc2822 docutils field-list" frame="void" rules="none">
24 g2boojum 1.1 <col class="field-name" />
25     <col class="field-body" />
26     <tbody valign="top">
27     <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">1</td>
28     </tr>
29     <tr class="field"><th class="field-name">Title:</th><td class="field-body">GLEP Purpose and Guidelines</td>
30     </tr>
31 antarus 1.12 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.10</td>
32 g2boojum 1.1 </tr>
33 antarus 1.12 <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/xml/htdocs/proj/en/glep/glep-0001.txt?cvsroot=gentoo">2008/01/05 03:05:07</a></td>
34 g2boojum 1.1 </tr>
35 g2boojum 1.2 <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>
36 g2boojum 1.1 </tr>
37 liquidx 1.6 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Active</td>
38 g2boojum 1.1 </tr>
39     <tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td>
40     </tr>
41 g2boojum 1.2 <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>
42 g2boojum 1.1 </tr>
43 g2boojum 1.3 <tr class="field"><th class="field-name">Created:</th><td class="field-body">31-May-2003</td>
44 g2boojum 1.1 </tr>
45 antarus 1.12 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">1-Jun-2003, 2-Jul-2003, 19-Jan-2008</td>
46     </tr>
47     <tr class="field"><th class="field-name">Replaced-By:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/proj/en/glepglep-0039.html">39</a></td>
48 g2boojum 1.1 </tr>
49     </tbody>
50     </table>
51     <hr />
52 g2boojum 1.9 <div class="contents topic">
53     <p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
54 g2boojum 1.1 <ul class="simple">
55 g2boojum 1.4 <li><a class="reference" href="#credits" id="id17" name="id17">Credits</a></li>
56     <li><a class="reference" href="#what-is-a-glep" id="id18" name="id18">What is a GLEP?</a></li>
57     <li><a class="reference" href="#kinds-of-gleps" id="id19" name="id19">Kinds of GLEPs</a></li>
58     <li><a class="reference" href="#glep-work-flow" id="id20" name="id20">GLEP Work Flow</a></li>
59     <li><a class="reference" href="#what-belongs-in-a-successful-glep" id="id21" name="id21">What belongs in a successful GLEP?</a></li>
60     <li><a class="reference" href="#glep-formating-and-template" id="id22" name="id22">GLEP Formating and Template</a></li>
61     <li><a class="reference" href="#glep-header-preamble" id="id23" name="id23">GLEP Header Preamble</a></li>
62     <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>
63     <li><a class="reference" href="#transferring-glep-ownership" id="id25" name="id25">Transferring GLEP Ownership</a></li>
64     <li><a class="reference" href="#references-and-footnotes" id="id26" name="id26">References and Footnotes</a></li>
65     <li><a class="reference" href="#copyright" id="id27" name="id27">Copyright</a></li>
66 g2boojum 1.1 </ul>
67     </div>
68 g2boojum 1.9 <div class="section">
69     <h1><a class="toc-backref" href="#id17" id="credits" name="credits">Credits</a></h1>
70 g2boojum 1.1 <p>The GLEP concept, and, in fact, much of the text of this document,
71     is liberally stolen from Python's <a class="footnote-reference" href="#python" id="id1" name="id1">[1]</a> PEPs
72     <a class="footnote-reference" href="#peps" id="id2" name="id2">[2]</a>, especially
73     PEP-0001 <a class="footnote-reference" href="#pep1" id="id3" name="id3">[3]</a> by Barry A. Warsaw, Jeremy Hylton, and David Goodger.</p>
74     </div>
75 g2boojum 1.9 <div class="section">
76     <h1><a class="toc-backref" href="#id18" id="what-is-a-glep" name="what-is-a-glep">What is a GLEP?</a></h1>
77 g2boojum 1.1 <p>GLEP stands for &quot;Gentoo Linux Enhancement Proposal&quot;. A GLEP is a design
78     document providing information to the Gentoo Linux community, or describing
79     a new feature for Gentoo Linux. The GLEP should provide a concise technical
80     specification of the feature and rationale for the feature.</p>
81     <p>We intend GLEPs to be the primary mechanisms for proposing <em>significant</em> new
82     features, for collecting community input on an issue, and for
83     documenting the design decisions that have gone into Gentoo Linux. The GLEP
84     author is responsible for building consensus within the community and
85     documenting dissenting opinions.</p>
86     <p>Because the GLEPs are maintained as text files under CVS control, their
87     revision history is the historical record of the feature proposal
88     <a class="footnote-reference" href="#cvs" id="id4" name="id4">[4]</a>.</p>
89     </div>
90 g2boojum 1.9 <div class="section">
91     <h1><a class="toc-backref" href="#id19" id="kinds-of-gleps" name="kinds-of-gleps">Kinds of GLEPs</a></h1>
92 g2boojum 1.1 <p>There are two kinds of GLEPs. A Standards Track GLEP describes a new feature
93     or implementation for Gentoo Linux. An Informational GLEP describes provides
94     general guidelines or information to the Gentoo Linux community, but does not
95     propose a new feature. Informational GLEPs do not necessarily represent a
96     Gentoo Linux community consensus or recommendation, so users and implementors
97     are free to ignore Informational GLEPs or follow their advice.</p>
98     </div>
99 g2boojum 1.9 <div class="section">
100     <h1><a class="toc-backref" href="#id20" id="glep-work-flow" name="glep-work-flow">GLEP Work Flow</a></h1>
101 g2boojum 1.1 <p>The GLEP editors assign GLEP numbers and change their status. The current
102 g2boojum 1.4 GLEP editors are Grant Goodyear and Alastair Tse. Please send all
103 g2boojum 1.1 GLEP-related email to &lt;<a class="reference" href="mailto:glep&#64;gentoo.org">glep&#64;gentoo.org</a>&gt;.</p>
104     <p>The GLEP process begins with a new idea for Gentoo Linux. It is highly
105     recommended that a single GLEP contain a single key proposal or new idea. The
106     more focussed the GLEP, the more successful it tends to be. The GLEP editors
107     reserve the right to reject GLEP proposals if they appear too unfocussed or
108     too broad. If in doubt, split your GLEP into several well-focussed ones.</p>
109     <p>Each GLEP must have a champion -- someone who writes the GLEP using the style
110     and format described below, shepherds the discussions in the appropriate
111     forums, and attempts to build community consensus around the idea. The GLEP
112     champion (a.k.a. Author) should first attempt to ascertain whether the idea is
113     GLEP-able. Small enhancements or patches often don't need a GLEP and can be
114     injected into the Gentoo Linux development work flow with an enhancement &quot;bug&quot;
115     submitted to the Gentoo Linux bugzilla <a class="footnote-reference" href="#bugs" id="id5" name="id5">[6]</a>.</p>
116 g2boojum 1.4 <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
117 g2boojum 1.1 proposed title and a rough, but fleshed out, draft of the GLEP. This draft
118     must be written in GLEP style as described below.</p>
119 g2boojum 1.8 <p>If the GLEP editor accepts the GLEP, he will assign the GLEP a number, label
120     it as Standards Track (a better name would be nice here -- suggestions?) or
121     Informational, give it status &quot;Draft&quot;, and create and check-in the initial
122     draft of the GLEP. The GLEP editors will not unreasonably deny a GLEP.
123     Reasons for denying GLEP status include duplication of effort, being
124     technically unsound, not providing proper motivation or addressing backwards
125     compatibility, or not in keeping with Gentoo Linux philosophy.</p>
126 g2boojum 1.1 <p>If a pre-GLEP is rejected, the author may elect to take the pre-GLEP to the
127     <a class="reference" href="mailto:gentoo-dev&#64;gentoo.org">gentoo-dev&#64;gentoo.org</a> mailing list to help flesh it out, gain feedback and
128     consensus from the community at large, and improve the GLEP for re-submission.</p>
129     <p>The author of the GLEP is then responsible for posting the GLEP to the
130     gentoo-dev mailing list and to the Gentoo Linux forums <a class="footnote-reference" href="#forums" id="id6" name="id6">[7]</a>, and
131     marshaling community support for it. As updates are necessary, the GLEP
132     author can check in new versions if they have CVS commit permissions, or can
133     email new GLEP versions to the GLEP editors for committing.</p>
134     <p>Standards Track GLEPs consist of two parts, a design document and a reference
135     implementation. The GLEP should be reviewed and accepted before a reference
136     implementation is begun, unless a reference implementation will aid people in
137     studying the GLEP. Standards Track GLEPs must include an implementation -- in
138     the form of code, patch, or URL to same -- before it can be considered Final.</p>
139     <p>GLEP authors are responsible for collecting community feedback on a GLEP
140     before submitting it for review. A GLEP that has not been discussed on
141     <a class="reference" href="mailto:gentoo-dev&#64;gentoo.org">gentoo-dev&#64;gentoo.org</a> and/or the Gentoo Linux forums <a class="footnote-reference" href="#forums" id="id7" name="id7">[7]</a> will not be
142     accepted. However, wherever possible, long open-ended discussions on public
143     mailing lists should be avoided. Strategies to keep the discussions efficient
144     include setting up a specific forums thread for the topic, having the GLEP
145     author accept private comments in the early design phases, etc. GLEP authors
146     should use their discretion here.</p>
147     <p>Once the authors have completed a GLEP, they must inform the GLEP editors that
148 g2boojum 1.4 it is ready for review. GLEPs are reviewed by the appropriate Gentoo
149 g2boojum 1.8 Manager <a class="footnote-reference" href="#manager" id="id8" name="id8">[8]</a>, who may approve or reject a GLEP outright, or
150 g2boojum 1.1 send it back to the author(s) for revision. For a GLEP that is pre-determined
151 g2boojum 1.8 to be approvable (e.g., it is an obvious win as-is and/or its implementation
152 g2boojum 1.4 has already been checked in) the appropriate Gentoo Manager <a class="footnote-reference" href="#manager" id="id9" name="id9">[8]</a>
153 g2boojum 1.1 may also initiate a GLEP review, first notifying the GLEP author(s) and giving
154     them a chance to make revisions.</p>
155 g2boojum 1.8 <p>For a GLEP to be approved it must meet certain minimum criteria. It must be a
156 g2boojum 1.1 clear and complete description of the proposed enhancement. The enhancement
157     must represent a net improvement. The proposed implementation, if applicable,
158     must be solid and must not complicate the distribution unduly. Finally, a
159     proposed enhancement must satisfy the philosophy of Gentoo Linux.</p>
160     <p>Once a GLEP has been accepted, the reference implementation must be completed.
161     When the reference implementation is complete and accepted, the status will be
162     changed to &quot;Final&quot;.</p>
163     <p>A GLEP can also be assigned status &quot;Deferred&quot;. The GLEP author or editor can
164     assign the GLEP this status when no progress is being made on the GLEP. Once
165     a GLEP is deferred, the GLEP editor can re-assign it to draft status.</p>
166     <p>A GLEP can also be &quot;Rejected&quot;. Perhaps after all is said and done it was not
167     a good idea. It is still important to have a record of this fact.</p>
168     <p>GLEPs can also be replaced by a different GLEP, rendering the original
169     obsolete (where version 2 of a policy, for example, might replace version 1).</p>
170     <p>GLEP work flow is as follows:</p>
171     <pre class="literal-block">
172     Draft -&gt; Accepted -&gt; Final -&gt; Replaced
173     ^
174     +----&gt; Rejected
175     v
176     Deferred
177     </pre>
178     <p>Some Informational GLEPs may also have a status of &quot;Active&quot; if they are never
179     meant to be completed. E.g. GLEP 1 (this GLEP).</p>
180     </div>
181 g2boojum 1.9 <div class="section">
182     <h1><a class="toc-backref" href="#id21" id="what-belongs-in-a-successful-glep" name="what-belongs-in-a-successful-glep">What belongs in a successful GLEP?</a></h1>
183 g2boojum 1.1 <p>Each GLEP should have the following parts:</p>
184     <ol class="arabic">
185     <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
186     GLEP, including the GLEP number, a short descriptive title (limited
187     to a maximum of 44 characters), the names, and optionally the
188     contact info for each author, etc.</p>
189     </li>
190     <li><p class="first">Abstract -- a short (~200 word) description of the technical issue
191     being addressed.</p>
192     </li>
193     <li><p class="first">Motivation -- The motivation is critical for GLEPs that want to
194 g2boojum 1.4 modify Gentoo Linux functionality. It should clearly explain why the
195 g2boojum 1.1 existing functionality or policy is inadequate to address the problem that
196     the GLEP solves. GLEP submissions without sufficient motivation may be
197     rejected outright.</p>
198     </li>
199     <li><p class="first">Specification -- The technical specification should describe the
200     specific areas of Gentoo Linux that would be touched by this GLEP. If new
201     functionality is being introduced, what packages will that functionality
202     affect? If new policy, who will be affected?</p>
203     </li>
204     <li><p class="first">Rationale -- The rationale fleshes out the specification by
205     describing what motivated the design and why particular design decisions
206     were made. It should describe alternate designs that were considered and
207     related work, e.g. how the feature is supported in other distributions.</p>
208     <p>The rationale should provide evidence of consensus within the community and
209     discuss important objections or concerns raised during discussion.</p>
210     </li>
211 g2boojum 1.9 <li><p class="first">Backwards Compatibility -- All GLEPs
212 g2boojum 1.1 must include a section describing any issues of backwards incompatibilities
213     and their severity. The GLEP must explain how the author proposes to deal
214     with these incompatibilities. (Even if there are none, this section should
215     be included to clearly state that fact.) GLEP submissions without a
216     sufficient backwards compatibility treatise may be rejected outright.</p>
217     </li>
218     <li><p class="first">Reference Implementation -- The reference implementation must be
219     completed before any GLEP is given status &quot;Final&quot;, but it need not be
220     completed before the GLEP is accepted. It is better to finish the
221     specification and rationale first and reach consensus on it before writing
222     code or significantly modifying ebuilds.</p>
223     </li>
224     <li><p class="first">Copyright/public domain -- Each GLEP must either be explicitly
225     labelled as placed in the public domain (see this GLEP as an example) or
226     licensed under the Open Publication License [#OPL].</p>
227     </li>
228     </ol>
229     </div>
230 g2boojum 1.9 <div class="section">
231     <h1><a class="toc-backref" href="#id22" id="glep-formating-and-template" name="glep-formating-and-template">GLEP Formating and Template</a></h1>
232 g2boojum 1.4 <p>GLEPs are written either in Gentoo Linux Guide-XML <a class="footnote-reference" href="#guidexml" id="id10" name="id10">[11]</a> or in
233     a just-barely-marked-up version of plain ASCII text
234     called ReStructuredText <a class="footnote-reference" href="#resthome" id="id11" name="id11">[10]</a> that is then converted to HTML using
235     Docutils <a class="footnote-reference" href="#docutils" id="id12" name="id12">[12]</a>. Using ReStructuredText GLEPs allows for rich markup
236 g2boojum 1.1 that is still quite easy to read, but results in much better-looking and more
237     functional HTML. Moreover, it should be straightforward to convert GLEPs to
238 g2boojum 1.4 Gentoo Linux guide xml <a class="footnote-reference" href="#guidexml" id="id13" name="id13">[11]</a> if needed. GLEP 2 contains a boilerplate
239     template <a class="footnote-reference" href="#rest" id="id14" name="id14">[5]</a> for use with ReStructuredText GLEPs.</p>
240 g2boojum 1.1 </div>
241 g2boojum 1.9 <div class="section">
242     <h1><a class="toc-backref" href="#id23" id="glep-header-preamble" name="glep-header-preamble">GLEP Header Preamble</a></h1>
243 g2boojum 1.1 <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
244     must appear in the following order. Headers marked with &quot;*&quot; are
245     optional and are described below. All other headers are required.</p>
246     <pre class="literal-block">
247     GLEP: &lt;glep number&gt;
248     Title: &lt;glep title&gt;
249     Version: &lt;cvs version string&gt;
250     Last-Modified: &lt;cvs date string&gt;
251     Author: &lt;list of authors' real names and optionally, email addrs&gt;
252     * Discussions-To: &lt;email address&gt;
253     Status: &lt;Draft | Active | Accepted | Deferred | Rejected |
254     Final | Replaced&gt;
255     Type: &lt;Informational | Standards Track&gt;
256     * Content-Type: &lt;text/plain | text/x-rst&gt;
257     * Requires: &lt;glep numbers&gt;
258     Created: &lt;date created on, in dd-mmm-yyyy format&gt;
259     Post-History: &lt;dates of postings to gentoo-dev&gt;
260     * Replaces: &lt;glep number&gt;
261     * Replaced-By: &lt;glep number&gt;
262     </pre>
263     <p>The Author header lists the names, and optionally the email addresses
264     of all the authors/owners of the GLEP. The format of the Author header
265     value must be</p>
266     <blockquote>
267     Random J. User &lt;<a class="reference" href="mailto:address&#64;dom.ain">address&#64;dom.ain</a>&gt;</blockquote>
268     <p>if the email address is included, and just</p>
269     <blockquote>
270     Random J. User</blockquote>
271     <p>if the address is not given.</p>
272     <p>If there are multiple authors, each should be on a separate line
273     following <a class="reference" href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> continuation line conventions. Note that personal
274     email addresses in GLEPs will be obscured as a defense against spam
275     harvesters.</p>
276     <p>While a GLEP is in private discussions (usually during the initial Draft
277     phase), a Discussions-To header will indicate the mailing list or URL where
278     the GLEP is being discussed. No Discussions-To header is necessary if the
279     GLEP is being discussed privately with the author, or on the gentoo-dev
280     mailing list. Note that email addresses in the Discussions-To header will not
281     be obscured.</p>
282     <p>The Type header specifies the type of GLEP: Informational or Standards
283     Track.</p>
284 g2boojum 1.9 <p>The format of a GLEP is specified with a Content-Type header, which
285     should read &quot;text/xml&quot; for Gentoo Guide XML or
286 g2boojum 1.4 &quot;text/x-rst&quot; for ReStructuredText GLEPs (see GLEP 2
287     <a class="footnote-reference" href="#rest" id="id15" name="id15">[5]</a>).</p>
288 g2boojum 1.1 <p>The Created header records the date that the GLEP was assigned a number, while
289     Post-History is used to record the dates of when new versions of the GLEP are
290     posted to gentoo-dev. Both headers should be in dd-mmm-yyyy format, e.g.
291     14-Aug-2001.</p>
292     <p>GLEPs may have a Requires header, indicating the GLEP numbers that this GLEP
293     depends on.</p>
294     <p>GLEPs may also have a Replaced-By header indicating that a GLEP has been
295     rendered obsolete by a later document; the value is the number of the GLEP
296     that replaces the current document. The newer GLEP must have a Replaces
297     header containing the number of the GLEP that it rendered obsolete.</p>
298     </div>
299 g2boojum 1.9 <div class="section">
300     <h1><a class="toc-backref" href="#id24" id="reporting-glep-bugs-or-submitting-glep-updates" name="reporting-glep-bugs-or-submitting-glep-updates">Reporting GLEP Bugs, or Submitting GLEP Updates</a></h1>
301 g2boojum 1.1 <p>How you report a bug, or submit a GLEP update depends on several factors, such
302     as the maturity of the GLEP, the preferences of the GLEP author, and the
303     nature of your comments. For the early draft stages of the GLEP, it's
304     probably best to send your comments and changes directly to the GLEP author.
305     For more mature, or finished GLEPs you may want to submit corrections to the
306 g2boojum 1.4 Gentoo 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
307 g2boojum 1.1 author is a Gentoo Linux developer, assign the bug/patch to him, otherwise
308     assign it to the GLEP editors.</p>
309     <p>When in doubt about where to send your changes, please check first with the
310     GLEP author and/or GLEP editors.</p>
311     <p>GLEP authors who are also Gentoo Linux developers can update the GLEPs
312     themselves by using &quot;cvs commit&quot; to commit their changes.</p>
313     </div>
314 g2boojum 1.9 <div class="section">
315     <h1><a class="toc-backref" href="#id25" id="transferring-glep-ownership" name="transferring-glep-ownership">Transferring GLEP Ownership</a></h1>
316 g2boojum 1.1 <p>It occasionally becomes necessary to transfer ownership of GLEPs to a new
317     champion. In general, we'd like to retain the original author as a co-author
318     of the transferred GLEP, but that's really up to the original author. A good
319     reason to transfer ownership is because the original author no longer has the
320     time or interest in updating it or following through with the GLEP process, or
321     has fallen off the face of the 'net (i.e. is unreachable or not responding to
322     email). A bad reason to transfer ownership is because you don't agree with
323     the direction of the GLEP. We try to build consensus around a GLEP, but if
324     that's not possible, you can always submit a competing GLEP.</p>
325     <p>If you are interested in assuming ownership of a GLEP, send a message asking
326     to take over, addressed to both the original author and the GLEP editors
327     &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
328     timely manner, the GLEP editors will make a unilateral decision (it's not like
329     such decisions can't be reversed :).</p>
330     </div>
331 g2boojum 1.9 <div class="section">
332     <h1><a class="toc-backref" href="#id26" id="references-and-footnotes" name="references-and-footnotes">References and Footnotes</a></h1>
333     <table class="docutils footnote" frame="void" id="python" rules="none">
334 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
335     <tbody valign="top">
336     <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>
337     </tbody>
338     </table>
339 g2boojum 1.9 <table class="docutils footnote" frame="void" id="peps" rules="none">
340 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
341     <tbody valign="top">
342     <tr><td class="label"><a class="fn-backref" href="#id2" name="peps">[2]</a></td><td><a class="reference" href="http://www.python.org/peps">http://www.python.org/peps</a></td></tr>
343     </tbody>
344     </table>
345 g2boojum 1.9 <table class="docutils footnote" frame="void" id="pep1" rules="none">
346 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
347     <tbody valign="top">
348     <tr><td class="label"><a class="fn-backref" href="#id3" name="pep1">[3]</a></td><td><a class="reference" href="http://www.python.org/peps/pep-0001.html">http://www.python.org/peps/pep-0001.html</a></td></tr>
349     </tbody>
350     </table>
351 g2boojum 1.9 <table class="docutils footnote" frame="void" id="cvs" rules="none">
352 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
353     <tbody valign="top">
354     <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
355     for retrieving older revisions. For those without direct access to the CVS
356     tree, you can browse the current and past GLEP revisions via the Gentoo
357     Linux viewcvs web site at
358 klieber 1.5 <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>
359 g2boojum 1.1 </tbody>
360     </table>
361 g2boojum 1.9 <table class="docutils footnote" frame="void" id="rest" rules="none">
362 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
363     <tbody valign="top">
364 g2boojum 1.9 <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,
365 g2boojum 1.1 (<a class="reference" href="http://glep.gentoo.org/glep-0002.html">http://glep.gentoo.org/glep-0002.html</a>)</td></tr>
366     </tbody>
367     </table>
368 g2boojum 1.9 <table class="docutils footnote" frame="void" id="bugs" rules="none">
369 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
370     <tbody valign="top">
371 g2boojum 1.4 <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>
372 g2boojum 1.1 </tbody>
373     </table>
374 g2boojum 1.9 <table class="docutils footnote" frame="void" id="forums" rules="none">
375 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
376     <tbody valign="top">
377     <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>
378     </tbody>
379     </table>
380 g2boojum 1.9 <table class="docutils footnote" frame="void" id="manager" rules="none">
381 g2boojum 1.4 <colgroup><col class="label" /><col /></colgroup>
382     <tbody valign="top">
383     <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>
384     </tbody>
385     </table>
386 g2boojum 1.9 <table class="docutils footnote" frame="void" id="opl" rules="none">
387 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
388     <tbody valign="top">
389 g2boojum 1.4 <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>
390 g2boojum 1.1 </tbody>
391     </table>
392 g2boojum 1.9 <table class="docutils footnote" frame="void" id="resthome" rules="none">
393 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
394     <tbody valign="top">
395 g2boojum 1.4 <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>
396 g2boojum 1.1 </tbody>
397     </table>
398 g2boojum 1.9 <table class="docutils footnote" frame="void" id="guidexml" rules="none">
399 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
400     <tbody valign="top">
401 g2boojum 1.4 <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>
402 g2boojum 1.1 </tbody>
403     </table>
404 g2boojum 1.9 <table class="docutils footnote" frame="void" id="docutils" rules="none">
405 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
406     <tbody valign="top">
407 g2boojum 1.4 <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>
408 g2boojum 1.1 </tbody>
409     </table>
410     </div>
411 g2boojum 1.9 <div class="section">
412     <h1><a class="toc-backref" href="#id27" id="copyright" name="copyright">Copyright</a></h1>
413 g2boojum 1.1 <p>This document has been placed in the public domain.</p>
414     </div>
415 g2boojum 1.9
416 g2boojum 1.1 </div>
417     <div class="footer">
418 g2boojum 1.9 <hr class="footer" />
419 g2boojum 1.1 <a class="reference" href="glep-0001.txt">View document source</a>.
420 antarus 1.12 Generated on: 2008-01-20 02:56 UTC.
421 g2boojum 1.1 Generated 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.
422 g2boojum 1.9
423 g2boojum 1.1 </div>
424     </body>
425     </html>

  ViewVC Help
Powered by ViewVC 1.1.20