/[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.7 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.7 2004/11/09 08:35:47 swift 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.8</version> 29<version>3.16</version>
31<date>November 09, 2004</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 79The Gentoo Documentation Project is strategically led by a top-level Manager
82manager as required by the 80as required by the <uri link="/doc/en/management-structure.xml">Gentoo
83<uri link="http://www.gentoo.org/doc/en/management-structure.xml">Gentoo
84Management Structure</uri>. This document also describes the responsibilities of 81Management Structure</uri>. This document also describes the responsibilities
85the strategic manager with respect to Gentoo Linux. 82of the Strategic Manager with respect to Gentoo Linux.
86</p>
87
88<p> 83</p>
84
85<p>
89For day-to-day managerial tasks the Gentoo Documentation Project has an 86For day-to-day managerial tasks, the Gentoo Documentation Project has an
90operational manager. This person keeps track of all 87Operational Manager. This person keeps track of all short-term tasks
91documentation-related tasks that are more short-term. The operational 88related to documentation. The Operational Manager and Strategic Manager can be
92manager and strategic manager can be one and the same if the strategic 89one and the same if the Strategic Manager wishes so.
93manager wishes so.
94</p> 90</p>
95 91
96<p> 92<p>
97Currently these positions are taken by the following people: 93Currently these positions are taken by the following people:
98</p> 94</p>
114 <ti><mail link="neysx@gentoo.org">neysx</mail></ti> 110 <ti><mail link="neysx@gentoo.org">neysx</mail></ti>
115</tr> 111</tr>
116</table> 112</table>
117 113
118<p> 114<p>
119Every subproject has a strategic manager of its own. he can 115Every subproject has a Strategic Manager of its own, and may have an
120have an operational manager if he deems appropriate. His 116Operational Manager if deemed appropriate. His responsibilities to the Gentoo
121responsibilities to the Gentoo Documentation Project are the same as are 117Documentation Project (GDP) are listed in the <e>Manager responsibilities</e>
122listed on the <uri 118section of the <uri
123link="http://www.gentoo.org/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo 119link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
124Management Structure</uri>. 120Structure</uri> document.
125</p>
126
127<p> 121</p>
128The subprojects of the Gentoo Documentation Team together with their 122
129respective strategic managers are listed on the <uri
130link="http://www.gentoo.org/proj/en/gdp">GDP Website</uri>.
131</p> 123<p>
132 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.
133<p> 127</p>
128
129<p>
134The 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.
135</p> 131</p>
136 132
137</body> 133</body>
138</section> 134</section>
139<section> 135<section>
147documentation-related issues. This mailing list is open to all interested 143documentation-related issues. This mailing list is open to all interested
148parties, developer or not. 144parties, developer or not.
149</p> 145</p>
150 146
151<p> 147<p>
152Every member of the Gentoo Documentation Project must be subscribed to 148Every member of the Gentoo Documentation Project must be part of the
153the <mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. 149<mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. This
154This alias is <e>only</e> used by <uri 150alias is <e>only</e> used by <uri
155link="http://bugs.gentoo.org">bugs.gentoo.org</uri> 151link="http://bugs.gentoo.org">bugs.gentoo.org</uri> to inform the documentation
156to inform the documentation team about bugs regarding the Gentoo 152team about bugs regarding the Gentoo Documentation. You can add yourself by
157Documentation. 153editing <path>/var/mail/alias/misc/docs-team</path> on dev.gentoo.org.
158</p>
159
160<p> 154</p>
155
156<p>
161Every member of the Gentoo Documentation Team should be available at 157Members of the Gentoo Documentation Team should be available at
162<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>
163whenever he is online. 159whenever they are online.
164</p>
165
166<p> 160</p>
161
162<p>
167Depending on his responsibilities, he can have limited CVS 163Depending on the assignment or responsibilities, a member may have limited CVS
168access 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
169developers. 165Developers. Read-only CVS access may be granted to recruits.
170</p> 166</p>
171 167
172</body> 168</body>
173</section> 169</section>
174<section> 170<section>
175<title>Documentation Translation Teams</title> 171<title>Documentation Translation Teams</title>
176<body> 172<body>
177 173
178<p> 174<p>
179Every language should be backed up by an official translation team. This 175Every language should be backed up by an official Translation Team. This
180team 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
181both 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
182perform 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
183even 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
184</p> 180mentor(s) is/are in charge of the language.
185
186<p> 181</p>
187If a translated document is contributed, but the language in itself is 182
188not supported, the Gentoo Documentation Team will not publish it
189officially. In this case the document will stay unlinked until an official
190translation team of that language is formed.
191</p> 183<p>
192 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.
193<p> 188</p>
189
190<p>
194When 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
195members or no one wants to take on the responsibilities of the lead 192members willing to take on the responsibilities of the <e>Lead
196translator, all links to the documents will be removed from the site. 193Translator</e>, all links to the documents will be removed from the site.
197However, the documents will stay available in case the language becomes 194However, the documents will stay available in case the language becomes
198officially supported again. 195officially supported again.
199</p> 196</p>
200 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
201</body> 206</body>
202</section> 207</section>
203</chapter> 208</chapter>
204 209
205<chapter> 210<chapter>
209<body> 214<body>
210 215
211<p> 216<p>
212Every document published by the Gentoo Documentation Project must be 217Every document published by the Gentoo Documentation Project must be
213licensed by the <uri 218licensed by the <uri
214link="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons 219link="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons
215Attribution-ShareAlike License</uri>. 220Attribution-ShareAlike License</uri>.
216</p> 221</p>
217 222
218<p> 223<p>
219Every document must have the following tag inside its GuideXML 224Every document must have the following tag inside its GuideXML
220sourcecode 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>
221tags: 226tags:
222</p> 227</p>
223 228
224<pre caption = "Licensing notice for the Gentoo Documentation"> 229<pre caption = "Licensing notice for the Gentoo Documentation">
225&lt;/abstract&gt; 230&lt;/abstract&gt;
226<i> 231<i>
227&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;
228&lt;!-- See http://creativecommons.org/licenses/by-sa/2.0 --&gt; 233&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;
229&lt;license/&gt; 234&lt;license/&gt;
230</i> 235</i>
231&lt;version&gt;...&lt;/version&gt; 236&lt;version&gt;...&lt;/version&gt;
232</pre> 237</pre>
233 238
239 244
240<p> 245<p>
241Every 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>
242should 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
243in 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
244this using a comment on the bug. The tactical or operational manager can 249this using a comment on the bug, and the bug should be registered in the
245decide that a bug has a higher priority and should be handled first before any 250<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if
246other task the assingee is responsible of. 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.
247</p> 254</p>
248 255
249<p> 256<p>
250Whenever 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
251she should assign the bug to herself/himself, but make sure that 258she should assign the bug to herself/himself, but make sure that
252<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
253of the operational manager, a bug may not be taken away from another
254Gentoo Documentation Team member without their approval. 260another Gentoo Documentation Team member without their approval; unless consent
261has been received from the Operational Manager.
255</p> 262</p>
256 263
257</body> 264</body>
258</section> 265</section>
259<section> 266<section>
260<title>Document Development</title> 267<title>Document Development</title>
261<body> 268<body>
262 269
263<p> 270<p>
264Every document the Gentoo Documentation Team develops can be developed 271Every Gentoo Documentation Team may handle documentation development as it sees
265as the related parties see fit. However, when the document is finished, 272fit. However, when the document is finished, it should be transformed into
266it should be transformed into <uri 273<uri link="/doc/en/xml-guide.xml">GuideXML</uri> and made available on the
267link="http://www.gentoo.org/doc/en/xml-guide.xml">GuideXML</uri>. 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.
268</p> 277</p>
269 278
270<p> 279<p>
271When a new document is started or a big change is needed, a bug should be filed 280When a new document is started or a big change is needed, a bug should be filed
272at <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> 281at <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
283number (and date) increase. Note that the change of a Code Listings should 292number (and date) increase. Note that the change of a Code Listings should
284definitely cause an increase of the version number and date. 293definitely cause an increase of the version number and date.
285</p> 294</p>
286 295
287<p> 296<p>
288When updating a handbook-related file (such as the various
289<path>hb-*</path> files) you must bump the parental
290<path>handbook-&lt;arch&gt;.xml</path> file as well and commit all files at
291once (which also means an identical commit message).
292</p>
293
294<p>
295All changes in XML formatting should lead to version (and date) bumps only in 297All changes in XML formatting should lead to version (and date) bumps only in
296case the layout of the document changes. 298case the layout of the document changes.
297</p> 299</p>
298 300
299<p> 301<p>
312<section> 314<section>
313<title>Reviewing and Committing</title> 315<title>Reviewing and Committing</title>
314<body> 316<body>
315 317
316<p> 318<p>
317To keep a high-pace development cycle of the documentation, technical or 319To maintain a high-paced documentation development cycle, technical or
318intrusive changes to documents can be propagated immediately to the document 320intrusive changes to documents can be propagated immediately to the document.
319<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
320you 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
321it 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
322Developer that can verify the change. 324changes reviewed by a Gentoo Developer that can verify the changes are apt.
323</p>
324
325<p> 325</p>
326
327<p>
326High volume, technical or intrusive changes must be accompanied by a bugreport 328High-volume, technical or intrusive changes must be accompanied by a bug report
327on <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
328the CVS log to allow backtracing of changes. 330in the CVS log to allow backtracing of changes.
329</p>
330
331<p> 331</p>
332If a bugfix consists out of both content as internal coding changes, 332
333both changes must be committed seperately so that translators can easily
334view the important changes (content) and ignore the coding changes.
335</p> 333<p>
336 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> 337</p>
338In case of a translation, the lead translator of the language is 338
339responsible for the document. Only he may commit the document to CVS 339<p>
340unless 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
341mentor 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.
342</p> 345</p>
343 346
344</body> 347</body>
345</section> 348</section>
346<section> 349<section>
347<title>Sanctions</title> 350<title>Sanctions</title>
348<body> 351<body>
349 352
350<p> 353<p>
351Although 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
352the policy - even though it is hateful. Anyway, documentation developers that 355noted that documentation developers that misuse their position by
353misuse their position by
354</p> 356</p>
355 357
356<ul> 358<ul>
357 <li>deliberately providing wrong information to users or developers</li> 359 <li>deliberately providing wrong information to users or developers</li>
358 <li>deliberately writing flawed documentation</li> 360 <li>deliberately writing flawed documentation</li>
360 <li> 362 <li>
361 deliberately go against the decisions made policy-wise or through a 363 deliberately go against the decisions made policy-wise or through a
362 consensus-model on the Gentoo Documentation mailinglist 364 consensus-model on the Gentoo Documentation mailinglist
363 </li> 365 </li>
364 <li> 366 <li>
365 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
366 replying to the operational manager's request for a status update 368 replying to the Operational Manager's request for a status update
367 </li> 369 </li>
368</ul> 370</ul>
369 371
370<p> 372<p>
371will be reported to the <uri link="/proj/en/devrel">Gentoo Developer 373will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer
372Relations</uri> project. 374Relations</uri> project.
373</p> 375</p>
374 376
375</body> 377</body>
376</section> 378</section>
377</chapter> 379</chapter>
378 380
379<chapter> 381<chapter>
380<title>Documentation Team Recruitement</title> 382<title>Documentation Team Recruitment</title>
381<section> 383<section>
382<title>Contributors, Authors, Translators</title> 384<title>Contributors, Authors, Translators</title>
383<body> 385<body>
384 386
385<p> 387<p>
386Everyone interested in contributing documentation, editing existing 388Everyone interested in contributing documentation, editing existing
387documentation, writing new documentation or translating documentation is 389documentation, writing new documentation or translating documentation is
388welcome 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
389this. 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>,
390and you have fully read this policy and understand it. 392and you have fully read this policy and understand it.
391</p> 393</p>
392 394
393</body> 395</body>
394</section> 396</section>
395<section> 397<section>
396<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
397<body> 417</body>
418</section>
419<section>
420<title>Phase 1: Contributions</title>
421<body>
398 422
399<p>
400As a Gentoo documentation developer should know everything in the <uri
401link="/proj/en/devrel/handbook/handbook.xml?part=3&amp;chap=1">Gentoo Ebuild
402Policy</uri> even though you're not submitting ebuilds. This is all needed to
403ensure our userbase that no Gentoo developer gives wrong information about
404critical things.
405</p> 423<p>
406 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.
407<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
408Contact the operational manager of the Gentoo Documentation Project. He 479the Operational Manager of the Gentoo Documentation Project. He
409will ask you for your coordinates and other information and then arrange 480will ask you for your coordinates and other information, and then arrange
410a mentor for you who will guide you through the first days or weeks as 481for the next phase to be started.
411developer.
412</p>
413
414<p> 482</p>
415You will be given a Gentoo e-mail address and be appointed to one or
416more subprojects. During the initial days or weeks, you should ask your
417mentor as much as possible, preferably have him double-check everything
418you do. If your function requires CVS access, you will only receive it
419when your mentor deems it appropriate. Until then, your mentor is in
420charge of the CVS commits.
421</p>
422 483
423</body> 484</body>
424</section>
425<section> 485</section>
426<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
427<body> 524</body>
525</section>
526<section>
527<title>Phase 3: Gentoo Recruitment</title>
528<body>
428 529
429<p>
430Becoming a (follow-up) lead translator shouldn't be held lightly. You are
431responsible for every translated document and final reviewing. The lead
432translator will make certain that the translated documents are
433grammatically and syntactically perfect.
434</p> 530<p>
435 531When Phase 2 is finished, the Operational Manager will contact <uri
436<p> 532link="/proj/en/devrel">Developer Relations</uri> and give a final "Go!" for the
437In 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
438developer. 534address and be appointed to one or more subprojects.
439</p>
440
441<p>
442During your "training" period you are a (follow-up) lead translator and
443should act upon it. All guidelines regarding (follow-up) lead translators
444apply.
445</p> 535</p>
446 536
447</body> 537</body>
448</section> 538</section>
449</chapter> 539</chapter>

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

  ViewVC Help
Powered by ViewVC 1.1.20