/[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.8 Revision 1.9
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.8 2004/12/28 17:20:15 swift Exp $ --> 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 $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 5
6<guide link="doc-policy.xml"> 6<guide link="doc-policy.xml">
7 7
25Contributers should know and exercise. 25Contributers should know and exercise.
26</abstract> 26</abstract>
27 27
28<license/> 28<license/>
29 29
30<version>3.9</version> 30<version>3.10</version>
31<date>2004-12-28</date> 31<date>2005-01-08</date>
32 32
33<chapter> 33<chapter>
34<title>Introduction</title> 34<title>Introduction</title>
35<section> 35<section>
36<title>Introduction</title> 36<title>Introduction</title>
76represents an active development team of a Gentoo Documentation 76represents an active development team of a Gentoo Documentation
77Subproject. 77Subproject.
78</p> 78</p>
79 79
80<p> 80<p>
81The Gentoo Documentation Project is strategically lead by a top-level 81The Gentoo Documentation Project is strategically lead by a top-level manager
82manager as required by the 82as 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 83Management Structure</uri>. This document also describes the responsibilities
85the strategic manager with respect to Gentoo Linux. 84of the strategic manager with respect to Gentoo Linux.
86</p> 85</p>
87 86
88<p> 87<p>
89For day-to-day managerial tasks the Gentoo Documentation Project has an 88For day-to-day managerial tasks the Gentoo Documentation Project has an
90operational manager. This person keeps track of all 89operational manager. This person keeps track of all documentation-related tasks
91documentation-related tasks that are more short-term. The operational 90that are more short-term. The operational manager and strategic manager can be
92manager and strategic manager can be one and the same if the strategic 91one and the same if the strategic manager wishes so.
93manager wishes so.
94</p> 92</p>
95 93
96<p> 94<p>
97Currently these positions are taken by the following people: 95Currently these positions are taken by the following people:
98</p> 96</p>
114 <ti><mail link="neysx@gentoo.org">neysx</mail></ti> 112 <ti><mail link="neysx@gentoo.org">neysx</mail></ti>
115</tr> 113</tr>
116</table> 114</table>
117 115
118<p> 116<p>
119Every subproject has a strategic manager of its own. he can 117Every subproject has a strategic manager of its own. he can have an operational
120have an operational manager if he deems appropriate. His 118manager if he deems appropriate. His responsibilities to the Gentoo
121responsibilities to the Gentoo Documentation Project are the same as are 119Documentation Project are the same as are listed on the <uri
122listed on the <uri
123link="http://www.gentoo.org/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo 120link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
124Management Structure</uri>. 121Structure</uri>.
125</p>
126
127<p> 122</p>
123
124<p>
128The subprojects of the Gentoo Documentation Team together with their 125The subprojects of the Gentoo Documentation Team together with their respective
129respective strategic managers are listed on the <uri 126strategic managers are listed on the <uri link="/proj/en/gdp/">GDP
130link="http://www.gentoo.org/proj/en/gdp">GDP Website</uri>. 127Website</uri>.
131</p> 128</p>
132 129
133<p> 130<p>
134The decision on adding subprojects is in hands of the strategic manager. 131The decision on adding subprojects is in hands of the strategic manager.
135</p> 132</p>
147documentation-related issues. This mailing list is open to all interested 144documentation-related issues. This mailing list is open to all interested
148parties, developer or not. 145parties, developer or not.
149</p> 146</p>
150 147
151<p> 148<p>
152Every member of the Gentoo Documentation Project must be subscribed to 149Every member of the Gentoo Documentation Project must be subscribed to the
153the <mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. 150<mail link="docs-team@gentoo.org">docs-team@gentoo.org</mail> alias. This
154This alias is <e>only</e> used by <uri 151alias is <e>only</e> used by <uri
155link="http://bugs.gentoo.org">bugs.gentoo.org</uri> 152link="http://bugs.gentoo.org">bugs.gentoo.org</uri> to inform the documentation
156to inform the documentation team about bugs regarding the Gentoo 153team about bugs regarding the Gentoo Documentation.
157Documentation.
158</p> 154</p>
159 155
160<p> 156<p>
161Every member of the Gentoo Documentation Team should be available at 157Every member 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>
261<section> 257<section>
262<title>Document Development</title> 258<title>Document Development</title>
263<body> 259<body>
264 260
265<p> 261<p>
266Every document the Gentoo Documentation Team develops can be developed 262Every document the Gentoo Documentation Team develops can be developed as the
267as the related parties see fit. However, when the document is finished, 263related parties see fit. However, when the document is finished, it should be
268it should be transformed into <uri 264transformed into <uri link="/doc/en/xml-guide.xml">GuideXML</uri> and put
269link="http://www.gentoo.org/doc/en/xml-guide.xml">GuideXML</uri> and put
270available on the Gentoo CVS infrastructure. It must also be registered in the 265available on the Gentoo CVS infrastructure. It must also be registered in the
271<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if 266<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if
272applicable. 267applicable.
273</p> 268</p>
274 269
285<p> 280<p>
286All changes in contents of the document, except for typo fixes in text 281All changes in contents of the document, except for typo fixes in text
287itself or in the comments to code listings, should lead to version 282itself or in the comments to code listings, should lead to version
288number (and date) increase. Note that the change of a Code Listings should 283number (and date) increase. Note that the change of a Code Listings should
289definitely cause an increase of the version number and date. 284definitely cause an increase of the version number and date.
290</p>
291
292<p>
293When updating a handbook-related file (such as the various
294<path>hb-*</path> files) you must bump the parental
295<path>handbook-&lt;arch&gt;.xml</path> file as well and commit all files at
296once (which also means an identical commit message).
297</p> 285</p>
298 286
299<p> 287<p>
300All changes in XML formatting should lead to version (and date) bumps only in 288All changes in XML formatting should lead to version (and date) bumps only in
301case the layout of the document changes. 289case the layout of the document changes.
371 replying to the operational manager's request for a status update 359 replying to the operational manager's request for a status update
372 </li> 360 </li>
373</ul> 361</ul>
374 362
375<p> 363<p>
376will be reported to the <uri link="/proj/en/devrel">Gentoo Developer 364will be reported to the <uri link="/proj/en/devrel/">Gentoo Developer
377Relations</uri> project. 365Relations</uri> project.
378</p> 366</p>
379 367
380</body> 368</body>
381</section> 369</section>

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

  ViewVC Help
Powered by ViewVC 1.1.20