swift       05/06/02 16:58:03

  Modified:    xml/htdocs/proj/en/gdp/doc doc-policy.xml
  Log:
  Rewrite sentences in policy to make it more clear. Part of #94519

Revision  Changes    Path
1.15      +75 -66    xml/htdocs/proj/en/gdp/doc/doc-policy.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/gdp/doc/doc-policy.xml?rev=1.15&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/gdp/doc/doc-policy.xml?rev=1.15&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/gdp/doc/doc-policy.xml.diff?r1=1.14&r2=1.15&cvsroot=gentoo

Index: doc-policy.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- doc-policy.xml      2 Jun 2005 16:48:26 -0000       1.14
+++ doc-policy.xml      2 Jun 2005 16:58:03 -0000       1.15
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v 
1.14 2005/06/02 16:48:26 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v 
1.15 2005/06/02 16:58:03 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -27,7 +27,7 @@
 
 <license/>
 
-<version>3.12</version>
+<version>3.13</version>
 <date>2005-06-02</date>
 
 <chapter>
@@ -40,7 +40,7 @@
 The Gentoo Linux Documentation team aspires to create exceptionally 
 professional documentation that is immediately clear and concise to the 
 end user. In order to fulfill this goal, we have very specific rules and 
-guidelines that <e>all</e> documentation must go through prior to 
+guidelines that <e>all</e> documentation must go through prior to
 dissemination on our website, or otherwise.
 </p>
 
@@ -72,9 +72,8 @@
 
 <p>
 The Gentoo Documentation Project Team is split into several smaller teams
-that operate in complete cooperation with each other. Each smaller team
-represents an active development team of a Gentoo Documentation
-Subproject.
+that work in tandem with each other. Each smaller team represents an active 
+development team of a Gentoo Documentation Subproject.
 </p>
 
 <p>
@@ -86,8 +85,8 @@
 
 <p>
 For day-to-day managerial tasks, the Gentoo Documentation Project has an
-Operational Manager. This person keeps track of all documentation-related tasks
-that are more short-term. The Operational Manager and Strategic Manager can be
+Operational Manager. This person keeps track of all short-term tasks
+related to documentation. The Operational Manager and Strategic Manager can be
 one and the same if the Strategic Manager wishes so.
 </p>
 
@@ -116,19 +115,20 @@
 <p>
 Every subproject has a Strategic Manager of its own and may have an 
 Operational Manager if deemed appropriate. His responsibilities to the Gentoo
-Documentation Project are the same as are listed on the <uri
+Documentation Project (GDP) are listed in the <e>Manager responsibilities</e>
+section of the <uri
 link="/doc/en/management-structure.xml#doc_chap1_sect5">Gentoo Management
-Structure</uri>.
+Structure</uri> document.
 </p>
 
 <p>
-The subprojects of the Gentoo Documentation Team together with their respective
-Strategic Managers are listed on the <uri link="/proj/en/gdp/">GDP
-Website</uri>. 
+Every subproject of the Gentoo Documentation Team is listed on the
+<uri link="/proj/en/gdp/">GDP Webpage</uri>, along with their respective 
+Strategic Managers.
 </p>
 
 <p>
-The decision on adding subprojects is in hands of the strategic Manager. 
+The decision on adding a subproject is in the hands of the Strategic Manager. 
 </p>
 
 </body>
@@ -155,15 +155,15 @@
 </p>
 
 <p>
-Every member of the Gentoo Documentation Team should be available at
+Members of the Gentoo Documentation Team should be available at
 <c>#gentoo-doc</c> on <uri 
link="http://www.freenode.net";>irc.freenode.net</uri>
-whenever he is online. 
+whenever they are online. 
 </p>
 
 <p>
-Depending on his responsibilities, he can have limited CVS 
-access to <c>cvs.gentoo.org</c>. Full CVS access can only be given to Gentoo
-developers. Read-only CVS access can be given to recruits.
+Depending on the assignment or responsibilities, a member may have limited CVS 
+access to <c>cvs.gentoo.org</c>. Full CVS access is restricted to Gentoo
+Developers. Read-only CVS access may be granted to recruits.
 </p>
 
 </body>
