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

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

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

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