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

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.11 - (show annotations) (download) (as text)
Sun Oct 14 17:00:15 2007 UTC (11 years, 5 months ago) by antarus
Branch: MAIN
Changes since 1.10: +4 -251 lines
File MIME type: text/html
the canary on 53 went well, changing the rest

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

  ViewVC Help
Powered by ViewVC 1.1.20