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

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.1 - (show annotations) (download) (as text)
Tue Jun 10 17:33:02 2003 UTC (15 years, 7 months ago) by g2boojum
Branch: MAIN
File MIME type: text/html
New glep (and a couple of date fixos).

1 <?xml version="1.0" encoding="utf-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 <!--
5 This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new
6 PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
8 -->
9 <head>
10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
11 <meta name="generator" content="Docutils 0.2.8: http://docutils.sourceforge.net/" />
12 <title>GLEP 3 -- Ebuild maintainter extension GLEP</title>
13 <link rel="stylesheet" href="tools/glep.css" type="text/css" />
14 </head>
15 <body bgcolor="white">
16 <table class="navigation" cellpadding="0" cellspacing="0"
17 width="100%" border="0">
18 <tr><td class="navicon" width="150" height="35">
19 <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
20 <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
21 border="0" width="150" height="35" /></a></td>
22 <td class="textlinks" align="left">
23 [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
24 [<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-0003.txt">GLEP Source</a></b>]
26 </td></tr></table>
27 <div class="document">
28 <table class="rfc2822 field-list" frame="void" rules="none">
29 <col class="field-name" />
30 <col class="field-body" />
31 <tbody valign="top">
32 <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">3</td>
33 </tr>
34 <tr class="field"><th class="field-name">Title:</th><td class="field-body">Ebuild maintainter extension GLEP</td>
35 </tr>
36 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.1</td>
37 </tr>
38 <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0003.txt">2003/06/10 17:31:01</a></td>
39 </tr>
40 <tr class="field"><th class="field-name">Author:</th><td class="field-body">Caleb Tennis &lt;caleb&#32;&#97;t&#32;gentoo.org&gt;</td>
41 </tr>
42 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
43 </tr>
44 <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
45 </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>
47 </tr>
48 <tr class="field"><th class="field-name">Created:</th><td class="field-body">09-Jun-2003</td>
49 </tr>
50 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">10-Jun-2003</td>
51 </tr>
52 </tbody>
53 </table>
54 <hr />
55 <div class="contents topic" id="contents">
56 <p class="topic-title"><a name="contents">Contents</a></p>
57 <ul class="simple">
58 <li><a class="reference" href="#abstract" id="id1" name="id1">Abstract</a></li>
59 <li><a class="reference" href="#motivation" id="id2" name="id2">Motivation</a></li>
60 <li><a class="reference" href="#rationale" id="id3" name="id3">Rationale</a></li>
61 <li><a class="reference" href="#backwards-compatibility" id="id4" name="id4">Backwards Compatibility</a></li>
62 <li><a class="reference" href="#implementation" id="id5" name="id5">Implementation</a></li>
63 <li><a class="reference" href="#security" id="id6" name="id6">Security</a></li>
64 <li><a class="reference" href="#future" id="id7" name="id7">Future</a></li>
65 <li><a class="reference" href="#references" id="id8" name="id8">References</a></li>
66 <li><a class="reference" href="#copyright" id="id9" name="id9">Copyright</a></li>
67 </ul>
68 </div>
69 <div class="section" id="abstract">
70 <h1><a class="toc-backref" href="#id1" name="abstract">Abstract</a></h1>
71 <p>Gentoo's portage tree attempts to provide a self contained, easy to use, and
72 automatic installation procedure for as many packages as can be maintained by
73 developers.</p>
74 <p>This GLEP proposes allowing non-core Gentoo developers to be considered as
75 ebuild maintainers sponsored via a core Gentoo developer. This system will
76 allow more ebuilds to be available in portage with active maintainers for
77 those ebuilds.</p>
78 <p>This GLEP only applies to EBUILD based bugs that contain a request for a
79 package to be committed or version bumped within portage.</p>
80 </div>
81 <div class="section" id="motivation">
82 <h1><a class="toc-backref" href="#id2" name="motivation">Motivation</a></h1>
83 <p>As of the first draft of this GLEP, there are 1387 EBUILD bug requests in
84 Gentoo's bugzilla database. Many of these requests contain ebuilds that
85 have been submitted by the bug reporter and are simply awaiting a Gentoo
86 developer to sponsor the submittal of the ebuild.</p>
87 </div>
88 <div class="section" id="rationale">
89 <h1><a class="toc-backref" href="#id3" name="rationale">Rationale</a></h1>
90 <p>Gentoo's portage tree already contains the most popular ebuilds for packages
91 available today. Many teams exist that are responsible for maintaining these
92 core ebuilds in the portage tree. But, for ebuilds that are not as commonly
93 used, there is no good focal point upon which to rest these ebuilds.</p>
94 <p>For example, any submitted ebuild that is a KDE application gets routed to the
95 KDE team. However, the KDE team may be unfamiliar with the submitted ebuild.
96 A new graphical MySQL editor may be submitted to the MYSQL team, but none of
97 the members of that team may be familiar or have the desire to learn a new
98 program to submit it to portage.</p>
99 <p>We want to be able to provide for as many ebuilds in portage as feasible and
100 make sure that all ebuilds have some person who is responsible for
101 maintenance.</p>
102 </div>
103 <div class="section" id="backwards-compatibility">
104 <h1><a class="toc-backref" href="#id4" name="backwards-compatibility">Backwards Compatibility</a></h1>
105 <p>No current policies exist that interfere with this document.</p>
106 </div>
107 <div class="section" id="implementation">
108 <h1><a class="toc-backref" href="#id5" name="implementation">Implementation</a></h1>
109 <p>Incoming ebuild bug reports should continue to be processed as normal.</p>
110 <p>Bug reports that <em>do not</em> contain an attached ebuild should be marked as
111 NEEDINFO. A message asking the user to create and submit an ebuild should be
112 attached to the bug.</p>
113 <p>Bug reports that <em>do</em> have an attached ebuild should be responded to with
114 a message asking if the reporter agrees to provide maintence and support for
115 the ebuild and package.</p>
116 <p>If a reporter <em>does not</em> agree to provide package maintence, the bug report
117 should be marked WONTFIX.</p>
118 <p>If a reporter <em>does</em> agree to provide package support, the ebuild should
119 be added to portage with a note in the ChangeLog that the reporter is
120 considered the maintainer of that particular ebuild.</p>
121 <p>Any incoming bug reports that are related to this ebuild should continue to
122 get processed as normal. The team that the ebuild goes to should then CC the
123 author of the ebuild. Optionally, if a docs-team member has prior knowledge
124 that the ebuild is externally maintained, he/she can add that person to the CC
125 list.</p>
126 </div>
127 <div class="section" id="security">
128 <h1><a class="toc-backref" href="#id6" name="security">Security</a></h1>
129 <p><strong>At the very least</strong>, all ebuilds must be looked over by the developer
130 handling the commit.</p>
131 <p>In no case should a submitted digest file be used. The developer is
132 responsible for creating the digest file based on an actual download of the
133 source code.</p>
134 <p>Potential breaches in security can still exist, however. The developer
135 handling the installation should take every step to ensure that no ebuild,
136 package, or other files have been compromised.</p>
137 </div>
138 <div class="section" id="future">
139 <h1><a class="toc-backref" href="#id7" name="future">Future</a></h1>
140 <p>Current proposals to rethink Gentoo portage and bug handling (a.k.a Herds) are
141 still in negotiation. It is the intention of the author of this GLEP to evolve
142 the concept of this GLEP as the Herds concept matures and stabilizes.</p>
143 </div>
144 <div class="section" id="references">
145 <h1><a class="toc-backref" href="#id8" name="references">References</a></h1>
146 <table class="footnote" frame="void" id="glep2" rules="none">
147 <colgroup><col class="label" /><col /></colgroup>
148 <tbody valign="top">
149 <tr><td class="label"><a name="glep2">[1]</a></td><td>GLEP 2, Sample ReStructuredText GLEP Template, Goodyear,
150 (<a class="reference" href="http://glep.gentoo.org/glep-0002.html">http://glep.gentoo.org/glep-0002.html</a>)</td></tr>
151 </tbody>
152 </table>
153 </div>
154 <div class="section" id="copyright">
155 <h1><a class="toc-backref" href="#id9" name="copyright">Copyright</a></h1>
156 <p>This document has been placed in the public domain.</p>
157 </div>
158 </div>
160 <hr class="footer"/>
161 <div class="footer">
162 <a class="reference" href="glep-0003.txt">View document source</a>.
163 Generated on: 2003-06-10 17:31 UTC.
164 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.
165 </div>
166 </body>
167 </html>

  ViewVC Help
Powered by ViewVC 1.1.20