| 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.15 2005/06/02 16:58:03 swift Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v 1.16 2005/06/02 17:01:24 swift 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 | |
| … | |
… | |
| 20 | <!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
20 | <!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
| 21 | |
21 | |
| 22 | <abstract> |
22 | <abstract> |
| 23 | This document contains the Gentoo Documentation Policy, which is the |
23 | This document contains the Gentoo Documentation Policy, which is the |
| 24 | base document which all Gentoo Documentation developers and |
24 | base document which all Gentoo Documentation developers and |
| 25 | Contributers should know and exercise. |
25 | Contributors should know and exercise. |
| 26 | </abstract> |
26 | </abstract> |
| 27 | |
27 | |
| 28 | <license/> |
28 | <license/> |
| 29 | |
29 | |
| 30 | <version>3.13</version> |
30 | <version>3.13</version> |
| … | |
… | |
| 39 | <p> |
39 | <p> |
| 40 | The Gentoo Linux Documentation team aspires to create exceptionally |
40 | The Gentoo Linux Documentation team aspires to create exceptionally |
| 41 | professional documentation that is immediately clear and concise to the |
41 | professional documentation that is immediately clear and concise to the |
| 42 | end user. In order to fulfill this goal, we have very specific rules and |
42 | end user. In order to fulfill this goal, we have very specific rules and |
| 43 | guidelines that <e>all</e> documentation must go through prior to |
43 | guidelines that <e>all</e> documentation must go through prior to |
| 44 | dissemination on our website, or otherwise. |
44 | dissemination on our website, or elsewhere. |
| 45 | </p> |
45 | </p> |
| 46 | |
46 | |
| 47 | </body> |
47 | </body> |
| 48 | </section> |
48 | </section> |
| 49 | <section> |
49 | <section> |
| … | |
… | |
| 111 | <ti><mail link="neysx@gentoo.org">neysx</mail></ti> |
111 | <ti><mail link="neysx@gentoo.org">neysx</mail></ti> |
| 112 | </tr> |
112 | </tr> |
| 113 | </table> |
113 | </table> |
| 114 | |
114 | |
| 115 | <p> |
115 | <p> |
| 116 | Every subproject has a Strategic Manager of its own and may have an |
116 | Every subproject has a Strategic Manager of its own, and may have an |
| 117 | Operational Manager if deemed appropriate. His responsibilities to the Gentoo |
117 | Operational Manager if deemed appropriate. His responsibilities to the Gentoo |
| 118 | Documentation Project (GDP) are listed in the <e>Manager responsibilities</e> |
118 | Documentation Project (GDP) are listed in the <e>Manager responsibilities</e> |
| 119 | section of the <uri |
119 | section of the <uri |
| 120 | link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management |
120 | link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management |
| 121 | Structure</uri> document. |
121 | Structure</uri> document. |
| … | |
… | |
| 245 | |
245 | |
| 246 | <p> |
246 | <p> |
| 247 | Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> |
247 | Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> |
| 248 | should be handled as fast as possible. If a bug cannot be handled |
248 | should be handled as fast as possible. If a bug cannot be handled |
| 249 | in a timely fashion, the reporter of that bug should be informed about |
249 | in a timely fashion, the reporter of that bug should be informed about |
| 250 | this using a comment on the bug and the bug should be registered in the |
250 | this using a comment on the bug, and the bug should be registered in the |
| 251 | <uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if |
251 | <uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if |
| 252 | applicable. The Strategic or Operational Manager may decide that a bug has a |
252 | applicable. The Strategic or Operational Manager may decide that a bug has a |
| 253 | higher priority and should be addressed ahead any other task the assignee |
253 | higher priority and should be addressed ahead any other task the assignee |
| 254 | is responsible for. |
254 | is responsible for. |
| 255 | </p> |
255 | </p> |
| … | |
… | |
| 363 | <li> |
363 | <li> |
| 364 | deliberately go against the decisions made policy-wise or through a |
364 | deliberately go against the decisions made policy-wise or through a |
| 365 | consensus-model on the Gentoo Documentation mailinglist |
365 | consensus-model on the Gentoo Documentation mailinglist |
| 366 | </li> |
366 | </li> |
| 367 | <li> |
367 | <li> |
| 368 | not performing at all for a long time without informing the GDP and without |
368 | not performing at all for a long time without informing the GDP, and without |
| 369 | replying to the Operational Manager's request for a status update |
369 | replying to the Operational Manager's request for a status update |
| 370 | </li> |
370 | </li> |
| 371 | </ul> |
371 | </ul> |
| 372 | |
372 | |
| 373 | <p> |
373 | <p> |
| … | |
… | |
| 378 | </body> |
378 | </body> |
| 379 | </section> |
379 | </section> |
| 380 | </chapter> |
380 | </chapter> |
| 381 | |
381 | |
| 382 | <chapter> |
382 | <chapter> |
| 383 | <title>Documentation Team Recruitement</title> |
383 | <title>Documentation Team Recruitment</title> |
| 384 | <section> |
384 | <section> |
| 385 | <title>Contributors, Authors, Translators</title> |
385 | <title>Contributors, Authors, Translators</title> |
| 386 | <body> |
386 | <body> |
| 387 | |
387 | |
| 388 | <p> |
388 | <p> |
| 389 | Everyone interested in contributing documentation, editing existing |
389 | Everyone interested in contributing documentation, editing existing |
| 390 | documentation, writing new documentation or translating documentation is |
390 | documentation, writing new documentation or translating documentation is |
| 391 | welcome to join the team. There are no rules or strings attached to |
391 | welcome to join the team. There are no rules or strings attached to |
| 392 | this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c> |
392 | this. Just make sure you are subscribed to <c>gentoo-doc@gentoo.org</c>, |
| 393 | and you have fully read this policy and understand it. |
393 | and you have fully read this policy and understand it. |
| 394 | </p> |
394 | </p> |
| 395 | |
395 | |
| 396 | </body> |
396 | </body> |
| 397 | </section> |
397 | </section> |
| … | |
… | |
| 459 | An update constitutes a non-trivial update to any documentation, translation or |
459 | An update constitutes a non-trivial update to any documentation, translation or |
| 460 | otherwise, completely written by the contributor and committed after review by |
460 | otherwise, completely written by the contributor and committed after review by |
| 461 | any existing documentation developer. The period is fixed - increasing the |
461 | any existing documentation developer. The period is fixed - increasing the |
| 462 | contributions does not decrease the period. Also, we don't average the |
462 | contributions does not decrease the period. Also, we don't average the |
| 463 | contributions over time to make sure the contributor doesn't give a contribution |
463 | contributions over time to make sure the contributor doesn't give a contribution |
| 464 | burst and then waits until the Phase is over. |
464 | burst, and then waits until the Phase is over. |
| 465 | </p> |
465 | </p> |
| 466 | |
466 | |
| 467 | <p> |
467 | <p> |
| 468 | Without this phase we can not know if the contributor understands what it takes |
468 | Without this phase we can not know if the contributor understands what it takes |
| 469 | to be a documentation developer. The validation of this activity happens through |
469 | to be a documentation developer. The validation of this activity happens through |
| … | |
… | |
| 476 | </p> |
476 | </p> |
| 477 | |
477 | |
| 478 | <p> |
478 | <p> |
| 479 | If you feel that you have shown sufficient amount of contributions, contact |
479 | If you feel that you have shown sufficient amount of contributions, contact |
| 480 | the Operational Manager of the Gentoo Documentation Project. He |
480 | the Operational Manager of the Gentoo Documentation Project. He |
| 481 | will ask you for your coordinates and other information and then arrange |
481 | will ask you for your coordinates and other information, and then arrange |
| 482 | for the next phase to be started. |
482 | for the next phase to be started. |
| 483 | </p> |
483 | </p> |
| 484 | |
484 | |
| 485 | </body> |
485 | </body> |
| 486 | </section> |
486 | </section> |
Parent Directory
| 
Revision Log
| 
Patch