/[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.12 Revision 1.21
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.12 2005/05/12 09:56:52 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v 1.21 2006/07/08 17:21:18 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>
9<author title="Author"> 8<author title="Author">
10 <mail link="zhen@gentoo.org">John P. Davis</mail> 9 <mail link="zhen@gentoo.org">John P. Davis</mail>
11</author> 10</author>
12<author title="Author"> 11<author title="Author">
13 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 12 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
14</author> 13</author>
15<author title="Editor"> 14<author title="Editor">
16 <mail link="spyderous@gentoo.org">Donnie Berkholz</mail> 15 <mail link="dberkholz@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.11</version> 29<version>3.17</version>
31<date>2005-05-07</date> 30<date>2005-12-22</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>
37<body> 36<body>
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<!--
79<p>
81The Gentoo Documentation Project is strategically lead by a top-level manager 80The Gentoo Documentation Project is strategically led by a top-level Manager
82as required by the <uri link="/doc/en/management-structure.xml">Gentoo 81as required by the <uri link="/doc/en/management-structure.xml">Gentoo
83Management Structure</uri>. This document also describes the responsibilities 82Management Structure</uri>. This document also describes the responsibilities
84of the strategic manager with respect to Gentoo Linux. 83of the Strategic Manager with respect to Gentoo Linux.
85</p>
86
87<p> 84</p>
85-->
86
87<p>
88For day-to-day managerial tasks the Gentoo Documentation Project has an 88For day-to-day managerial tasks, the Gentoo Documentation Project has an
89operational manager. This person keeps track of all documentation-related tasks 89Operational Manager. This person keeps track of all short-term tasks
90that are more short-term. The operational manager and strategic manager can be 90related to documentation. The Operational Manager and Strategic Manager can be
91one and the same if the strategic manager wishes so. 91one and the same if the Strategic Manager wishes so.
92</p> 92</p>
93 93
94<p> 94<p>
95Currently these positions are taken by the following people: 95Currently these positions are taken by the following people:
96</p> 96</p>
112 <ti><mail link="neysx@gentoo.org">neysx</mail></ti> 112 <ti><mail link="neysx@gentoo.org">neysx</mail></ti>
113</tr> 113</tr>
114</table> 114</table>
115 115
116<p> 116<p>
117Every subproject has a strategic manager of its own. he can have an operational 117Every subproject has a Strategic Manager of its own, and may have an
118manager if he deems appropriate. His responsibilities to the Gentoo 118Operational Manager if deemed appropriate. His responsibilities to the Gentoo
119Documentation Project are the same as are listed on the <uri 119Documentation Project (GDP) are listed in the <e>Manager responsibilities</e>
120section of the <uri
120link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management 121link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
121Structure</uri>. 122Structure</uri> document.
122</p>
123
124<p> 123</p>
125The subprojects of the Gentoo Documentation Team together with their respective 124
126strategic managers are listed on the <uri link="/proj/en/gdp/">GDP
127Website</uri>.
128</p> 125<p>
129 126Every subproject of the Gentoo Documentation Team is listed on the
127<uri link="/proj/en/gdp/">GDP Webpage</uri>, along with their respective
128Strategic Managers.
130<p> 129</p>
130
131<p>
131The decision on adding subprojects is in hands of the strategic manager. 132The decision on adding a subproject is in the hands of the Strategic Manager.
132</p> 133</p>
133 134
134</body> 135</body>
135</section> 136</section>
136<section> 137<section>
153team about bugs regarding the Gentoo Documentation. You can add yourself by 154team about bugs regarding the Gentoo Documentation. You can add yourself by
154editing <path>/var/mail/alias/misc/docs-team</path> on dev.gentoo.org. 155editing <path>/var/mail/alias/misc/docs-team</path> on dev.gentoo.org.
155</p> 156</p>
156 157
157<p> 158<p>
158Every member of the Gentoo Documentation Team should be available at 159Members of the Gentoo Documentation Team should be available at
159<c>#gentoo-doc</c> on <uri link="http://www.freenode.net">irc.freenode.net</uri> 160<c>#gentoo-doc</c> on <uri link="http://www.freenode.net">irc.freenode.net</uri>
160whenever he is online. 161whenever they are online.
161</p>
162
163<p> 162</p>
163
164<p>
164Depending on his responsibilities, he can have limited CVS 165Depending on the assignment or responsibilities, a member may have limited CVS
165access to <c>cvs.gentoo.org</c>. Full CVS access can only be given to Gentoo 166access to <c>cvs.gentoo.org</c>. Full CVS access is restricted to Gentoo
166developers. Read-only CVS access can be given to recruitees. 167Developers. Read-only CVS access may be granted to recruits.
167</p> 168</p>
168 169
169</body> 170</body>
170</section> 171</section>
171<section> 172<section>
172<title>Documentation Translation Teams</title> 173<title>Documentation Translation Teams</title>
173<body> 174<body>
174 175
175<p> 176<p>
176Every language should be backed up by an official translation team. This 177Every language should be backed up by an official Translation Team. This
177team is lead by a lead translator and perhaps a follow-up lead translator, who 178team is led by a <e>Lead Translator</e> and perhaps a <e>Follow-On Lead
178both have CVS commit access. If for any reason the lead translator cannot 179Translator</e>, who both have CVS commit access. If for any reason the
179perform his or her duties, the follow-up lead translator is in charge. If 180<e>Lead Translator</e> cannot perform his duties, the <e>Follow-On Lead
180even this person is unavailable, the mentor(s) is/are in charge of the language. 181Translator</e> is in charge. If the <e>Follow-On</e> is unavailable, the
181</p> 182mentor(s) is/are in charge of the language.
182
183<p> 183</p>
184If a translated document is contributed, but the language in itself is 184
185not supported, the Gentoo Documentation Team will not publish it
186officially. In this case the document will stay unlinked until an official
187translation team of that language is formed.
188</p> 185<p>
189 186If a translated document for an unsupported language is contributed, the Gentoo
187Documentation Team will not publish it officially. Such documents shall not be
188linked to the website until an official Translation Team of that language is
189formed.
190<p> 190</p>
191
192<p>
191When a language is officially supported, but the team doesn't have any 193When a language is officially supported, but the team does not have any
192members or no one wants to take on the responsibilities of the lead 194members willing to take on the responsibilities of the <e>Lead
193translator, all links to the documents will be removed from the site. 195Translator</e>, all links to the documents will be removed from the site.
194However, the documents will stay available in case the language becomes 196However, the documents will stay available in case the language becomes
195officially supported again. 197officially supported again.
196</p> 198</p>
197 199
200<p>
201For more information Gentoo document translations, please consult the
202<uri link="/proj/en/gdp/doc/translators-howto.xml">
203Translators Howto for Gentoo Documentation</uri> and the
204<uri link="/proj/en/gdp/international.xml">
205GDP Internationalisation Subproject</uri> page.
206</p>
207
198</body> 208</body>
199</section> 209</section>
200</chapter> 210</chapter>
201 211
202<chapter> 212<chapter>
205<title>Legal Issues</title> 215<title>Legal Issues</title>
206<body> 216<body>
207 217
208<p> 218<p>
209Every document published by the Gentoo Documentation Project must be 219Every document published by the Gentoo Documentation Project must be
210licensed by the <uri 220licensed by the <uri
211link="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons 221link="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons
212Attribution-ShareAlike License</uri>. 222Attribution-ShareAlike License</uri>.
213</p> 223</p>
214 224
215<p> 225<p>
216Every document must have the following tag inside its GuideXML 226Every document must have the following tag inside its GuideXML
217sourcecode between the <c>&lt;/abstract&gt;</c> and the <c>&lt;version&gt;</c> 227source code between the <c>&lt;/abstract&gt;</c> and the <c>&lt;version&gt;</c>
218tags: 228tags:
219</p> 229</p>
220 230
221<pre caption = "Licensing notice for the Gentoo Documentation"> 231<pre caption = "Licensing notice for the Gentoo Documentation">
222&lt;/abstract&gt; 232&lt;/abstract&gt;
223<i> 233<i>
224&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt; 234&lt;!-- The content of this document is licensed under the CC-BY-SA license --&gt;
225&lt;!-- See http://creativecommons.org/licenses/by-sa/2.0 --&gt; 235&lt;!-- See http://creativecommons.org/licenses/by-sa/2.5 --&gt;
226&lt;license/&gt; 236&lt;license/&gt;
227</i> 237</i>
228&lt;version&gt;...&lt;/version&gt; 238&lt;version&gt;...&lt;/version&gt;
229</pre> 239</pre>
230 240
234<title>Bugs and Updates</title> 244<title>Bugs and Updates</title>
235<body> 245<body>
236 246
237<p> 247<p>
238Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> 248Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
239should be handled as fast as possible. If a bug cannot be handled 249should be handled as fast as possible. If a bug cannot be handled
240in a timely fashion, the reporter of that bug should be informed about 250in a timely fashion, the reporter of that bug should be informed about
241this using a comment on the bug and the bug should be registered in the 251this using a comment on the bug, and the bug should be registered in the
242<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if 252<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if
243applicable. The tactical or operational manager can decide that a bug has a 253applicable. The Strategic or Operational Manager may decide that a bug has a
244higher priority and should be handled first before any other task the assingee 254higher priority and should be addressed ahead any other task the assignee
245is responsible of. 255is responsible for.
246</p> 256</p>
247 257
248<p> 258<p>
249Whenever a Gentoo Documentation Team member takes care of a bug, he or 259Whenever a Gentoo Documentation Team member takes care of a bug, he or
250she should assign the bug to herself/himself, but make sure that 260she should assign the bug to herself/himself, but make sure that
251<c>docs-team@gentoo.org</c> is on the Cc-list. Unless with the consent 261<c>docs-team@gentoo.org</c> is on the Cc-list. A bug may not be taken away from
252of the operational manager, a bug may not be taken away from another
253Gentoo Documentation Team member without their approval. 262another Gentoo Documentation Team member without their approval; unless consent
263has been received from the Operational Manager.
254</p> 264</p>
255 265
256</body> 266</body>
257</section> 267</section>
258<section> 268<section>
259<title>Document Development</title> 269<title>Document Development</title>
260<body> 270<body>
261 271
262<p> 272<p>
263Every document the Gentoo Documentation Team develops can be developed as the 273Every Gentoo Documentation Team may handle documentation development as it sees
264related parties see fit. However, when the document is finished, it should be 274fit. However, when the document is finished, it should be transformed into
265transformed into <uri link="/doc/en/xml-guide.xml">GuideXML</uri> and put 275<uri link="/doc/en/xml-guide.xml">GuideXML</uri> and made available on the
266available on the Gentoo CVS infrastructure. It must also be registered in the 276Gentoo CVS infrastructure. It must also be registered in the
267<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if 277<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if
268applicable. 278applicable.
269</p> 279</p>
270 280
271<p> 281<p>
272When a new document is started or a big change is needed, a bug should be filed 282When a new document is started or a big change is needed, a bug should be filed
273at <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> 283at <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
274concerning the development of this document. If there is already a bug 284concerning the development of this document. If there is already a bug
275in the database that requests a change to the documentation, a new bug 285in the database that requests a change to the documentation, a new bug
276does not have to be filed. Grammatical, syntactical or small changes 286does not have to be filed. Grammatical, syntactical or small changes
277do not require a bug to be filed on <uri 287do not require a bug to be filed on <uri
278link="http://bugs.gentoo.org">bugs.gentoo.org</uri> as well. 288link="http://bugs.gentoo.org">bugs.gentoo.org</uri> as well.
279</p> 289</p>
280 290
281<p> 291<p>
282All changes in contents of the document, except for typo fixes in text 292All changes in contents of the document, except for typo fixes in text
284number (and date) increase. Note that the change of a Code Listings should 294number (and date) increase. Note that the change of a Code Listings should
285definitely cause an increase of the version number and date. 295definitely cause an increase of the version number and date.
286</p> 296</p>
287 297
288<p> 298<p>
289All changes in XML formatting should lead to version (and date) bumps only in 299All changes in XML formatting should lead to version (and date) bumps only in
290case the layout of the document changes. 300case the layout of the document changes.
291</p> 301</p>
292 302
293<p> 303<p>
294Whether or not to increment the major version number instead of minor version 304Whether or not to increment the major version number instead of minor version
306<section> 316<section>
307<title>Reviewing and Committing</title> 317<title>Reviewing and Committing</title>
308<body> 318<body>
309 319
310<p> 320<p>
311To keep a high-pace development cycle of the documentation, technical or 321To maintain a high-paced documentation development cycle, technical or
312intrusive changes to documents can be propagated immediately to the document 322intrusive changes to documents can be propagated immediately to the document.
313<e>if</e> the editor is 100% confident his changes are correct and working. If 323This is allowed only <e>if</e> the editor is absolutely confident the changes
314you are not 100% confident (for instance because a user has told you how to fix 324are functional. If you are not absolutely confident (for instance because a
315it but you cannot verify yourself), have the change reviewed by a Gentoo 325user has told you how to fix it but you cannot verify yourself), have the
316Developer that can verify the change. 326changes reviewed by a Gentoo Developer that can verify the changes are apt.
317</p>
318
319<p> 327</p>
328
329<p>
320High volume, technical or intrusive changes must be accompanied by a bugreport 330High-volume, technical or intrusive changes must be accompanied by a bug report
321on <uri>http://bugs.gentoo.org</uri>. This bugnumber <e>must</e> be mentioned in 331on <uri>http://bugs.gentoo.org</uri>. This bug number <e>must</e> be mentioned
322the CVS log to allow backtracing of changes. 332in the CVS log to allow backtracing of changes.
323</p>
324
325<p> 333</p>
326If a bugfix consists out of both content as internal coding changes, 334
327both changes must be committed separately so that translators can easily
328view the important changes (content) and ignore the coding changes.
329</p> 335<p>
330 336If a bugfix includes changes to content as well as internal coding changes,
337both changes must be committed separately. This allows translators to focus
338on the relevant changes regarding content and ignore the coding changes.
331<p> 339</p>
332In case of a translation, the lead translator of the language is 340
333responsible for the document. Only he may commit the document to CVS 341<p>
334unless he is currently "in training", in which case his or her 342If the document in question is a translation, the <e>Lead Translator</e> of the
335mentor should commit it. 343affected language is responsible for the document. Only the
344<e>Lead Translator</e> may commit the document to the CVS repository. However,
345if the <e>Lead Translator</e> is currently "in training", the trainee's mentor
346should commit the changes.
336</p> 347</p>
337 348
338</body> 349</body>
339</section> 350</section>
340<section> 351<section>
341<title>Sanctions</title> 352<title>Sanctions</title>
342<body> 353<body>
343 354
344<p> 355<p>
345Although this has never been necessary, it is still important to list this in 356Malicious conduct by developers has never been an issue. However, it should be
346the policy - even though it is hateful. Anyway, documentation developers that 357noted that documentation developers that misuse their position by
347misuse their position by
348</p> 358</p>
349 359
350<ul> 360<ul>
351 <li>deliberately providing wrong information to users or developers</li> 361 <li>deliberately providing wrong information to users or developers</li>
352 <li>deliberately writing flawed documentation</li> 362 <li>deliberately writing flawed documentation</li>
354 <li> 364 <li>
355 deliberately go against the decisions made policy-wise or through a 365 deliberately go against the decisions made policy-wise or through a
356 consensus-model on the Gentoo Documentation mailinglist 366 consensus-model on the Gentoo Documentation mailinglist
357 </li> 367 </li>
358 <li> 368 <li>
359 not performing at all for a long time without informing the GDP and without 369 not performing at all for a long time without informing the GDP, and without
360 replying to the operational manager's request for a status update 370 replying to the Operational Manager's request for a status update
361 </li> 371 </li>
362</ul> 372</ul>
363 373
364<p> 374<p>
365will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer 375will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer
369</body> 379</body>
370</section> 380</section>
371</chapter> 381</chapter>
372 382
373<chapter> 383<chapter>
374<title>Documentation Team Recruitement</title> 384<title>Documentation Team Recruitment</title>
375<section> 385<section>
376<title>Contributors, Authors, Translators</title> 386<title>Contributors, Authors, Translators</title>
377<body> 387<body>
378 388
379<p> 389<p>
380Everyone interested in contributing documentation, editing existing 390Everyone interested in contributing documentation, editing existing
381documentation, writing new documentation or translating documentation is 391documentation, writing new documentation or translating documentation is
382welcome to join the team. There are no rules or strings attached to 392welcome to join the team. There are no rules or strings attached to
383this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c> 393this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c>,
384and you have fully read this policy and understand it. 394and you have fully read this policy and understand it.
385</p> 395</p>
386 396
387</body> 397</body>
388</section> 398</section>
391<body> 401<body>
392 402
393<p> 403<p>
394The Documentation Project has a strict recruitment process outlined below. 404The Documentation Project has a strict recruitment process outlined below.
395This process can not be deviated from in any circumstance. We have opted for 405This process can not be deviated from in any circumstance. We have opted for
396this recruitment process to assure ourselves that the recruitee is well informed 406this recruitment process to assure ourselves that the recruit is well informed
397about the Gentoo Documentation Policy and the Gentoo Coding Style. It has proven 407about the Gentoo Documentation Policy and the Gentoo Coding Style. It has proven
398to be quite effective even though many contributors see it as a too large burden 408to be quite effective even though many contributors see it as a too large burden
399to cross. 409to cross.
400</p> 410</p>
401 411
413<body> 423<body>
414 424
415<p> 425<p>
416No recruitment process starts without investigating the contributions done 426No recruitment process starts without investigating the contributions done
417already to the Gentoo Documentation Project. The number of contributions must be 427already to the Gentoo Documentation Project. The number of contributions must be
418large to assure a good knowledge of GuideXML, Coding Style and policy. The 428large to assure a good knowledge of GuideXML, Coding Style and policy. The
419contribution period must be large as well to inform the contributor about the 429contribution period must be large as well to inform the contributor about the
420time-consuming position and pressure the application involves. 430time-consuming position and pressure the application involves.
421</p> 431</p>
422 432
423<p> 433<p>
424The number of contributions and period over which the contributions should be 434The number of contributions and period over which the contributions should be
450An update constitutes a non-trivial update to any documentation, translation or 460An update constitutes a non-trivial update to any documentation, translation or
451otherwise, completely written by the contributor and committed after review by 461otherwise, completely written by the contributor and committed after review by
452any existing documentation developer. The period is fixed - increasing the 462any existing documentation developer. The period is fixed - increasing the
453contributions does not decrease the period. Also, we don't average the 463contributions does not decrease the period. Also, we don't average the
454contributions over time to make sure the contributor doesn't give a contribution 464contributions over time to make sure the contributor doesn't give a contribution
455burst and then waits until the Phase is over. 465burst, and then waits until the Phase is over.
456</p> 466</p>
457 467
458<p> 468<p>
459Without this phase we can not know if the contributor understands what it takes 469Without this phase we can not know if the contributor understands what it takes
460to be a documentation developer. The validation of this activity happens through 470to be a documentation developer. The validation of this activity happens through
465Any request for CVS access that does not allow a development activity as written 475Any request for CVS access that does not allow a development activity as written
466down in the aforementioned table will not be taken into account. 476down in the aforementioned table will not be taken into account.
467</p> 477</p>
468 478
469<p> 479<p>
470If you feel that you have shown sufficient amount of contributions, contact 480If you feel that you have shown sufficient amount of contributions, contact
471the Operational Manager of the Gentoo Documentation Project. He 481the Operational Manager of the Gentoo Documentation Project. He
472will ask you for your coordinates and other information and then arrange 482will ask you for your coordinates and other information, and then arrange
473for the next phase to be started. 483for the next phase to be started.
474</p> 484</p>
475 485
476</body> 486</body>
477</section> 487</section>
478<section> 488<section>
479<title>Phase 2: Read-Only CVS Access</title> 489<title>Phase 2: Read-Only CVS Access</title>
480<body> 490<body>
481 491
482<p> 492<p>
483During phase 2, the recruitee is given read-only access to the Gentoo 493During phase 2, the recruit is given read-only access to the Gentoo
484Documentation Repository, allowing him to generate commit-ready patches for the 494Documentation Repository, allowing him to generate commit-ready patches for
485tree. During this period, which is roughly the same as the aforementioned table, 495the tree. During this period, which is roughly the same as the aforementioned
486his patches are not edited by a documentation developer anymore, but are either 496table, his patches are not edited by a documentation developer anymore, but
487committed as-is or refused. The recruitee is also assigned to a full-time 497are either committed as-is or refused. The recruit is also assigned to a
488documentation developer (the mentor) which will guide him through these last 498full-time documentation developer (the mentor) which will guide him through
489phases. 499these last phases.
490</p> 500</p>
491 501
492<p> 502<p>
493The quality of the contributions are in this phase most important - every patch 503The quality of the contributions are in this phase most important - every patch
494that does not follow the Documentation Policy, Coding Style or other guideline 504that does not follow the Documentation Policy, Coding Style or other guideline
499During this period, you: 509During this period, you:
500</p> 510</p>
501 511
502<ul> 512<ul>
503 <li> 513 <li>
504 are advised to learn about Gentoo's inner workings. 514 are advised to learn about Gentoo's inner workings.
505 This is required as you will be asked later on to answer Gentoo's <uri 515 This is required as you will be asked later on to answer Gentoo's <uri
506 link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>. 516 link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
507 </li> 517 </li>
508 <li> 518 <li>
509 will be asked to fill in the <uri 519 will be asked to fill in the <uri
510 link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project 520 link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project
511 Quiz</uri>. You need to succesfully pass this entire quiz (all questions) 521 Quiz</uri>. You need to successfully pass this entire quiz (all questions)
512 before you can continue with the next Phase. 522 before you can continue with the next Phase.
513 </li> 523 </li>
514</ul> 524</ul>
515 525
516</body> 526</body>
520<body> 530<body>
521 531
522<p> 532<p>
523When Phase 2 is finished, the Operational Manager will contact <uri 533When Phase 2 is finished, the Operational Manager will contact <uri
524link="/proj/en/devrel">Developer Relations</uri> and give a final "Go!" for the 534link="/proj/en/devrel">Developer Relations</uri> and give a final "Go!" for the
525Gentoo recruitment process after which you will be given a Gentoo e-mail 535Gentoo recruitment process after which you will be given a Gentoo e-mail
526address and be appointed to one or more subprojects. 536address and be appointed to one or more subprojects.
527</p> 537</p>
528 538
529</body> 539</body>
530</section> 540</section>
531</chapter> 541</chapter>

Legend:
Removed from v.1.12  
changed lines
  Added in v.1.21

  ViewVC Help
Powered by ViewVC 1.1.20