Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status

Gentoo Archives: gentoo-doc-cvs

From: Jan Kundrat <jkt@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: management-structure.xml
Date: Thu, 28 Jul 2005 12:31:11
Message-Id: 200507281230.j6SCUY65027014@robin.gentoo.org
1 jkt 05/07/28 12:30:51
2
3 Modified: xml/htdocs/doc/en management-structure.xml
4 Log:
5 Coding style fixes (formatting & <date>), *no content change*
6
7 Revision Changes Path
8 1.16 +169 -155 xml/htdocs/doc/en/management-structure.xml
9
10 file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/management-structure.xml?rev=1.16&content-type=text/x-cvsweb-markup&cvsroot=gentoo
11 plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/management-structure.xml?rev=1.16&content-type=text/plain&cvsroot=gentoo
12 diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/management-structure.xml.diff?r1=1.15&r2=1.16&cvsroot=gentoo
13
14 Index: management-structure.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/management-structure.xml,v
17 retrieving revision 1.15
18 retrieving revision 1.16
19 diff -u -r1.15 -r1.16
20 --- management-structure.xml 24 Sep 2004 20:46:42 -0000 1.15
21 +++ management-structure.xml 28 Jul 2005 12:30:51 -0000 1.16
22 @@ -1,40 +1,49 @@
23 <?xml version='1.0' encoding="UTF-8"?>
24 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/management-structure.xml,v 1.15 2004/09/24 20:46:42 swift Exp $ -->
25 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/management-structure.xml,v 1.16 2005/07/28 12:30:51 jkt Exp $ -->
26 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
27
28 <guide link="/doc/en/management-structure.xml">
29 <title>Gentoo Top-Level Management Structure</title>
30
31 -<author title = "Author">
32 -<mail link = "drobbins@g.o">Daniel Robbins</mail></author>
33 +<author title="Author">
34 + <mail link = "drobbins@g.o">Daniel Robbins</mail>
35 +</author>
36 <author title = "Editor">
37 -<mail link = "pauldv@g.o">Paul de Vrieze</mail></author>
38 + <mail link = "pauldv@g.o">Paul de Vrieze</mail>
39 +</author>
40
41
42 -<abstract>Gentoo top-level management structure (work in progress)</abstract>
43 +<abstract>
44 +Gentoo top-level management structure (work in progress)
45 +</abstract>
46 +
47 <license/>
48 +
49 <version>1.4</version>
50 <date>20 Jul 2003</date>
51
52
53 - <chapter>
54 - <title>Gentoo top-level management structure</title>
55 - <section>
56 - <title>What was the purpose of the new management structure?</title>
57 - <body>
58 +<chapter>
59 +<title>Gentoo top-level management structure</title>
60 +<section>
61 +<title>What was the purpose of the new management structure?</title>
62 +<body>
63
64 -<impo>This document, as well as our management structure, is in "beta" and
65 +<impo>
66 +This document, as well as our management structure, is in "beta" and
67 is subject to futher improvement and clarification over time by the
68 -author.</impo>
69 +author.
70 +</impo>
71
72 -<p> The purpose of the new management structure was to solve chronic
73 +<p>
74 +The purpose of the new management structure was to solve chronic
75 management, coordination and communication issues in the Gentoo project. In
76 particular, we had no clearly defined top-level management structure, and no
77 official, regular meetings to communicate status updates between developers
78 serving in critical roles. In general, most communication took place on irc
79 and irregularly via email. There was also little to no accountability, even
80 -at a high level, to complete projects on time. </p>
81 -
82 +at a high level, to complete projects on time.
83 +</p>
84
85 <p>
86 Because of this prior state of affairs, it was difficult to set goals and
87 @@ -50,7 +59,6 @@
88 Architect for all executive decisions.
89 </p>
90
91 -
92 <p>
93 Clearly, a plan was needed to swiftly and permanently address these issues by
94 increasing communication, coordination, and accountability. Roles and scopes
95 @@ -60,14 +68,11 @@
96 efficiently and on-schedule.
97 </p>
98
99 - </body>
100 -
101 - </section>
102 - <section>
103 - <title>Initial implementation</title>
104 -
105 - <body>
106 -
107 +</body>
108 +</section>
109 +<section>
110 +<title>Initial implementation</title>
111 +<body>
112
113 <p>
114 Initial implementation of the new management structure began by creating official top-level
115 @@ -79,43 +84,48 @@
116 as well as other responsibilities detailed later in this document.
117 </p>
118
119 -
120 -<p> All the top-level projects in the Gentoo project are in the process of
121 +<p>
122 +All the top-level projects in the Gentoo project are in the process of
123 being clearly defined, including goals, sub-projects, members, roadmap and
124 schedules. The "Hardened Gentoo" page at
125 <uri>http://www.gentoo.org/proj/en/hardened/</uri> is an excellent example
126 of such a top-level project definition, and many other top-level projects
127 -currently exist today.</p>
128 -
129 +currently exist today.
130 +</p>
131
132 -<p> Certain executive decision-making authority will be granted to these
133 +<p>
134 +Certain executive decision-making authority will be granted to these
135 projects, as agreed upon by the Chief Architect, Top-level Managers and
136 project members. Then, as part of the initial implementation of the new
137 management structure, a Top-level Manager or managers will be officially
138 adopt projects and ebuild herds. These managers will be responsible for
139 tracking the status of the project, ensuring that the project meets targets
140 and is generally managed properly. Manager responsibilities are described
141 -in detail later in this document. </p>
142 -
143 +in detail later in this document.
144 +</p>
145
146 - </body>
147 +</body>
148 </section>
149 <section>
150 - <title>Management team</title>
151 - <body>
152 - <p>The current top-level management team is as follows (in no
153 - particular order):</p>
154 - <ul>
155 - <li>Seemant Kulleen (seemant)</li>
156 - <li>Jay Pfeifer (pfeifer)</li>
157 - <li>Joshua Brindle (method)</li>
158 - <li>Kurt Lieber (klieber)</li>
159 - <li>Pieter Van den Abeele (pvdabeel)</li>
160 - <li>Jon Portnoy (avenj)</li>
161 - <li>Paul de Vrieze (pauldv)</li>
162 +<title>Management team</title>
163 +<body>
164 +
165 +<p>
166 +The current top-level management team is as follows (in no particular order):
167 +</p>
168 +
169 +<ul>
170 + <li>Seemant Kulleen (seemant)</li>
171 + <li>Jay Pfeifer (pfeifer)</li>
172 + <li>Joshua Brindle (method)</li>
173 + <li>Kurt Lieber (klieber)</li>
174 + <li>Pieter Van den Abeele (pvdabeel)</li>
175 + <li>Jon Portnoy (avenj)</li>
176 + <li>Paul de Vrieze (pauldv)</li>
177 <li>Sven Vermeulen (swift)</li>
178 - </ul>
179 - </body>
180 +</ul>
181 +
182 +</body>
183 </section>
184 <section>
185 <title>Management charter</title>
186 @@ -128,21 +138,18 @@
187 manner.
188 </p>
189
190 -
191 <p>
192 2) Accountability to peers: Allow fellow members of this list to hold us
193 accountable to follow-through on projects and meet deadlines. Keep fellow
194 members accountable.
195 </p>
196
197 -
198 <p>
199 3) Management of projects: empower managers to have the authority and
200 strategic direction necessary to properly manage thier projects and efforts
201 to ensure projects complete their appointed work on time.
202 </p>
203
204 -
205 <p>
206 4) Results: our expectation is that our efforts, when properly executed,
207 will result in the Gentoo project's ability to meet deadlines, have much
208 @@ -152,7 +159,6 @@
209
210 </body>
211 </section>
212 -
213
214
215
216 --
217 gentoo-doc-cvs@g.o mailing list
Report Message
Find on MARC Find on Google Groups