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

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.8 - (hide annotations) (download) (as text)
Sun Apr 4 23:05:35 2004 UTC (14 years, 10 months ago) by g2boojum
Branch: MAIN
Changes since 1.7: +11 -12 lines
File MIME type: text/html
Minor fixos to GLEP 1

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

  ViewVC Help
Powered by ViewVC 1.1.20