/[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.14 - (hide annotations) (download) (as text)
Thu Mar 10 20:53:02 2011 UTC (3 years, 4 months ago) by vapier
Branch: MAIN
Changes since 1.13: +90 -93 lines
File MIME type: text/html
update glep 1 to reflect the Gentoo Council workflow rather than the old Managers

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

  ViewVC Help
Powered by ViewVC 1.1.20