translation-quick-start-guide/en_US doc-entities.xml, 1.5, 1.6 rpm-info.xml, 1.3, 1.4 translation-quick-start.xml, 1.10, 1.11

Mon Aug 14 13:31:06 UTC 2006

Author: pfrields

Update of /cvs/docs/translation-quick-start-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5353/en_US

Modified Files:
	doc-entities.xml rpm-info.xml translation-quick-start.xml 
Log Message:
Correct procedure and do a little editorial work; bump to 0.3.5


Index: doc-entities.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/en_US/doc-entities.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6

--- doc-entities.xml	11 Aug 2006 02:32:55 -0000	1.5
+++ doc-entities.xml	14 Aug 2006 13:31:04 -0000	1.6
@@ -10,11 +10,11 @@
     </entity>
     <entity name="DOCVERSION">
       <comment>Document version</comment>
-      <text>0.3.4</text>
+      <text>0.3.5</text>
     </entity>
     <entity name="DOCDATE">
       <comment>Revision date</comment>
-      <text>2006-08-10</text>
+      <text>2006-08-14</text>
     </entity>
     <entity name="DOCID">
       <comment>Revision ID</comment>


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/en_US/rpm-info.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.xml	11 Aug 2006 02:32:55 -0000	1.3
+++ rpm-info.xml	14 Aug 2006 13:31:04 -0000	1.4
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 
-<!DOCTYPE rpm-info SYSTEM "${fdpdir}/docs-common/packaging/rpm-info.dtd">
+<!DOCTYPE rpm-info SYSTEM "../../docs-common/packaging/rpm-info.dtd">
 
 <rpm-info>
   <colophon>
@@ -47,6 +47,10 @@
   <title>Translation Quick Start Guide</title>
   <desc>Quick start guide to providing translations on the Fedora Project.</desc>
   <changelog order="newest-first">
+    <revision date="2006-08-14" number="0.3.5" role="doc">
+      <author worker="PaulWFrields"/>
+      <details>Editorial pass, revising procedure to match proper ordering</details>
+    </revision>
     <revision date="2006-08-10" number="0.3.4" role="doc">
       <author worker="ManuelOspina"/>
       <details>Additional information about joining the Docs Project and GPG.</details>


Index: translation-quick-start.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/en_US/translation-quick-start.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- translation-quick-start.xml	14 Aug 2006 01:10:09 -0000	1.10
+++ translation-quick-start.xml	14 Aug 2006 13:31:04 -0000	1.11
@@ -111,54 +111,105 @@
     <section id="sn-accounts-docs">
       <title>Accounts for Documentation</title>
       <para>
-	If you plan to translate &FED; documentation, you should create a GPG key, 
-	since the &FDP; encourages all participants to sign e-mails.  To create a key,
-	use the	following command:
+	Follow this procedure to start working directly with the &FDP;
+	to translate documentation.
       </para>
+      <procedure>
+	<step>
+	  <para>
+	    The &FDP; encourages all participants to sign e-mails with a
+	    GPG key.  To create a key, use the following command:
+	  </para>
 
 <screen>
 <command>gpg --gen-key</command>
 </screen>
 
-      <para>
-	A series of prompts guides you through the process. Press
-	<keycap>Enter</keycap> to select the default values.
-      </para>
-      <para>
-	You must export your public key so other people can verify your
-	signature. Use this command to export your key to a public
-	server:
-      </para>
+	  <para>
+	    A series of prompts guides you through the process. Press
+	    <keycap>Enter</keycap> to select the default values.
+	  </para>
+	  <para>
+	    You must export your public key so other people can verify
+	    your signature. Use this command to export your key to a
+	    public server:
+	  </para>
 
 <screen>
 <command>gpg --keyserver pgp.mit.edu --send-keys GPGKEYID</command>
 </screen>
