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

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.3 - (hide annotations) (download) (as text)
Thu Feb 9 21:53:54 2006 UTC (12 years, 10 months ago) by ciaranm
Branch: MAIN
Changes since 1.2: +21 -12 lines
File MIME type: text/html
Add the one person one vote clause to GLEP 39 as agreed.

1 g2boojum 1.1 <?xml version="1.0" encoding="utf-8" ?>
2     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3     <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4     <!--
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 g2boojum 1.2 <meta name="generator" content="Docutils 0.3.9: http://docutils.sourceforge.net/" />
12 g2boojum 1.1 <title>GLEP 39 -- An "old-school" metastructure proposal with "boot for being a slacker"</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="./glep-0039.txt">GLEP Source</a></b>]
26     </td></tr></table>
27     <table class="rfc2822 docutils field-list" frame="void" rules="none">
28     <col class="field-name" />
29     <col class="field-body" />
30     <tbody valign="top">
31     <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">39</td>
32     </tr>
33     <tr class="field"><th class="field-name">Title:</th><td class="field-body">An &quot;old-school&quot; metastructure proposal with &quot;boot for being a slacker&quot;</td>
34     </tr>
35     <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.1</td>
36     </tr>
37     <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/xml/htdocs/proj/en/glep/glep-0039.txt?cvsroot=gentoo">2005/09/01 16:31:57</a></td>
38     </tr>
39     <tr class="field"><th class="field-name">Author:</th><td class="field-body">Grant Goodyear &lt;g2boojum&#32;&#97;t&#32;gentoo.org&gt;,
40     Ciaran McCreesh &lt;ciaranm&#32;&#97;t&#32;gentoo.org&gt;,</td>
41     </tr>
42     <tr class="field"><th class="field-name">Status:</th><td class="field-body">Accepted</td>
43     </tr>
44     <tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td>
45     </tr>
46 g2boojum 1.2 <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="http://www.python.org/peps/glep-0012.html">text/x-rst</a></td>
47 g2boojum 1.1 </tr>
48     <tr class="field"><th class="field-name">Created:</th><td class="field-body">01-Sep-2005</td>
49     </tr>
50 ciaranm 1.3 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">01-Sep-2005, 09-Feb-2006</td>
51 g2boojum 1.1 </tr>
52     </tbody>
53     </table>
54     <hr />
55     <div class="contents topic" id="contents">
56     <p class="topic-title first"><a name="contents">Contents</a></p>
57     <ul class="simple">
58 ciaranm 1.3 <li><a class="reference" href="#status" id="id2" name="id2">Status</a></li>
59     <li><a class="reference" href="#abstract" id="id3" name="id3">Abstract</a></li>
60     <li><a class="reference" href="#motivation" id="id4" name="id4">Motivation</a></li>
61     <li><a class="reference" href="#specification" id="id5" name="id5">Specification</a></li>
62     <li><a class="reference" href="#rationale" id="id6" name="id6">Rationale</a></li>
63     <li><a class="reference" href="#copyright" id="id7" name="id7">Copyright</a></li>
64 g2boojum 1.1 </ul>
65     </div>
66 ciaranm 1.3 <div class="section" id="status">
67     <h1><a class="toc-backref" href="#id2" name="status">Status</a></h1>
68     <p>Implemented. GLEP amended on 09 Feb 2006 to add the final bullet point to
69     list B in <a class="reference" href="#specification">Specification</a>.</p>
70     </div>
71 g2boojum 1.1 <div class="section" id="abstract">
72 ciaranm 1.3 <h1><a class="toc-backref" href="#id3" name="abstract">Abstract</a></h1>
73 g2boojum 1.1 <p>GLEP 4 is replaced with a new &quot;metastructure&quot; that retains established
74     projects (and makes new projects easier to create), but adds a new &quot;Gentoo
75     Council&quot; to handle global (cross-project) issues.</p>
76     </div>
77     <div class="section" id="motivation">
78 ciaranm 1.3 <h1><a class="toc-backref" href="#id4" name="motivation">Motivation</a></h1>
79 g2boojum 1.1 <p>The Fosdem and subsequent reform proposals shepherded by Koon are thorough,
80     extremely detailed, and somewhat complicated. They have a lot of good ideas.
81     For many who have been with Gentoo a long time, though, there's just something
82     about them that they don't really like. More than a few Gentoo devs are
83     almost entirely uninterested in metastructure as long as it doesn't get in
84     their way, and because the current proposals impose at least some order on our
85     unruly devs these proposals are guaranteed to &quot;get in the way&quot; to some degree.
86     For example, a frequent comment that has been heard is that many Gentoo devs
87     don't know who his/her manager (or project lead) is, which is a clear
88     indication that our current system is broken. The existing proposals solve
89     the problem by requiring that each dev belong to a project. Perhaps the part
90     that is broken, though, is the belief that every dev should have a manager.
91     The history of Gentoo is such that traditionally big advances have often been
92     implemented by a single or a small number of dedicated devs (thus our
93     long-standing tradition that devs have access to the entire tree), and surely
94     we do not want to make things harder (or less fun) for such people. So here's
95     a minimal proposal for those who remembers the &quot;good ol' days&quot; and thinks
96     things aren't really so different now.</p>
97     <p>Synopsis of the current system:</p>
98     <blockquote>
99     <ul class="simple">
100     <li>There are 13-15 top-level projects (TLPs). Top-level projects are
101     comprised of sub-projects, and the goal was that every Gentoo
102     project would be a sub-project of one of the TLPs. Supposedly each
103     dev therefore belongs to one or more TLPs.</li>
104     <li>Each TLP has at least a &quot;strategic&quot; manager, and potentially also an
105     &quot;operational&quot; manager. Only the strategic managers vote on global
106     Gentoo issues.</li>
107     <li>The managers of each TLP were appointed by drobbins, the other
108     TLP managers, or elected by their project members. These managers
109     have no set term.</li>
110     <li>Within each TLP the managers are responsible for making decisions
111     about the project, defining clear goals, roadmaps, and timelines
112     for the project, and solving problems that arise within the TLP
113     (see GLEP 4 for the specific list).</li>
114     <li>The strategic TLP managers are also responsible for deciding issues that
115     affect Gentoo across project lines. The primary mechanism for
116     handling global-scope issues is the managers' meetings.</li>
117     <li>Disciplinary action taken against erring devs is handled by the
118     &quot;devrel&quot; TLP, unless the dev is a strategic TLP manager. In that
119     case disciplinary action must be enacted by the other strategic TLP
120     managers.</li>
121     </ul>
122     </blockquote>
123     <p>Problems with the existing system:</p>
124     <ol class="arabic simple">
125     <li>The assumption that TLPs are complete is either incorrect (there
126     still is no &quot;server&quot; TLP) or just plain weird (but the lack of a
127     server TLP is technically okay because all devs who don't have an
128     obvious TLP belong to the &quot;base&quot; TLP by default).</li>
129     <li>There is nothing at all to ensure that project leads actually do
130     represent the devs they supposedly lead or satisfy their
131     responsibilities. Indeed, should a TLP manager go AWOL it is not at
132     all obvious how the situation should be resolved.</li>
133     <li>Nothing is being decided at global scope right now. Some TLP strategic
134     managers rarely attend the managers' meetings, and the managers as a
135     whole certainly are not providing any sort of global vision for
136     Gentoo right now.</li>
137     <li>Even if the strategic TLP managers were making global decisions for
138     Gentoo, the TLP structure is such that almost all devs fall under
139     only one or two TLPs. Thus voting on global issues is hardly
140     proportional, and thus many devs feel disenfranchised.</li>
141     <li>Regardless of whether or not it is justified, devrel is loathed by
142     many in its enforcement role.</li>
143     </ol>
144     <p>Here's a couple of additional problems identified by the current
145     metastructure reform proposals:</p>
146     <ol class="arabic simple" start="6">
147     <li>The current system has no mechanism for identifying either projects
148     or devs that have gone inactive.</li>
149     <li>Bugs that cut across projects often remain unresolved.</li>
150     <li>GLEPs often linger in an undetermined state.</li>
151     </ol>
152     </div>
153     <div class="section" id="specification">
154 ciaranm 1.3 <h1><a class="toc-backref" href="#id5" name="specification">Specification</a></h1>
155 g2boojum 1.1 <ol class="upperalpha">
156     <li><p class="first">A project is a group of developers working towards a goal (or a set
157     of goals).</p>
158     <blockquote>
159     <ul class="simple">
160     <li>A project exists if it has a web page at
161     www.g.o/proj/en/whatever that is maintained. (&quot;Maintained&quot; means
162     that the information on the page is factually correct and not
163     out-of-date.) If the webpage isn't maintained, it is presumed dead.</li>
164     <li>It may have one or many leads, and the leads are
165     selected by the members of the project. This selection must
166     occur at least once every 12 months, and may occur at any
167     time.</li>
168     <li>It may have zero or more sub-projects. Sub-projects are
169     just projects that provide some additional structure, and their
170     web pages are in the project's space.</li>
171     <li>Not everything (or everyone) needs a project.</li>
172     <li>Projects need not be long-term.</li>
173     <li>Projects may well conflict with other projects. That's okay.</li>
174     <li>Any dev may create a new project just by creating a new page
175     (or, more realistically, directory and page) in
176     <tt class="docutils literal"><span class="pre">gentoo/xml/htdocs/proj/en</span></tt>.</li>
177     </ul>
178     </blockquote>
179     </li>
180     <li><p class="first">Global issues will be decided by an elected Gentoo council.</p>
181     <blockquote>
182     <ul class="simple">
183     <li>There will be a set number of council members. (For the
184     first election that number was set to 7 by acclamation.)</li>
185     <li>Council members will be chosen by a general election of all
186     devs once per year.</li>
187     <li>The council must hold an open meeting at least once per month.</li>
188     <li>Council decisions are by majority vote of those who show up (or
189     their proxies).</li>
190     <li>If a council member (or their appointed proxy) fails to show up for
191     two consecutive meetings, they are marked as a slacker.</li>
192     <li>If a council member who has been marked a slacker misses any further
193     meeting (or their appointed proxy doesn't show up), they lose their
194     position and a new election is held to replace that person. The newly
195     elected council member gets a 'reduced' term so that the yearly
196     elections still elect a full group.</li>
197     <li>Council members who have previously been booted for excessive slacking
198     may stand for future elections, including the election for their
199     replacement. They should, however, justify their slackerness, and
200     should expect to have it pointed out if they don't do so themselves.</li>
201     <li>The 'slacker' marker is reset when a member is elected.</li>
202     <li>If any meeting has less than 50% attendance by council members, a new
203     election for <em>all</em> places must be held within a month. The 'one year'
204     is then reset from that point.</li>
205     <li>Disciplinary actions may be appealed to the council.</li>
206 ciaranm 1.3 <li>A proxy must not be an existing council member, and any single person
207     may not be a proxy for more than one council member at any given
208     meeting.</li>
209 g2boojum 1.1 </ul>
210     </blockquote>
211     </li>
212     </ol>
213     </div>
214     <div class="section" id="rationale">
215 ciaranm 1.3 <h1><a class="toc-backref" href="#id6" name="rationale">Rationale</a></h1>
216 g2boojum 1.1 <p>So, does this proposal solve any of the previously-mentioned problems?</p>
217     <p>1. There is no longer any requirement that the project structure be
218     complete. Some devs work on very specific parts of the tree, while
219     some work on practically everything; neither should be shoehorned into
220     an ad-hoc project structure. Moreover, it should be easy to create new
221     projects where needed (and remove them when they are not), which this
222     proposal should enable.</p>
223     <p>2. By having the members choose their project leads periodically, the
224     project leads are necessarily at least somewhat responsible (and hopefully
225     responsive) to the project members. This proposal has removed the list of
226     responsibilities that project leads were supposed to satisfy, since hardly
227     anybody has ever looked at the original list since it was written. Instead
228     the practical responsibility of a lead is &quot;whatever the members require&quot;, and
229     if that isn't satisfied, the members can get a new lead (if they can find
230     somebody to take the job!).</p>
231     <p>3. If the council does a lousy job handling global issues (or has no
232     global vision), vote out the bums.</p>
233     <p>4. Since everybody gets to vote for the council members, at least in
234     principle the council members represent all developers, not just a
235     particular subset.</p>
236     <p>5. An appeal process should make disciplinary enforcement both less
237     capricious and more palatable.</p>
238     <p>6. This proposal doesn't help find inactive devs or projects. It
239     really should not be that much of a problem. We already have a script for
240     identifying devs who haven't made a CVS commit within a certain period of
241     time. As for moribund projects, if the project page isn't maintained, it's
242     dead, and we should remove it. That, too, could be automated. A much bigger
243     problem is understaffed herds, but more organization is not necessarily a
244     solution.</p>
245     <p>7. The metabug project is a great idea. Let's do that! Adding a useful
246     project shouldn't require &quot;metastructure reform&quot;, although with the
247     current system it does. With this proposal it wouldn't.</p>
248     <ol class="arabic simple" start="8">
249     <li>This proposal has nothing to say about GLEPs.</li>
250     </ol>
251     </div>
252     <div class="section" id="copyright">
253 ciaranm 1.3 <h1><a class="toc-backref" href="#id7" name="copyright">Copyright</a></h1>
254 g2boojum 1.1 <p>This document has been placed in the public domain.</p>
255     </div>
257     </div>
258     <div class="footer">
259 g2boojum 1.2 <hr class="footer" />
260 g2boojum 1.1 <a class="reference" href="glep-0039.txt">View document source</a>.
261 ciaranm 1.3 Generated on: 2006-02-09 21:53 UTC.
262 g2boojum 1.1 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.
263 g2boojum 1.2
264 g2boojum 1.1 </div>
265     </body>
266     </html>

  ViewVC Help
Powered by ViewVC 1.1.20