/[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.12
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.12 2005/05/12 09:56:52 neysx Exp $ -->
3
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 5
5<guide link="/proj/en/gdp/doc/doc-developer-guide.xml"> 6<guide link="doc-policy.xml">
6 7
7<title>Gentoo Linux Documentation Policy</title> 8<title>Gentoo Linux Documentation Policy</title>
8<author title="Author"><mail link="zhen@gentoo.org">John P. Davis</mail></author> 9<author title="Author">
10 <mail link="zhen@gentoo.org">John P. Davis</mail>
11</author>
12<author title="Author">
13 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
14</author>
15<author title="Editor">
16 <mail link="spyderous@gentoo.org">Donnie Berkholz</mail>
17</author>
18
19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
21
9<abstract> 22<abstract>
10 This guide explains the current Gentoo Documentation Policy. 23This document contains the Gentoo Documentation Policy, which is the
24base document which all Gentoo Documentation developers and
25Contributers should know and exercise.
11</abstract> 26</abstract>
12 27
28<license/>
29
13<version>2.1.1</version> 30<version>3.11</version>
14<date>1 April 2003</date> 31<date>2005-05-07</date>
15 32
16<chapter> 33<chapter>
17 <title>Introduction</title> 34<title>Introduction</title>
18 <section> 35<section>
19 <title>Introduction</title> 36<title>Introduction</title>
20 <body> 37<body>
21 38
39<p>
22 <p><B>The Gentoo Linux Documentation team aspires to create exceptionally professional 40The Gentoo Linux Documentation team aspires to create exceptionally
23 documentation that is immediately clear and concise to the end user</B>. In order to 41professional documentation that is immediately clear and concise to the
24 fulfill this goal, we have very specific rules and guidelines that <e>all</e> 42end 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. 43guidelines that <e>all</e> documentation must go through before it is
26 </p> 44published on our website, or otherwise.
27 45</p>
46
28 </body> 47</body>
29 </section> 48</section>
30
31 <section> 49<section>
32 <title>Covered Topics</title> 50<title>Covered Topics</title>
33 <body> 51<body>
34 52
53<p>
35 <p>This policy will cover these topics: </p> 54This policy will cover these topics:
36 <ul> 55</p>
56
57<ul>
37 <li>Documentation Team Organization</li> 58<li>Documentation Project Team Organization</li>
38 <li>English Developer Guidelines </li> 59<li>Documentation Guidelines</li>
39 <li>Translator Guidelines</li> 60<li>Documentation Team Recruitement</li>
40 <li>Contact Lists </li>
41 </ul> 61</ul>
42 62
43 </body> 63</body>
44 </section> 64</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> 65</chapter>
83 66
84<chapter> 67<chapter>
85 <title>Documentation Team Organization</title> 68<title>Documentation Project Team Organization</title>
86 <section> 69<section>
87 <title>Organization</title> 70<title>Organization</title>
88 <body> 71<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 72
94 <p><b>Technical Writers: </b>The technical writers' function is to completely 73<p>
95 document every aspect of Gentoo Linux. The writers will periodically be given 74The Gentoo Documentation Project Team is split into several smaller teams
96 assignments by the Senior Developers, and those assignments are to take precedence 75that operate in complete cooperation with each other. Each smaller team
97 over any other Gentoo Linux development work. Although the writers' work is 76represents an active development team of a Gentoo Documentation
98 ultimately proofed by the <b>Editing Team</b>, the writers <e>will still</e> 77Subproject.
99 proof their own work before submitting it to the <i>gentoo-docs-review@gentoo.org</i> 78</p>
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 79
103 <p><b>Editors/ Proofreaders: </b>The editors are in charge of editing and proofing 80<p>
104 all changes to the Gentoo Linux Documentation. No change can be made unless it is 81The Gentoo Documentation Project is strategically lead by a top-level manager
105 verified to be grammatically and syntactically correct by an Editor. The Editors 82as 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 83Management Structure</uri>. This document also describes the responsibilities
107 is as professional and grammatically correct as possible. All Editors must 84of the strategic manager with respect to Gentoo Linux.
108 be subscribed to the <i>gentoo-docs-review@gentoo.org</i> mailing list.</p> 85</p>
109 86
110 <p><b>Translators: </b>Due to the special nature of translations, the translators 87<p>
111 are broken into their own team. Each language will have a lead Developer which will 88For 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 89operational manager. This person keeps track of all documentation-related tasks
113 a translation is ready to go live on the documentation index page, they may add it. 90that are more short-term. 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> 91one and the same if the strategic manager wishes so.
115 mailing list.</p> 92</p>
93
94<p>
95Currently these positions are taken by the following people:
96</p>
97
98<table>
99<tr>
100 <th>Position</th>
101 <th>Developer Name</th>
102 <th>Developer Nick</th>
103</tr>
104<tr>
105 <ti>Strategic Manager</ti>
106 <ti>Sven Vermeulen</ti>
107 <ti><mail link="swift@gentoo.org">swift</mail></ti>
108</tr>
109<tr>
110 <ti>Operational Manager</ti>
111 <ti>Xavier Neys</ti>
112 <ti><mail link="neysx@gentoo.org">neysx</mail></ti>
113</tr>
114</table>
115
116<p>
117Every subproject has a strategic manager of its own. he can have an operational
118manager if he deems appropriate. His responsibilities to the Gentoo
119Documentation Project are the same as are listed on the <uri
120link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
121Structure</uri>.
122</p>
123
124<p>
125The subprojects of the Gentoo Documentation Team together with their respective
126strategic managers are listed on the <uri link="/proj/en/gdp/">GDP
127Website</uri>.
128</p>
129
130<p>
131The decision on adding subprojects is in hands of the strategic manager.
132</p>
133
116 </body> 134</body>
117 </section> 135</section>
136<section>
137<title>Documentation Project Team Members</title>
138<body>
139
140<p>
141Every member of the Gentoo Documentation Project must be subscribed to
142the <mail link="gentoo-doc-subscribe@gentoo.org">gentoo-doc@gentoo.org</mail>
143mailing list. This mailing list will be used to discuss all
144documentation-related issues. This mailing list is open to all interested
145parties, developer or not.
146</p>
147
148<p>
149Every 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
151alias is <e>only</e> used by <uri
152link="http://bugs.gentoo.org">bugs.gentoo.org</uri> to inform the documentation
153team about bugs regarding the Gentoo Documentation. You can add yourself by
154editing <path>/var/mail/alias/misc/docs-team</path> on dev.gentoo.org.
155</p>
156
157<p>
158Every member 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>
160whenever he is online.
161</p>
162
163<p>
164Depending on his responsibilities, he can have limited CVS
165access to <c>cvs.gentoo.org</c>. Full CVS access can only be given to Gentoo
166developers. Read-only CVS access can be given to recruitees.
167</p>
168
169</body>
170</section>
171<section>
172<title>Documentation Translation Teams</title>
173<body>
174
175<p>
176Every 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
178both have CVS commit access. If for any reason the lead translator cannot
179perform his or her duties, the follow-up lead translator is in charge. If
180even this person is unavailable, the mentor(s) is/are in charge of the language.
181</p>
182
183<p>
184If a translated document is contributed, but the language in itself is
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>
189
190<p>
191When a language is officially supported, but the team doesn't have any
192members or no one wants to take on the responsibilities of the lead
193translator, 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</body>
199</section>
118</chapter> 200</chapter>
119 201
120<chapter> 202<chapter>
121 <title>English Developer Guidelines</title> 203<title>Gentoo Documentation Guidelines</title>
122 <section> 204<section>
123 <title>QA Process</title> 205<title>Legal Issues</title>
124 <body> 206<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 207
131 <p>If not done already, the following documents need to be read before continuing: 208<p>
132 </p> 209Every document published by the Gentoo Documentation Project must be
210licensed by the <uri
211link="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons
212Attribution-ShareAlike License</uri>.
213</p>
133 214
134 <ul> 215<p>
135 <li><uri link="http://www.gentoo.org/doc/en/xml-guide.xml">The Gentoo Linux XML Guide</uri></li> 216Every document must have the following tag inside its GuideXML
136 </ul> 217sourcecode between the <c>&lt;/abstract&gt;</c> and the <c>&lt;version&gt;</c>
218tags:
219</p>
137 220
138 <p>The Gentoo Linux Documentation process can be broken down into several parts: 221<pre caption = "Licensing notice for the Gentoo Documentation">
139 </p> 222&lt;/abstract&gt;
140 223<i>
141 <p><b>The first step to submitting a new document or changing an existing document</b> 224&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 225&lt;!-- See http://creativecommons.org/licenses/by-sa/2.0 --&gt;
143 as a notification to other developers and users alike that there is a work in process. 226&lt;license/&gt;
144 If there is already a bug in the database that requests a change to the documentation, 227</i>
145 a new bug does not have to be filed. 228&lt;version&gt;...&lt;/version&gt;
146 </p> 229</pre>
147 230
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> 231</body>
163 </section> 232</section>
233<section>
234<title>Bugs and Updates</title>
235<body>
236
237<p>
238Every 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
240in 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
242<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
244higher priority and should be handled first before any other task the assingee
245is responsible of.
246</p>
247
248<p>
249Whenever a Gentoo Documentation Team member takes care of a bug, he or
250she 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
252of the operational manager, a bug may not be taken away from another
253Gentoo Documentation Team member without their approval.
254</p>
255
256</body>
257</section>
258<section>
259<title>Document Development</title>
260<body>
261
262<p>
263Every document the Gentoo Documentation Team develops can be developed as the
264related parties see fit. However, when the document is finished, it should be
265transformed into <uri link="/doc/en/xml-guide.xml">GuideXML</uri> and put
266available on the Gentoo CVS infrastructure. It must also be registered in the
267<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if
268applicable.
269</p>
270
271<p>
272When 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>
274concerning the development of this document. If there is already a bug
275in the database that requests a change to the documentation, a new bug
276does not have to be filed. Grammatical, syntactical or small changes
277do not require a bug to be filed on <uri
278link="http://bugs.gentoo.org">bugs.gentoo.org</uri> as well.
279</p>
280
281<p>
282All changes in contents of the document, except for typo fixes in text
283itself or in the comments to code listings, should lead to version
284number (and date) increase. Note that the change of a Code Listings should
285definitely cause an increase of the version number and date.
286</p>
287
288<p>
289All changes in XML formatting should lead to version (and date) bumps only in
290case the layout of the document changes.
291</p>
292
293<p>
294Whether or not to increment the major version number instead of minor version
295number or other is up to the editor.
296</p>
297
298<p>
299Every update of a translation should copy the new version information
300verbatim from the master English document so fully synchronised
301translations have the same version information.
302</p>
303
304</body>
305</section>
306<section>
307<title>Reviewing and Committing</title>
308<body>
309
310<p>
311To keep a high-pace development cycle of the documentation, technical or
312intrusive 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
314you are not 100% confident (for instance because a user has told you how to fix
315it but you cannot verify yourself), have the change reviewed by a Gentoo
316Developer that can verify the change.
317</p>
318
319<p>
320High volume, technical or intrusive changes must be accompanied by a bugreport
321on <uri>http://bugs.gentoo.org</uri>. This bugnumber <e>must</e> be mentioned in
322the CVS log to allow backtracing of changes.
323</p>
324
325<p>
326If a bugfix consists out of both content as internal coding changes,
327both changes must be committed separately so that translators can easily
328view the important changes (content) and ignore the coding changes.
329</p>
330
331<p>
332In case of a translation, the lead translator of the language is
333responsible for the document. Only he may commit the document to CVS
334unless he is currently "in training", in which case his or her
335mentor should commit it.
336</p>
337
338</body>
339</section>
340<section>
341<title>Sanctions</title>
342<body>
343
344<p>
345Although this has never been necessary, it is still important to list this in
346the policy - even though it is hateful. Anyway, documentation developers that
347misuse their position by
348</p>
349
350<ul>
351 <li>deliberately providing wrong information to users or developers</li>
352 <li>deliberately writing flawed documentation</li>
353 <li>deliberately corrupting documents</li>
354 <li>
355 deliberately go against the decisions made policy-wise or through a
356 consensus-model on the Gentoo Documentation mailinglist
357 </li>
358 <li>
359 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
361 </li>
362</ul>
363
364<p>
365will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer
366Relations</uri> project.
367</p>
368
369</body>
370</section>
164</chapter> 371</chapter>
165 372
166
167<chapter> 373<chapter>
168 <title>Translator Guidelines</title> 374<title>Documentation Team Recruitement</title>
169 <section> 375<section>
170 <title>QA Process</title> 376<title>Contributors, Authors, Translators</title>
171 <body> 377<body>
172
173 <p>Translators will follow the English Developer's QA process, but with the following exceptions:
174 </p>
175 378
176 <p><b>Each language will have a translation team, with an Offical Gentoo Linux Translator</b> as their head. 379<p>
177 All translations will be filtered through this lead person. The lead translator will make certain that the 380Everyone interested in contributing documentation, editing existing
178 translated documents are grammatically and syntactically perfect. The lead translator will have limited CVS 381documentation, writing new documentation or translating documentation is
179 access which will enable them to commit documents in a timely manner. </p> 382welcome to join the team. There are no rules or strings attached to
180 383this. 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: 384and you have fully read this policy and understand it.
182 </p> 385</p>
183 386
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> 387</body>
205 </section> 388</section>
389<section>
390<title>Recruitment Process</title>
391<body>
392
393<p>
394The Documentation Project has a strict recruitment process outlined below.
395This 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
397about 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
399to cross.
400</p>
401
402<p>
403This recruitment process is meant only for requests to the Gentoo Documentation
404Repository through CVS. Being listed as the maintainer or Point-Of-Contact for a
405certain document or range of documents is granted by a simple request to the
406Operational Manager or Project Lead.
407</p>
408
409</body>
410</section>
411<section>
412<title>Phase 1: Contributions</title>
413<body>
414
415<p>
416No recruitment process starts without investigating the contributions done
417already to the Gentoo Documentation Project. The number of contributions must be
418large 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
420time-consuming position and pressure the application involves.
421</p>
422
423<p>
424The number of contributions and period over which the contributions should be
425made depends on the position which the contributor solicits for. Although it is
426difficult to write down these measurements in numbers, the following table
427should give a general overview. Final decision however lays in the hands of the
428Operational Manager.
429</p>
430
431<table>
432<tr>
433 <th>Position</th>
434 <th>Minimal Activity</th>
435 <th>Minimal Period</th>
436</tr>
437<tr>
438 <ti>Full-time Developer</ti>
439 <ti>2 updates per week</ti>
440 <ti>1 month</ti>
441</tr>
442<tr>
443 <ti>Part-time Developer</ti>
444 <ti>4 updates per month</ti>
445 <ti>1 month</ti>
446</tr>
447</table>
448
449<p>
450An update constitutes a non-trivial update to any documentation, translation or
451otherwise, completely written by the contributor and committed after review by
452any existing documentation developer. The period is fixed - increasing the
453contributions does not decrease the period. Also, we don't average the
454contributions over time to make sure the contributor doesn't give a contribution
455burst and then waits until the Phase is over.
456</p>
457
458<p>
459Without 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
461bugzilla reports.
462</p>
463
464<p>
465Any request for CVS access that does not allow a development activity as written
466down in the aforementioned table will not be taken into account.
467</p>
468
469<p>
470If you feel that you have shown sufficient amount of contributions, contact
471the Operational Manager of the Gentoo Documentation Project. He
472will ask you for your coordinates and other information and then arrange
473for the next phase to be started.
474</p>
475
476</body>
477</section>
478<section>
479<title>Phase 2: Read-Only CVS Access</title>
480<body>
481
482<p>
483During phase 2, the recruitee is given read-only access to the Gentoo
484Documentation Repository, allowing him to generate commit-ready patches for the
485tree. During this period, which is roughly the same as the aforementioned table,
486his patches are not edited by a documentation developer anymore, but are either
487committed as-is or refused. The recruitee is also assigned to a full-time
488documentation developer (the mentor) which will guide him through these last
489phases.
490</p>
491
492<p>
493The quality of the contributions are in this phase most important - every patch
494that does not follow the Documentation Policy, Coding Style or other guideline
495that affects the document is refused.
496</p>
497
498<p>
499During this period, you:
500</p>
501
502<ul>
503 <li>
504 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
506 link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
507 </li>
508 <li>
509 will be asked to fill in the <uri
510 link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project
511 Quiz</uri>. You need to succesfully pass this entire quiz (all questions)
512 before you can continue with the next Phase.
513 </li>
514</ul>
515
516</body>
517</section>
518<section>
519<title>Phase 3: Gentoo Recruitment</title>
520<body>
521
522<p>
523When Phase 2 is finished, the Operational Manager will contact <uri
524link="/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
526address and be appointed to one or more subprojects.
527</p>
528
529</body>
530</section>
206</chapter> 531</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> 532</guide>

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

  ViewVC Help
Powered by ViewVC 1.1.20