-      <para>After creating the GPG key, you can request a membership on the &FDP;
-	  mailing list. To do that, fill the form at <ulink
-	  url="http://www.redhat.com/mailman/listinfo/fedora-docs-list/"/>.
-	You should post a self-introduction to the &FDP; mailing
-	list.  For details, refer to <ulink
-	  url="http://fedoraproject.org/wiki/DocsProject/SelfIntroduction"/>.
-      </para>
-      <para>
-	You also need to sign up for a &FED; CVS account.  Visit <ulink
-	  url="https://admin.fedoraproject.com/accounts/"/> and follow the link 
-	  "Apply for a new account". After filling this form you will have a basic account. 
-	  Once you have an account, return to the same url and go to "Edit Your Account".
-	  Prompt the password you received by e-mail and go to "Add new membership" at
-	  the bottom of the page. In the fild "Groupname", add "cvsdocs" and click "add". 
-	  This action will give you access to the cvs repository where the documentation is stored. 
-      </para>
+
+	</step>
+	<step>
 	  <para>
-	  The next step is to create a wiki account. Fill the form at <ulink 
-	  url="http://fedoraproject.org/wiki/UserPreferences" />, and click on "Create Profile". 
-	  You need to contact a person with edit access and request her to being added on the Wiki 
-	  edit account in <ulink url="http://fedoraproject.org/wiki/EditGroup" />
-     </para>
-	 <para>
-	 Finally, you need to sign a Contributors License Agreement (CLA), refer to <ulink 
-	 url="http://fedoraproject.org/wiki/Infrastructure/AccountSystem/CLAHowTo" /> for instructions
-	 </para>
+	    Request a membership on the &FDP; mailing list. To do that,
+	    fill out the form at <ulink
+	      url="http://www.redhat.com/mailman/listinfo/fedora-docs-list/"/>.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    You should post a self-introduction to the &FDP; mailing
+	    list. For details, refer to <ulink
+	      url="http://fedoraproject.org/wiki/DocsProject/SelfIntroduction"/>.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    You also need to sign up for a &FED; account.  Visit <ulink
+	      url="https://admin.fedoraproject.com/accounts/"/> and
+	    select the link <guilabel>Apply for a new
+	      account</guilabel>. After filling out this form, you have
+	    a basic account.
+	  </para>
+	  <para>
+	    You must complete the Contributors License Agreement
+	    (<acronym>CLA</acronym>), refer to <ulink
+	      url="http://fedoraproject.org/wiki/Infrastructure/AccountSystem/CLAHowTo" 
+	      /> for instructions.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Once you have successfully completed the CLA, return to the
+	    account system and select <guilabel>Edit Your
+	      Account</guilabel>. Enter the password you received by
+	    email and select <guilabel>Add new membership</guilabel> at
+	    the bottom of the page.  In the field
+	    <guilabel>Groupname</guilabel>, enter
+	    <userinput>cvsdocs</userinput> and select
+	    <guilabel>Add</guilabel>.  This action requests access
+	    to the CVS repository where the documentation is stored.
+	  </para>
+	  <important>
+	    <title>CVS Access is Not Automatic</title>
+	    <para>
+	      When you fill out this form, you are not automatically
+	      granted write access to the CVS repository.  You may need
+	      sponsorship from one of the &FDP; managers to get this
+	      access.
+	    </para>
+	  </important>
+	</step>
+	<step>
+	  <para>
+	    The next step is to create a wiki account. Fill out the form
+	    at <ulink
+	      url="http://fedoraproject.org/wiki/UserPreferences" />,
+	    and select <guilabel>Create Profile</guilabel>.
+	  </para>
+	</step>
+	<step>
+	  <para>
+	    Contact any person with edit access and ask to be added to
+	    the Wiki edit account in <ulink
+	      url="http://fedoraproject.org/wiki/EditGroup" />.  You can
+	    do this on IRC or by posting on the
+	    <systemitem>fedora-docs-list</systemitem> mailing list you
+	    joined in a previous step.
+	  </para>
+	</step>
+      </procedure>
     </section>
 
   </section>


