/[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.9 Revision 1.19
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v 1.9 2005/01/07 23:02:29 neysx Exp $ --> 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
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 4
6<guide link="doc-policy.xml"> 5<guide link="doc-policy.xml">
7 6
8<title>Gentoo Linux Documentation Policy</title> 7<title>Gentoo Linux Documentation Policy</title>
15<author title="Editor"> 14<author title="Editor">
16 <mail link="spyderous@gentoo.org">Donnie Berkholz</mail> 15 <mail link="spyderous@gentoo.org">Donnie Berkholz</mail>
17</author> 16</author>
18 17
19<!-- The content of this document is licensed under the CC-BY-SA license --> 18<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 19<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21 20
22<abstract> 21<abstract>
23This document contains the Gentoo Documentation Policy, which is the 22This document contains the Gentoo Documentation Policy, which is the
24base document which all Gentoo Documentation developers and 23base document which all Gentoo Documentation developers and
25Contributers should know and exercise. 24Contributors should know and exercise.
26</abstract> 25</abstract>
27 26
28<license/> 27<license/>
29 28
30<version>3.10</version> 29<version>3.16</version>
31<date>2005-01-08</date> 30<date>2005-11-26</date>
32 31
33<chapter> 32<chapter>
34<title>Introduction</title> 33<title>Introduction</title>
35<section> 34<section>
36<title>Introduction</title> 35<title>Introduction</title>
38 37
39<p> 38<p>
40The Gentoo Linux Documentation team aspires to create exceptionally 39The Gentoo Linux Documentation team aspires to create exceptionally
41professional documentation that is immediately clear and concise to the 40professional documentation that is immediately clear and concise to the
42end user. In order to fulfill this goal, we have very specific rules and 41end user. In order to fulfill this goal, we have very specific rules and
43guidelines that <e>all</e> documentation must go through before it is 42guidelines that <e>all</e> documentation must go through prior to
44published on our website, or otherwise. 43dissemination on our website, or elsewhere.
45</p> 44</p>
46 45
47</body> 46</body>
48</section> 47</section>
49<section> 48<section>
50<title>Covered Topics</title> 49<title>Covered Topics</title>
51<body> 50<body>
52 51
53<p> 52<p>
54This policy will cover these topics: 53This policy will cover the following topics:
55</p> 54</p>
56 55
57<ul> 56<ul>
58<li>Documentation Project Team Organization</li> 57<li>Documentation Project Team Organization</li>
59<li>Documentation Guidelines</li> 58<li>Documentation Guidelines</li>
60<li>Documentation Team Recruitement</li> 59<li>Documentation Team Recruitment</li>
61</ul> 60</ul>
62 61
63</body> 62</body>
64</section> 63</section>
65</chapter> 64</chapter>
70<title>Organization</title> 69<title>Organization</title>
71<body> 70<body>
72 71
73<p> 72<p>
74The Gentoo Documentation Project Team is split into several smaller teams 73The Gentoo Documentation Project Team is split into several smaller teams
75that operate in complete cooperation with each other. Each smaller team 74that work in tandem with each other. Each smaller team represents an active
76represents an active development team of a Gentoo Documentation 75development team of a Gentoo Documentation Subproject.
77Subproject.
78</p>
79
80<p> 76</p>
77
78<p>
81The Gentoo Documentation Project is strategically lead by a top-level manager 79The Gentoo Documentation Project is strategically led by a top-level Manager
82as required by the <uri link="/doc/en/management-structure.xml">Gentoo 80as required by the <uri link="/doc/en/management-structure.xml">Gentoo
83Management Structure</uri>. This document also describes the responsibilities 81Management Structure</uri>. This document also describes the responsibilities
84of the strategic manager with respect to Gentoo Linux. 82of the Strategic Manager with respect to Gentoo Linux.
85</p>
86
87<p> 83</p>
84
85<p>
88For day-to-day managerial tasks the Gentoo Documentation Project has an 86For day-to-day managerial tasks, the Gentoo Documentation Project has an
89operational manager. This person keeps track of all documentation-related tasks 87Operational Manager. This person keeps track of all short-term tasks
90that are more short-term. The operational manager and strategic manager can be 88related to documentation. The Operational Manager and Strategic Manager can be
91one and the same if the strategic manager wishes so. 89one and the same if the Strategic Manager wishes so.
92</p> 90</p>
93 91
94<p> 92<p>
95Currently these positions are taken by the following people: 93Currently these positions are taken by the following people:
96</p> 94</p>
112 <ti><mail link="neysx@gentoo.org">neysx</mail></ti> 110 <ti><mail link="neysx@gentoo.org">neysx</mail></ti>
113</tr> 111</tr>
114</table> 112</table>
115 113
116<p> 114<p>
117Every subproject has a strategic manager of its own. he can have an operational 115Every subproject has a Strategic Manager of its own, and may have an
118manager if he deems appropriate. His responsibilities to the Gentoo 116Operational Manager if deemed appropriate. His responsibilities to the Gentoo
119Documentation Project are the same as are listed on the <uri 117Documentation Project (GDP) are listed in the <e>Manager responsibilities</e>
118section of the <uri
120link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management 119link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
121Structure</uri>. 120Structure</uri> document.
122</p>
123
124<p> 121</p>
125The subprojects of the Gentoo Documentation Team together with their respective 122
126strategic managers are listed on the <uri link="/proj/en/gdp/">GDP
127Website</uri>.
128</p> 123<p>
129 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.
130<p> 127</p>
128
129<p>
131The decision on adding subprojects is in hands of the strategic manager. 130The decision on adding a subproject is in the hands of the Strategic Manager.
132</p> 131</p>
133 132
134</body> 133</body>
135</section> 134</section>
136<section> 135<section>
144documentation-related issues. This mailing list is open to all interested 143documentation-related issues. This mailing list is open to all interested
145parties, developer or not. 144parties, developer or not.
146</p> 145</p>
147 146
148<p> 147<p>
149Every member of the Gentoo Documentation Project must be subscribed to the 148Every member of the Gentoo Documentation Project must be part of the
150<mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. This 149<mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. This
151alias is <e>only</e> used by <uri 150alias is <e>only</e> used by <uri
152link="http://bugs.gentoo.org">bugs.gentoo.org</uri> to inform the documentation 151link="http://bugs.gentoo.org">bugs.gentoo.org</uri> to inform the documentation
153team about bugs regarding the Gentoo Documentation. 152team about bugs regarding the Gentoo Documentation. You can add yourself by
154</p> 153editing <path>/var/mail/alias/misc/docs-team</path> on dev.gentoo.org.
155
156<p> 154</p>
155
156<p>
157Every member of the Gentoo Documentation Team should be available at 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> 158<c>#gentoo-doc</c> on <uri link="http://www.freenode.net">irc.freenode.net</uri>
159whenever he is online. 159whenever they are online.
160</p>
161
162<p> 160</p>
161
162<p>
163Depending on his responsibilities, he can have limited CVS 163Depending on the assignment or responsibilities, a member may have limited CVS
164access to <c>cvs.gentoo.org</c>. CVS access can only be given to Gentoo 164access to <c>cvs.gentoo.org</c>. Full CVS access is restricted to Gentoo
165developers. 165Developers. Read-only CVS access may be granted to recruits.
166</p> 166</p>
167 167
168</body> 168</body>
169</section> 169</section>
170<section> 170<section>
171<title>Documentation Translation Teams</title> 171<title>Documentation Translation Teams</title>
172<body> 172<body>
173 173
174<p> 174<p>
175Every language should be backed up by an official translation team. This 175Every language should be backed up by an official Translation Team. This
176team is lead by a lead translator and perhaps a follow-up lead translator, who 176team is led by a <e>Lead Translator</e> and perhaps a <e>Follow-On Lead
177both have CVS commit access. If for any reason the lead translator cannot 177Translator</e>, who both have CVS commit access. If for any reason the
178perform his or her duties, the follow-up lead translator is in charge. If 178<e>Lead Translator</e> cannot perform his duties, the <e>Follow-On Lead
179even this person is unavailable, the mentor(s) is/are in charge of the language. 179Translator</e> is in charge. If the <e>Follow-On</e> is unavailable, the
180</p> 180mentor(s) is/are in charge of the language.
181
182<p> 181</p>
183If a translated document is contributed, but the language in itself is 182
184not supported, the Gentoo Documentation Team will not publish it
185officially. In this case the document will stay unlinked until an official
186translation team of that language is formed.
187</p> 183<p>
188 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.
189<p> 188</p>
189
190<p>
190When a language is officially supported, but the team doesn't have any 191When a language is officially supported, but the team does not have any
191members or no one wants to take on the responsibilities of the lead 192members willing to take on the responsibilities of the <e>Lead
192translator, all links to the documents will be removed from the site. 193Translator</e>, all links to the documents will be removed from the site.
193However, the documents will stay available in case the language becomes 194However, the documents will stay available in case the language becomes
194officially supported again. 195officially supported again.
195</p> 196</p>
196 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
197</body> 206</body>
198</section> 207</section>
199</chapter> 208</chapter>
200 209
201<chapter> 210<chapter>
205<body> 214<body>
206 215
207<p> 216<p>
208Every document published by the Gentoo Documentation Project must be 217Every document published by the Gentoo Documentation Project must be
209licensed by the <uri 218licensed by the <uri
210link="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons 219link="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons
211Attribution-ShareAlike License</uri>. 220Attribution-ShareAlike License</uri>.
212</p> 221</p>
213 222
214<p> 223<p>
215Every document must have the following tag inside its GuideXML 224Every document must have the following tag inside its GuideXML
216sourcecode between the <c>&lt;/abstract&gt;</c> and the <c>&lt;version&gt;</c> 225source code between the <c>&lt;/abstract&gt;</c> and the <c>&lt;version&gt;</c>
217tags: 226tags:
218</p> 227</p>
219 228
220<pre caption = "Licensing notice for the Gentoo Documentation"> 229<pre caption = "Licensing notice for the Gentoo Documentation">
221&lt;/abstract&gt; 230&lt;/abstract&gt;
222<i> 231<i>
223&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt; 232&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;
224&lt;!-- See http://creativecommons.org/licenses/by-sa/2.0 --&gt; 233&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;
225&lt;license/&gt; 234&lt;license/&gt;
226</i> 235</i>
227&lt;version&gt;...&lt;/version&gt; 236&lt;version&gt;...&lt;/version&gt;
228</pre> 237</pre>
229 238
235 244
236<p> 245<p>
237Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> 246Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
238should be handled as fast as possible. If a bug cannot be handled 247should be handled as fast as possible. If a bug cannot be handled
239in a timely fashion, the reporter of that bug should be informed about 248in a timely fashion, the reporter of that bug should be informed about
240this using a comment on the bug and the bug should be registered in the 249this using a comment on the bug, and the bug should be registered in the
241<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if 250<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if
242applicable. The tactical or operational manager can decide that a bug has a 251applicable. The Strategic or Operational Manager may decide that a bug has a
243higher priority and should be handled first before any other task the assingee 252higher priority and should be addressed ahead any other task the assignee
244is responsible of. 253is responsible for.
245</p> 254</p>
246 255
247<p> 256<p>
248Whenever a Gentoo Documentation Team member takes care of a bug, he or 257Whenever a Gentoo Documentation Team member takes care of a bug, he or
249she should assign the bug to herself/himself, but make sure that 258she should assign the bug to herself/himself, but make sure that
250<c>docs-team@gentoo.org</c> is on the Cc-list. Unless with the consent 259<c>docs-team@gentoo.org</c> is on the Cc-list. A bug may not be taken away from
251of the operational manager, a bug may not be taken away from another
252Gentoo Documentation Team member without their approval. 260another Gentoo Documentation Team member without their approval; unless consent
261has been received from the Operational Manager.
253</p> 262</p>
254 263
255</body> 264</body>
256</section> 265</section>
257<section> 266<section>
258<title>Document Development</title> 267<title>Document Development</title>
259<body> 268<body>
260 269
261<p> 270<p>
262Every document the Gentoo Documentation Team develops can be developed as the 271Every Gentoo Documentation Team may handle documentation development as it sees
263related parties see fit. However, when the document is finished, it should be 272fit. However, when the document is finished, it should be transformed into
264transformed into <uri link="/doc/en/xml-guide.xml">GuideXML</uri> and put 273<uri link="/doc/en/xml-guide.xml">GuideXML</uri> and made available on the
265available on the Gentoo CVS infrastructure. It must also be registered in the 274Gentoo CVS infrastructure. It must also be registered in the
266<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if 275<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if
267applicable. 276applicable.
268</p> 277</p>
269 278
270<p> 279<p>
305<section> 314<section>
306<title>Reviewing and Committing</title> 315<title>Reviewing and Committing</title>
307<body> 316<body>
308 317
309<p> 318<p>
310To keep a high-pace development cycle of the documentation, technical or 319To maintain a high-paced documentation development cycle, technical or
311intrusive changes to documents can be propagated immediately to the document 320intrusive changes to documents can be propagated immediately to the document.
312<e>if</e> the editor is 100% confident his changes are correct and working. If 321This is allowed only <e>if</e> the editor is absolutely confident the changes
313you are not 100% confident (for instance because a user has told you how to fix 322are functional. If you are not absolutely confident (for instance because a
314it but you cannot verify yourself), have the change reviewed by a Gentoo 323user has told you how to fix it but you cannot verify yourself), have the
315Developer that can verify the change. 324changes reviewed by a Gentoo Developer that can verify the changes are apt.
316</p>
317
318<p> 325</p>
326
327<p>
319High volume, technical or intrusive changes must be accompanied by a bugreport 328High-volume, technical or intrusive changes must be accompanied by a bug report
320on <uri>http://bugs.gentoo.org</uri>. This bugnumber <e>must</e> be mentioned in 329on <uri>http://bugs.gentoo.org</uri>. This bug number <e>must</e> be mentioned
321the CVS log to allow backtracing of changes. 330in the CVS log to allow backtracing of changes.
322</p>
323
324<p> 331</p>
325If a bugfix consists out of both content as internal coding changes, 332
326both changes must be committed seperately so that translators can easily
327view the important changes (content) and ignore the coding changes.
328</p> 333<p>
329 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.
330<p> 337</p>
331In case of a translation, the lead translator of the language is 338
332responsible for the document. Only he may commit the document to CVS 339<p>
333unless he is currently "in training", in which case his or her 340If the document in question is a translation, the <e>Lead Translator</e> of the
334mentor should commit it. 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.
335</p> 345</p>
336 346
337</body> 347</body>
338</section> 348</section>
339<section> 349<section>
340<title>Sanctions</title> 350<title>Sanctions</title>
341<body> 351<body>
342 352
343<p> 353<p>
344Although this has never been necessary, it is still important to list this in 354Malicious conduct by developers has never been an issue. However, it should be
345the policy - even though it is hateful. Anyway, documentation developers that 355noted that documentation developers that misuse their position by
346misuse their position by
347</p> 356</p>
348 357
349<ul> 358<ul>
350 <li>deliberately providing wrong information to users or developers</li> 359 <li>deliberately providing wrong information to users or developers</li>
351 <li>deliberately writing flawed documentation</li> 360 <li>deliberately writing flawed documentation</li>
353 <li> 362 <li>
354 deliberately go against the decisions made policy-wise or through a 363 deliberately go against the decisions made policy-wise or through a
355 consensus-model on the Gentoo Documentation mailinglist 364 consensus-model on the Gentoo Documentation mailinglist
356 </li> 365 </li>
357 <li> 366 <li>
358 not performing at all for a long time without informing the GDP and without 367 not performing at all for a long time without informing the GDP, and without
359 replying to the operational manager's request for a status update 368 replying to the Operational Manager's request for a status update
360 </li> 369 </li>
361</ul> 370</ul>
362 371
363<p> 372<p>
364will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer 373will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer
368</body> 377</body>
369</section> 378</section>
370</chapter> 379</chapter>
371 380
372<chapter> 381<chapter>
373<title>Documentation Team Recruitement</title> 382<title>Documentation Team Recruitment</title>
374<section> 383<section>
375<title>Contributors, Authors, Translators</title> 384<title>Contributors, Authors, Translators</title>
376<body> 385<body>
377 386
378<p> 387<p>
379Everyone interested in contributing documentation, editing existing 388Everyone interested in contributing documentation, editing existing
380documentation, writing new documentation or translating documentation is 389documentation, writing new documentation or translating documentation is
381welcome to join the team. There are no rules or strings attached to 390welcome to join the team. There are no rules or strings attached to
382this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c> 391this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c>,
383and you have fully read this policy and understand it. 392and you have fully read this policy and understand it.
384</p> 393</p>
385 394
386</body> 395</body>
387</section> 396</section>
388<section> 397<section>
389<title>Gentoo Documentation Developer</title> 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
390<body> 417</body>
418</section>
419<section>
420<title>Phase 1: Contributions</title>
421<body>
391 422
392<p>
393As a Gentoo documentation developer should know everything in the <uri
394link="/proj/en/devrel/handbook/handbook.xml?part=3&amp;chap=1">Gentoo Ebuild
395Policy</uri> even though you're not submitting ebuilds. This is all needed to
396ensure our userbase that no Gentoo developer gives wrong information about
397critical things.
398</p> 423<p>
399 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.
400<p> 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
401Contact the operational manager of the Gentoo Documentation Project. He 479the Operational Manager of the Gentoo Documentation Project. He
402will ask you for your coordinates and other information and then arrange 480will ask you for your coordinates and other information, and then arrange
403a mentor for you who will guide you through the first days or weeks as 481for the next phase to be started.
404developer.
405</p>
406
407<p> 482</p>
408You will be given a Gentoo e-mail address and be appointed to one or
409more subprojects. During the initial days or weeks, you should ask your
410mentor as much as possible, preferably have him double-check everything
411you do. If your function requires CVS access, you will only receive it
412when your mentor deems it appropriate. Until then, your mentor is in
413charge of the CVS commits.
414</p>
415 483
416</body> 484</body>
417</section>
418<section> 485</section>
419<title>(Follow-Up) Lead Translator</title> 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
420<body> 524</body>
525</section>
526<section>
527<title>Phase 3: Gentoo Recruitment</title>
528<body>
421 529
422<p>
423Becoming a (follow-up) lead translator shouldn't be held lightly. You are
424responsible for every translated document and final reviewing. The lead
425translator will make certain that the translated documents are
426grammatically and syntactically perfect.
427</p> 530<p>
428 531When Phase 2 is finished, the Operational Manager will contact <uri
429<p> 532link="/proj/en/devrel">Developer Relations</uri> and give a final "Go!" for the
430In order to become a Gentoo (follow-up) lead translator you must be a Gentoo 533Gentoo recruitment process after which you will be given a Gentoo e-mail
431developer. 534address and be appointed to one or more subprojects.
432</p>
433
434<p>
435During your "training" period you are a (follow-up) lead translator and
436should act upon it. All guidelines regarding (follow-up) lead translators
437apply.
438</p> 535</p>
439 536
440</body> 537</body>
441</section> 538</section>
442</chapter> 539</chapter>

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

  ViewVC Help
Powered by ViewVC 1.1.20