/[gentoo]/xml/htdocs/proj/en/gdp/doc/doc-policy.xml
Gentoo

Diff of /xml/htdocs/proj/en/gdp/doc/doc-policy.xml

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

Revision 1.1 Revision 1.19
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v 1.19 2005/11/26 13:18:07 neysx Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/proj/en/gdp/doc/doc-developer-guide.xml"> 5<guide link="doc-policy.xml">
6 6
7<title>Gentoo Linux Documentation Policy</title> 7<title>Gentoo Linux Documentation Policy</title>
8<author title="Author"><mail link="zhen@gentoo.org">John P. Davis</mail></author> 8<author title="Author">
9 <mail link="zhen@gentoo.org">John P. Davis</mail>
10</author>
11<author title="Author">
12 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
13</author>
14<author title="Editor">
15 <mail link="spyderous@gentoo.org">Donnie Berkholz</mail>
16</author>
17
18<!-- The content of this document is licensed under the CC-BY-SA license -->
19<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
20
9<abstract> 21<abstract>
10 This guide explains the current Gentoo Documentation Policy. 22This document contains the Gentoo Documentation Policy, which is the
23base document which all Gentoo Documentation developers and
24Contributors should know and exercise.
11</abstract> 25</abstract>
12 26
27<license/>
28
13<version>2.1.1</version> 29<version>3.16</version>
14<date>1 April 2003</date> 30<date>2005-11-26</date>
15 31
16<chapter> 32<chapter>
17 <title>Introduction</title> 33<title>Introduction</title>
18 <section> 34<section>
19 <title>Introduction</title> 35<title>Introduction</title>
20 <body> 36<body>
21 37
38<p>
22 <p><B>The Gentoo Linux Documentation team aspires to create exceptionally professional 39The Gentoo Linux Documentation team aspires to create exceptionally
23 documentation that is immediately clear and concise to the end user</B>. In order to 40professional documentation that is immediately clear and concise to the
24 fulfill this goal, we have very specific rules and guidelines that <e>all</e> 41end user. In order to fulfill this goal, we have very specific rules and
25 documentation must go through before it is published on our website, or otherwise. 42guidelines that <e>all</e> documentation must go through prior to
26 </p> 43dissemination on our website, or elsewhere.
27 44</p>
45
28 </body> 46</body>
29 </section> 47</section>
30
31 <section> 48<section>
32 <title>Covered Topics</title> 49<title>Covered Topics</title>
33 <body> 50<body>
34 51
52<p>
35 <p>This policy will cover these topics: </p> 53This policy will cover the following topics:
36 <ul> 54</p>
55
56<ul>
37 <li>Documentation Team Organization</li> 57<li>Documentation Project Team Organization</li>
38 <li>English Developer Guidelines </li> 58<li>Documentation Guidelines</li>
39 <li>Translator Guidelines</li> 59<li>Documentation Team Recruitment</li>
40 <li>Contact Lists </li>
41 </ul> 60</ul>
42 61
43 </body> 62</body>
44 </section> 63</section>
45
46 <section>
47 <title>Preliminaries</title>
48 <body>
49 <p>Before continuing, it is expected that all documentation developers be subscribed to
50 the <i>gentoo-doc@gentoo.org</i> mailinglist, and that they are readily available in
51 <i>#gentoo-doc</i> at all times.
52 </p>
53
54 <p>Additionally, some functional definitions are needed in order to specifically outline
55 the duties and responsibilities of the documentation team. </p>
56
57 <p><b>Official Gentoo Linux Documentation</b> is simply defined as any documentation
58 that is released by Gentoo Linux for consumption by the end user. The only exceptions to
59 this are the Gentoo Weekly Newsletter, and the <i>gentoo.org</i> website, which
60 are maintained by their own respective teams. </p>
61
62 <p>Gentoo Linux Documentation can be separated into two categories, critical and
63 non-critical documentation. </p>
64
65 <p><b>Critical Documentation</b> is defined as any documentation that is <e>directly</e>
66 involved with the installation and base configuration of any Gentoo Linux system.
67 To date, our critical documents are: </p>
68
69 <ul>
70 <li>All of the Gentoo Linux Installation Guides</li>
71 <li>The Desktop Configuration Guide</li>
72 <li>The official Gentoo Linux FAQ</li>
73 <li>The Gentoo Linux Security Guide</li>
74 <li>Any Portage Documentation</li>
75 </ul>
76
77 <p><b>Non-critical</b> documentation includes all documentation not specifically defined
78 as Critical Documentation. </p>
79
80 </body>
81 </section>
82 </chapter> 64</chapter>
83 65
84<chapter> 66<chapter>
85 <title>Documentation Team Organization</title> 67<title>Documentation Project Team Organization</title>
86 <section> 68<section>
87 <title>Organization</title> 69<title>Organization</title>
88 <body> 70<body>
89 <p>The Gentoo Linux Documentation team is split into three teams that operate
90 in complete cooperation with eachother. The Documentation team is divided into
91 these three categories:
92 </p>
93 71
94 <p><b>Technical Writers: </b>The technical writers' function is to completely 72<p>
95 document every aspect of Gentoo Linux. The writers will periodically be given 73The Gentoo Documentation Project Team is split into several smaller teams
96 assignments by the Senior Developers, and those assignments are to take precedence 74that work in tandem with each other. Each smaller team represents an active
97 over any other Gentoo Linux development work. Although the writers' work is 75development team of a Gentoo Documentation Subproject.
98 ultimately proofed by the <b>Editing Team</b>, the writers <e>will still</e> 76</p>
99 proof their own work before submitting it to the <i>gentoo-docs-review@gentoo.org</i>
100 mailing list and the <b>Editing Team</b> All technical writers must be subscribed to the
101 <i>gentoo-docs-review@gentoo.org</i> mailing list.</p>
102 77
103 <p><b>Editors/ Proofreaders: </b>The editors are in charge of editing and proofing 78<p>
104 all changes to the Gentoo Linux Documentation. No change can be made unless it is 79The Gentoo Documentation Project is strategically led by a top-level Manager
105 verified to be grammatically and syntactically correct by an Editor. The Editors 80as required by the <uri link="/doc/en/management-structure.xml">Gentoo
106 must make absolutely sure that <e>all</e> documentation going live on the website 81Management Structure</uri>. This document also describes the responsibilities
107 is as professional and grammatically correct as possible. All Editors must 82of the Strategic Manager with respect to Gentoo Linux.
108 be subscribed to the <i>gentoo-docs-review@gentoo.org</i> mailing list.</p> 83</p>
109 84
110 <p><b>Translators: </b>Due to the special nature of translations, the translators 85<p>
111 are broken into their own team. Each language will have a lead Developer which will 86For day-to-day managerial tasks, the Gentoo Documentation Project has an
112 serve as the Editor and CVS publisher. Once the lead translator has deemed that 87Operational Manager. This person keeps track of all short-term tasks
113 a translation is ready to go live on the documentation index page, they may add it. 88related to documentation. The Operational Manager and Strategic Manager can be
114 After the translation is added, a notice must be sent to the <i>gentoo-docs-review@gentoo.org</i> 89one and the same if the Strategic Manager wishes so.
115 mailing list.</p> 90</p>
91
92<p>
93Currently these positions are taken by the following people:
94</p>
95
96<table>
97<tr>
98 <th>Position</th>
99 <th>Developer Name</th>
100 <th>Developer Nick</th>
101</tr>
102<tr>
103 <ti>Strategic Manager</ti>
104 <ti>Sven Vermeulen</ti>
105 <ti><mail link="swift@gentoo.org">swift</mail></ti>
106</tr>
107<tr>
108 <ti>Operational Manager</ti>
109 <ti>Xavier Neys</ti>
110 <ti><mail link="neysx@gentoo.org">neysx</mail></ti>
111</tr>
112</table>
113
114<p>
115Every subproject has a Strategic Manager of its own, and may have an
116Operational Manager if deemed appropriate. His responsibilities to the Gentoo
117Documentation Project (GDP) are listed in the <e>Manager responsibilities</e>
118section of the <uri
119link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
120Structure</uri> document.
121</p>
122
123<p>
124Every subproject of the Gentoo Documentation Team is listed on the
125<uri link="/proj/en/gdp/">GDP Webpage</uri>, along with their respective
126Strategic Managers.
127</p>
128
129<p>
130The decision on adding a subproject is in the hands of the Strategic Manager.
131</p>
132
116 </body> 133</body>
117 </section> 134</section>
135<section>
136<title>Documentation Project Team Members</title>
137<body>
138
139<p>
140Every member of the Gentoo Documentation Project must be subscribed to
141the <mail link="gentoo-doc-subscribe@gentoo.org">gentoo-doc@gentoo.org</mail>
142mailing list. This mailing list will be used to discuss all
143documentation-related issues. This mailing list is open to all interested
144parties, developer or not.
145</p>
146
147<p>
148Every member of the Gentoo Documentation Project must be part of the
149<mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. This
150alias is <e>only</e> used by <uri
151link="http://bugs.gentoo.org">bugs.gentoo.org</uri> to inform the documentation
152team about bugs regarding the Gentoo Documentation. You can add yourself by
153editing <path>/var/mail/alias/misc/docs-team</path> on dev.gentoo.org.
154</p>
155
156<p>
157Members of the Gentoo Documentation Team should be available at
158<c>#gentoo-doc</c> on <uri link="http://www.freenode.net">irc.freenode.net</uri>
159whenever they are online.
160</p>
161
162<p>
163Depending on the assignment or responsibilities, a member may have limited CVS
164access to <c>cvs.gentoo.org</c>. Full CVS access is restricted to Gentoo
165Developers. Read-only CVS access may be granted to recruits.
166</p>
167
168</body>
169</section>
170<section>
171<title>Documentation Translation Teams</title>
172<body>
173
174<p>
175Every language should be backed up by an official Translation Team. This
176team is led by a <e>Lead Translator</e> and perhaps a <e>Follow-On Lead
177Translator</e>, who both have CVS commit access. If for any reason the
178<e>Lead Translator</e> cannot perform his duties, the <e>Follow-On Lead
179Translator</e> is in charge. If the <e>Follow-On</e> is unavailable, the
180mentor(s) is/are in charge of the language.
181</p>
182
183<p>
184If a translated document for an unsupported language is contributed, the Gentoo
185Documentation Team will not publish it officially. Such documents shall not be
186linked to the website until an official Translation Team of that language is
187formed.
188</p>
189
190<p>
191When a language is officially supported, but the team does not have any
192members willing to take on the responsibilities of the <e>Lead
193Translator</e>, all links to the documents will be removed from the site.
194However, the documents will stay available in case the language becomes
195officially supported again.
196</p>
197
198<p>
199For more information Gentoo document translations, please consult the
200<uri link="/proj/en/gdp/doc/translators-howto.xml">
201Translators Howto for Gentoo Documentation</uri> and the
202<uri link="/proj/en/gdp/international.xml">
203GDP Internationalisation Subproject</uri> page.
204</p>
205
206</body>
207</section>
118</chapter> 208</chapter>
119 209
120<chapter> 210<chapter>
121 <title>English Developer Guidelines</title> 211<title>Gentoo Documentation Guidelines</title>
122 <section> 212<section>
123 <title>QA Process</title> 213<title>Legal Issues</title>
124 <body> 214<body>
125
126 <p>The English developer's job is <e>extremely</e> important, as all translations have their roots
127 in our English documentation. So, it is imperative that the process described below is followed quite
128 pedantically.
129 </p>
130 215
131 <p>If not done already, the following documents need to be read before continuing: 216<p>
132 </p> 217Every document published by the Gentoo Documentation Project must be
218licensed by the <uri
219link="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons
220Attribution-ShareAlike License</uri>.
221</p>
133 222
134 <ul> 223<p>
135 <li><uri link="http://www.gentoo.org/doc/en/xml-guide.xml">The Gentoo Linux XML Guide</uri></li> 224Every document must have the following tag inside its GuideXML
136 </ul> 225source code between the <c>&lt;/abstract&gt;</c> and the <c>&lt;version&gt;</c>
226tags:
227</p>
137 228
138 <p>The Gentoo Linux Documentation process can be broken down into several parts: 229<pre caption = "Licensing notice for the Gentoo Documentation">
139 </p> 230&lt;/abstract&gt;
140 231<i>
141 <p><b>The first step to submitting a new document or changing an existing document</b> 232&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;
142 is filing a bug on our <uri link="http://bugs.gentoo.org">Bug System</uri>. This serves 233&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;
143 as a notification to other developers and users alike that there is a work in process. 234&lt;license/&gt;
144 If there is already a bug in the database that requests a change to the documentation, 235</i>
145 a new bug does not have to be filed. 236&lt;version&gt;...&lt;/version&gt;
146 </p> 237</pre>
147 238
148 <p><b>When the proposed new document or change is completed</b>, two courses of action can
149 be taken: </p>
150
151 <p>If the change/ bugfix is technical in nature, the revised document, along with its associated
152 bug number, must be posted to the <i>gentoo-docs-review@gentoo.org</i> mailinglist for technical
153 review. This step is incredibly important, as it ensures the technical accuracy of our documentation.
154 The document in question <e>cannot</e> be committed to CVS unless it is submitted for review.</p>
155
156 <p>If the change/ bugfix is grammatical or syntactical in nature, all that is needed is a short note
157 to <i>gentoo-docs-review@gentoo.org</i> stating the bug number if applicable, and the fix. </p>
158
159 <p><b>Once the document is in CVS</b>, a Senior Developer will be notified, and the Document will
160 be posted to the live document index page. </p>
161
162 </body> 239</body>
163 </section> 240</section>
241<section>
242<title>Bugs and Updates</title>
243<body>
244
245<p>
246Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
247should be handled as fast as possible. If a bug cannot be handled
248in a timely fashion, the reporter of that bug should be informed about
249this using a comment on the bug, and the bug should be registered in the
250<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if
251applicable. The Strategic or Operational Manager may decide that a bug has a
252higher priority and should be addressed ahead any other task the assignee
253is responsible for.
254</p>
255
256<p>
257Whenever a Gentoo Documentation Team member takes care of a bug, he or
258she should assign the bug to herself/himself, but make sure that
259<c>docs-team@gentoo.org</c> is on the Cc-list. A bug may not be taken away from
260another Gentoo Documentation Team member without their approval; unless consent
261has been received from the Operational Manager.
262</p>
263
264</body>
265</section>
266<section>
267<title>Document Development</title>
268<body>
269
270<p>
271Every Gentoo Documentation Team may handle documentation development as it sees
272fit. However, when the document is finished, it should be transformed into
273<uri link="/doc/en/xml-guide.xml">GuideXML</uri> and made available on the
274Gentoo CVS infrastructure. It must also be registered in the
275<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if
276applicable.
277</p>
278
279<p>
280When a new document is started or a big change is needed, a bug should be filed
281at <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
282concerning the development of this document. If there is already a bug
283in the database that requests a change to the documentation, a new bug
284does not have to be filed. Grammatical, syntactical or small changes
285do not require a bug to be filed on <uri
286link="http://bugs.gentoo.org">bugs.gentoo.org</uri> as well.
287</p>
288
289<p>
290All changes in contents of the document, except for typo fixes in text
291itself or in the comments to code listings, should lead to version
292number (and date) increase. Note that the change of a Code Listings should
293definitely cause an increase of the version number and date.
294</p>
295
296<p>
297All changes in XML formatting should lead to version (and date) bumps only in
298case the layout of the document changes.
299</p>
300
301<p>
302Whether or not to increment the major version number instead of minor version
303number or other is up to the editor.
304</p>
305
306<p>
307Every update of a translation should copy the new version information
308verbatim from the master English document so fully synchronised
309translations have the same version information.
310</p>
311
312</body>
313</section>
314<section>
315<title>Reviewing and Committing</title>
316<body>
317
318<p>
319To maintain a high-paced documentation development cycle, technical or
320intrusive changes to documents can be propagated immediately to the document.
321This is allowed only <e>if</e> the editor is absolutely confident the changes
322are functional. If you are not absolutely confident (for instance because a
323user has told you how to fix it but you cannot verify yourself), have the
324changes reviewed by a Gentoo Developer that can verify the changes are apt.
325</p>
326
327<p>
328High-volume, technical or intrusive changes must be accompanied by a bug report
329on <uri>http://bugs.gentoo.org</uri>. This bug number <e>must</e> be mentioned
330in the CVS log to allow backtracing of changes.
331</p>
332
333<p>
334If a bugfix includes changes to content as well as internal coding changes,
335both changes must be committed separately. This allows translators to focus
336on the relevant changes regarding content and ignore the coding changes.
337</p>
338
339<p>
340If the document in question is a translation, the <e>Lead Translator</e> of the
341affected language is responsible for the document. Only the
342<e>Lead Translator</e> may commit the document to the CVS repository. However,
343if the <e>Lead Translator</e> is currently "in training", the trainee's mentor
344should commit the changes.
345</p>
346
347</body>
348</section>
349<section>
350<title>Sanctions</title>
351<body>
352
353<p>
354Malicious conduct by developers has never been an issue. However, it should be
355noted that documentation developers that misuse their position by
356</p>
357
358<ul>
359 <li>deliberately providing wrong information to users or developers</li>
360 <li>deliberately writing flawed documentation</li>
361 <li>deliberately corrupting documents</li>
362 <li>
363 deliberately go against the decisions made policy-wise or through a
364 consensus-model on the Gentoo Documentation mailinglist
365 </li>
366 <li>
367 not performing at all for a long time without informing the GDP, and without
368 replying to the Operational Manager's request for a status update
369 </li>
370</ul>
371
372<p>
373will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer
374Relations</uri> project.
375</p>
376
377</body>
378</section>
164</chapter> 379</chapter>
165 380
166
167<chapter> 381<chapter>
168 <title>Translator Guidelines</title> 382<title>Documentation Team Recruitment</title>
169 <section> 383<section>
170 <title>QA Process</title> 384<title>Contributors, Authors, Translators</title>
171 <body> 385<body>
172
173 <p>Translators will follow the English Developer's QA process, but with the following exceptions:
174 </p>
175 386
176 <p><b>Each language will have a translation team, with an Offical Gentoo Linux Translator</b> as their head. 387<p>
177 All translations will be filtered through this lead person. The lead translator will make certain that the 388Everyone interested in contributing documentation, editing existing
178 translated documents are grammatically and syntactically perfect. The lead translator will have limited CVS 389documentation, writing new documentation or translating documentation is
179 access which will enable them to commit documents in a timely manner. </p> 390welcome to join the team. There are no rules or strings attached to
180 391this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c>,
181 <p>If not done already, the following documents need to be read before continuing: 392and you have fully read this policy and understand it.
182 </p> 393</p>
183 394
184 <ul>
185 <li><uri link="http://www.gentoo.org/doc/en/xml-guide.xml">The Gentoo Linux XML Guide</uri></li>
186 </ul>
187 <p>The translator's QA process is as follows:</p>
188
189 <p><b>The first step to submitting a new document or changing an existing document</b>
190 is filing a bug on our <uri link="http://bugs.gentoo.org">Bug System</uri>. This serves
191 as a notification to other developers and users alike that there is a work in process.
192 If there is already a bug in the database that requests a change to the documentation,
193 a new bug does not have to be filed. </p>
194
195 <p><b>When the proposed new document or change is completed</b>, a notification is to be sent to the
196 translation lead, and the translation lead is to make positively sure that the translated document is
197 perfect in every way.</p>
198
199 <p><b>Once the document and or change is carefully edited by the lead translator</b>, it can be moved
200 into CVS. </p>
201
202 <p><b>Once the document is in CVS</b>, a Senior Developer will be notified, and the Document will
203 be posted to the live document index page. </p>
204 </body> 395</body>
205 </section> 396</section>
397<section>
398<title>Recruitment Process</title>
399<body>
400
401<p>
402The Documentation Project has a strict recruitment process outlined below.
403This process can not be deviated from in any circumstance. We have opted for
404this recruitment process to assure ourselves that the recruit is well informed
405about the Gentoo Documentation Policy and the Gentoo Coding Style. It has proven
406to be quite effective even though many contributors see it as a too large burden
407to cross.
408</p>
409
410<p>
411This recruitment process is meant only for requests to the Gentoo Documentation
412Repository through CVS. Being listed as the maintainer or Point-Of-Contact for a
413certain document or range of documents is granted by a simple request to the
414Operational Manager or Project Lead.
415</p>
416
417</body>
418</section>
419<section>
420<title>Phase 1: Contributions</title>
421<body>
422
423<p>
424No recruitment process starts without investigating the contributions done
425already to the Gentoo Documentation Project. The number of contributions must be
426large to assure a good knowledge of GuideXML, Coding Style and policy. The
427contribution period must be large as well to inform the contributor about the
428time-consuming position and pressure the application involves.
429</p>
430
431<p>
432The number of contributions and period over which the contributions should be
433made depends on the position which the contributor solicits for. Although it is
434difficult to write down these measurements in numbers, the following table
435should give a general overview. Final decision however lays in the hands of the
436Operational Manager.
437</p>
438
439<table>
440<tr>
441 <th>Position</th>
442 <th>Minimal Activity</th>
443 <th>Minimal Period</th>
444</tr>
445<tr>
446 <ti>Full-time Developer</ti>
447 <ti>2 updates per week</ti>
448 <ti>1 month</ti>
449</tr>
450<tr>
451 <ti>Part-time Developer</ti>
452 <ti>4 updates per month</ti>
453 <ti>1 month</ti>
454</tr>
455</table>
456
457<p>
458An update constitutes a non-trivial update to any documentation, translation or
459otherwise, completely written by the contributor and committed after review by
460any existing documentation developer. The period is fixed - increasing the
461contributions does not decrease the period. Also, we don't average the
462contributions over time to make sure the contributor doesn't give a contribution
463burst, and then waits until the Phase is over.
464</p>
465
466<p>
467Without this phase we can not know if the contributor understands what it takes
468to be a documentation developer. The validation of this activity happens through
469bugzilla reports.
470</p>
471
472<p>
473Any request for CVS access that does not allow a development activity as written
474down in the aforementioned table will not be taken into account.
475</p>
476
477<p>
478If you feel that you have shown sufficient amount of contributions, contact
479the Operational Manager of the Gentoo Documentation Project. He
480will ask you for your coordinates and other information, and then arrange
481for the next phase to be started.
482</p>
483
484</body>
485</section>
486<section>
487<title>Phase 2: Read-Only CVS Access</title>
488<body>
489
490<p>
491During phase 2, the recruit is given read-only access to the Gentoo
492Documentation Repository, allowing him to generate commit-ready patches for
493the tree. During this period, which is roughly the same as the aforementioned
494table, his patches are not edited by a documentation developer anymore, but
495are either committed as-is or refused. The recruit is also assigned to a
496full-time documentation developer (the mentor) which will guide him through
497these last phases.
498</p>
499
500<p>
501The quality of the contributions are in this phase most important - every patch
502that does not follow the Documentation Policy, Coding Style or other guideline
503that affects the document is refused.
504</p>
505
506<p>
507During this period, you:
508</p>
509
510<ul>
511 <li>
512 are advised to learn about Gentoo's inner workings.
513 This is required as you will be asked later on to answer Gentoo's <uri
514 link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
515 </li>
516 <li>
517 will be asked to fill in the <uri
518 link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project
519 Quiz</uri>. You need to successfully pass this entire quiz (all questions)
520 before you can continue with the next Phase.
521 </li>
522</ul>
523
524</body>
525</section>
526<section>
527<title>Phase 3: Gentoo Recruitment</title>
528<body>
529
530<p>
531When Phase 2 is finished, the Operational Manager will contact <uri
532link="/proj/en/devrel">Developer Relations</uri> and give a final "Go!" for the
533Gentoo recruitment process after which you will be given a Gentoo e-mail
534address and be appointed to one or more subprojects.
535</p>
536
537</body>
538</section>
206</chapter> 539</chapter>
207
208<chapter>
209 <title>Documentation Contact List</title>
210 <section>
211 <title>Contact List</title>
212
213 <body>
214
215 <p>If you have any questions, please consult the appropriate person:
216 </p>
217
218 <table>
219 <tr><th>IRC Nick</th><th>Real Name</th><th>Duties</th></tr>
220 <tr><ti>ZhEN</ti><ti><mail link="zhen@gentoo.org">John P. Davis</mail></ti><ti>Documentation Coordinator</ti></tr>
221 <tr><ti>stocke2</ti><ti><mail link="stocke2@gentoo.org">Eric Stockbridge</mail></ti><ti>Website</ti></tr>
222 <tr><ti>rajiv</ti><ti><mail link="rajiv@gentoo.org">Rajiv</mail></ti><ti>PPC Documentation/ Website</ti></tr>
223 <tr><ti>nakano</ti><ti><mail link="nakano@gentoo.org">Masatomo Nakano</mail></ti><ti>Japanese Documentation</ti></tr>
224 <tr><ti>seo</ti><ti><mail link="seo@gentoo.org">Jungmin Seo</mail></ti><ti>Bug fixing/Korean Docs</ti></tr>
225 <tr><ti>BaSS</ti><ti><mail link="bass@gentoo.org">BaSS</mail></ti><ti>Spanish Documentation</ti></tr>
226 <tr><ti>SwifT</ti><ti><mail link="swift@gentoo.org">Sven Vermeulen</mail></ti><ti>Bug Fixing/Dutch Documentation</ti></tr>
227 <tr><ti>george</ti><ti><mail link="george@gentoo.org">George Shapovalov</mail></ti><ti>Russian Documentation</ti></tr>
228 <tr><ti>Pylon</ti><ti><mail link="pylon@gentoo.org">Lars Weiler</mail></ti><ti>German Documentation</ti></tr>
229 <tr><ti>Arachne</ti><ti><mail link="arachne@gentoo.org">Guillaume Morin</mail></ti><ti>French Documentation</ti></tr>
230 </table>
231
232 </body>
233 </section>
234</chapter>
235
236</guide> 540</guide>

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.19

  ViewVC Help
Powered by ViewVC 1.1.20