@@ -173,28 +173,37 @@
 <body>
 
 <p>
-Every language should be backed up by an official translation team. This
-team is lead by a Lead Translator and perhaps a Follow-up Lead Translator, who 
-both have CVS commit access. If for any reason the Lead Translator cannot
-perform his or her duties, the Follow-up Lead Translator is in charge. If
-even this person is unavailable, the mentor(s) is/are in charge of the 
language.
+Every language should be backed up by an official Translation Team. This
+team is led by a <e>Lead Translator</e> and perhaps a <e>Follow-On Lead 
+Translator</e>, who both have CVS commit access. If for any reason the 
+<e>Lead Translator</e> cannot perform his duties, the <e>Follow-On Lead 
+Translator</e> is in charge. If the <e>Follow-On</e> is unavailable, the 
+mentor(s) is/are in charge of the language.
 </p>
 
 <p>
-If a translated document is contributed, but the language in itself is
-not supported, the Gentoo Documentation Team will not publish it
-officially. In this case the document will stay unlinked until an official
-translation team of that language is formed.
+If a translated document for an unsupported language is contributed, the Gentoo
+Documentation Team will not publish it officially. Such documents shall not be 
+linked to the website until an official Translation Team of that language is 
+formed.
 </p>
 
 <p>
-When a language is officially supported, but the team doesn't have any
-members or no one wants to take on the responsibilities of the Lead
-Translator, all links to the documents will be removed from the site.
+When a language is officially supported, but the team does not have any
+members willing to take on the responsibilities of the <e>Lead
+Translator</e>, all links to the documents will be removed from the site.
 However, the documents will stay available in case the language becomes
 officially supported again.
 </p>
 
+<p>
+For more information Gentoo document translations, please consult the 
+<uri link="/proj/en/gdp/doc/translators-howto.xml">
+Translators Howto for Gentoo Documentation</uri> and the 
+<uri link="/proj/en/gdp/international.xml">
+GDP Internationalisation Subproject</uri> page.
+</p>
+
 </body>
 </section>
 </chapter>
@@ -240,17 +249,17 @@
 in a timely fashion, the reporter of that bug should be informed about
 this using a comment on the bug and the bug should be registered in the 
 <uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if 
-applicable. The Tactical or Operational Manager may decide that a bug has a
-higher priority and should be addressed ahead any other task the assingee
-is responsible of.
+applicable. The Strategic or Operational Manager may decide that a bug has a
+higher priority and should be addressed ahead any other task the assignee
+is responsible for.
 </p>
 
 <p>
 Whenever a Gentoo Documentation Team member takes care of a bug, he or
 she should assign the bug to herself/himself, but make sure that
-<c>[EMAIL PROTECTED]</c> is on the Cc-list. Unless with the consent
-of the Operational Manager, a bug may not be taken away from another
-Gentoo Documentation Team member without their approval.
+<c>[EMAIL PROTECTED]</c> is on the Cc-list. A bug may not be taken away from
+another Gentoo Documentation Team member without their approval; unless consent
+has been received from the Operational Manager.
 </p>
 
 </body>
@@ -260,10 +269,10 @@
 <body>
 
 <p>
-Every document the Gentoo Documentation Team develops can be developed as the
-related parties see fit. However, when the document is finished, it should be
-transformed into <uri link="/doc/en/xml-guide.xml">GuideXML</uri> and put
-available on the Gentoo CVS infrastructure. It must also be registered in the
+Every Gentoo Documentation Team may handle documentation development as it sees
+fit. However, when the document is finished, it should be transformed into 
+<uri link="/doc/en/xml-guide.xml">GuideXML</uri> and made available on the 
+Gentoo CVS infrastructure. It must also be registered in the
 <uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file if
 applicable.
 </p>
@@ -308,31 +317,32 @@
 <body>
 
 <p>
-To keep a high-pace development cycle of the documentation, technical or
-intrusive changes to documents can be propagated immediately to the document
        <<Truncated>>


-- 
[email protected] mailing list

Reply via email to