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

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.7 - (show annotations) (download) (as text)
Sun Oct 14 17:00:15 2007 UTC (10 years, 8 months ago) by antarus
Branch: MAIN
Changes since 1.6: +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 3 -- Ebuild maintainter extension GLEP</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-0003.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">3</td>
28 </tr>
29 <tr class="field"><th class="field-name">Title:</th><td class="field-body">Ebuild maintainter extension GLEP</td>
30 </tr>
31 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</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-0003.txt?cvsroot=gentoo">2003/08/20 02:32:05</a></td>
34 </tr>
35 <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>
36 </tr>
37 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Deferred</td>
38 </tr>
39 <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</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">09-Jun-2003</td>
44 </tr>
45 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">10-Jun-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="#abstract" id="id1" name="id1">Abstract</a></li>
54 <li><a class="reference" href="#motivation" id="id2" name="id2">Motivation</a></li>
55 <li><a class="reference" href="#rationale" id="id3" name="id3">Rationale</a></li>
56 <li><a class="reference" href="#backwards-compatibility" id="id4" name="id4">Backwards Compatibility</a></li>
57 <li><a class="reference" href="#implementation" id="id5" name="id5">Implementation</a></li>
58 <li><a class="reference" href="#security" id="id6" name="id6">Security</a></li>
59 <li><a class="reference" href="#future" id="id7" name="id7">Future</a></li>
60 <li><a class="reference" href="#references" id="id8" name="id8">References</a></li>
61 <li><a class="reference" href="#copyright" id="id9" name="id9">Copyright</a></li>
62 </ul>
63 </div>
64 <div class="section">
65 <h1><a class="toc-backref" href="#id1" id="abstract" name="abstract">Abstract</a></h1>
66 <p>Gentoo's portage tree attempts to provide a self contained, easy to use, and
67 automatic installation procedure for as many packages as can be maintained by
68 developers.</p>
69 <p>This GLEP proposes allowing non-core Gentoo developers to be considered as
70 ebuild maintainers sponsored via a core Gentoo developer. This system will
71 allow more ebuilds to be available in portage with active maintainers for
72 those ebuilds.</p>
73 <p>This GLEP only applies to EBUILD based bugs that contain a request for a
74 package to be committed or version bumped within portage.</p>
75 </div>
76 <div class="section">
77 <h1><a class="toc-backref" href="#id2" id="motivation" name="motivation">Motivation</a></h1>
78 <p>As of the first draft of this GLEP, there are 1387 EBUILD bug requests in
79 Gentoo's bugzilla database. Many of these requests contain ebuilds that
80 have been submitted by the bug reporter and are simply awaiting a Gentoo
81 developer to sponsor the submittal of the ebuild.</p>
82 </div>
83 <div class="section">
84 <h1><a class="toc-backref" href="#id3" id="rationale" name="rationale">Rationale</a></h1>
85 <p>Gentoo's portage tree already contains the most popular ebuilds for packages
86 available today. Many teams exist that are responsible for maintaining these
87 core ebuilds in the portage tree. But, for ebuilds that are not as commonly
88 used, there is no good focal point upon which to rest these ebuilds.</p>
89 <p>For example, any submitted ebuild that is a KDE application gets routed to the
90 KDE team. However, the KDE team may be unfamiliar with the submitted ebuild.
91 A new graphical MySQL editor may be submitted to the MYSQL team, but none of
92 the members of that team may be familiar or have the desire to learn a new
93 program to submit it to portage.</p>
94 <p>We want to be able to provide for as many ebuilds in portage as feasible and
95 make sure that all ebuilds have some person who is responsible for
96 maintenance.</p>
97 </div>
98 <div class="section">
99 <h1><a class="toc-backref" href="#id4" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
100 <p>No current policies exist that interfere with this document.</p>
101 </div>
102 <div class="section">
103 <h1><a class="toc-backref" href="#id5" id="implementation" name="implementation">Implementation</a></h1>
104 <p>Incoming ebuild bug reports should continue to be processed as normal.</p>
105 <p>Bug reports that <em>do not</em> contain an attached ebuild should be marked as
106 NEEDINFO. A message asking the user to create and submit an ebuild should be
107 attached to the bug.</p>
108 <p>Bug reports that <em>do</em> have an attached ebuild should be responded to with
109 a message asking if the reporter agrees to provide maintence and support for
110 the ebuild and package.</p>
111 <p>If a reporter <em>does not</em> agree to provide package maintence, the bug report
112 should be marked WONTFIX.</p>
113 <p>If a reporter <em>does</em> agree to provide package support, the ebuild should
114 be added to portage with a note in the ChangeLog that the reporter is
115 considered the maintainer of that particular ebuild.</p>
116 <p>Any incoming bug reports that are related to this ebuild should continue to
117 get processed as normal. The team that the ebuild goes to should then CC the
118 author of the ebuild. Optionally, if a docs-team member has prior knowledge
119 that the ebuild is externally maintained, he/she can add that person to the CC
120 list.</p>
121 </div>
122 <div class="section">
123 <h1><a class="toc-backref" href="#id6" id="security" name="security">Security</a></h1>
124 <p><strong>At the very least</strong>, all ebuilds must be looked over by the developer
125 handling the commit.</p>
126 <p>In no case should a submitted digest file be used. The developer is
127 responsible for creating the digest file based on an actual download of the
128 source code.</p>
129 <p>Potential breaches in security can still exist, however. The developer
130 handling the installation should take every step to ensure that no ebuild,
131 package, or other files have been compromised.</p>
132 </div>
133 <div class="section">
134 <h1><a class="toc-backref" href="#id7" id="future" name="future">Future</a></h1>
135 <p>Current proposals to rethink Gentoo portage and bug handling (a.k.a Herds) are
136 still in negotiation. It is the intention of the author of this GLEP to evolve
137 the concept of this GLEP as the Herds concept matures and stabilizes.</p>
138 </div>
139 <div class="section">
140 <h1><a class="toc-backref" href="#id8" id="references" name="references">References</a></h1>
141 <table class="docutils footnote" frame="void" id="glep2" rules="none">
142 <colgroup><col class="label" /><col /></colgroup>
143 <tbody valign="top">
144 <tr><td class="label"><a name="glep2">[1]</a></td><td>GLEP 2, Sample ReStructuredText GLEP Template, Goodyear,
145 (<a class="reference" href="http://glep.gentoo.org/glep-0002.html">http://glep.gentoo.org/glep-0002.html</a>)</td></tr>
146 </tbody>
147 </table>
148 </div>
149 <div class="section">
150 <h1><a class="toc-backref" href="#id9" id="copyright" name="copyright">Copyright</a></h1>
151 <p>This document has been placed in the public domain.</p>
152 </div>
154 </div>
155 <div class="footer">
156 <hr class="footer" />
157 <a class="reference" href="glep-0003.txt">View document source</a>.
158 Generated on: 2007-10-13 13:39 UTC.
159 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.
161 </div>
162 </body>
163 </html>

  ViewVC Help
Powered by ViewVC 1.1.20