translation-quick-start-guide/en_US Accounts_And_Subscriptions.xml, 1.4, 1.5
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Wed Oct 3 02:53:59 UTC 2007
- Previous message (by thread): release-notes/devel/po release-notes.pot, 1.16, 1.17 bn_IN.po, 1.10, 1.11 ca.po, 1.14, 1.15 cs.po, 1.13, 1.14 da.po, 1.16, 1.17 de.po, 1.48, 1.49 el.po, 1.71, 1.72 es.po, 1.60, 1.61 fi.po, 1.39, 1.40 fr.po, 1.22, 1.23 gu.po, 1.13, 1.14 hr.po, 1.16, 1.17 hu.po, 1.25, 1.26 it.po, 1.57, 1.58 ja.po, 1.50, 1.51 ms.po, 1.15, 1.16 nb.po, 1.16, 1.17 nl.po, 1.33, 1.34 pa.po, 1.47, 1.48 pl.po, 1.37, 1.38 pt_BR.po, 1.66, 1.67 pt.po, 1.82, 1.83 ru.po, 1.31, 1.32 sr at Latn.po, 1.8, 1.9 sr.po, 1.53, 1.54 sv.po, 1.55, 1.56 ta.po, 1.13, 1.14 uk.po, 1.32, 1.33 zh_CN.po, 1.47, 1.48 zh_TW.po, 1.9, 1.10
- Next message (by thread): release-notes/devel/po es.po,1.61,1.62
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: pfrields
Update of /cvs/docs/translation-quick-start-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18640
Modified Files:
Accounts_And_Subscriptions.xml
Log Message:
- Style and grammar checks
- Substitute entities where appropriate
- Take the pain of reformatting now, to avoid doing more later
Index: Accounts_And_Subscriptions.xml
===================================================================
RCS file: /cvs/docs/translation-quick-start-guide/en_US/Accounts_And_Subscriptions.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Accounts_And_Subscriptions.xml 27 Sep 2007 02:04:05 -0000 1.4
+++ Accounts_And_Subscriptions.xml 3 Oct 2007 02:53:57 -0000 1.5
@@ -10,294 +10,369 @@
]>
- <section id="sn_accounts">
- <title>Accounts and Subscriptions</title>
- <para>
- First and most important step to become Fedora Translator is to obtain an account and subscription(s). At the end of this chapter, you should successfully complete all steps requiring to obtain your account and subscription(s). Any question, feel free to post in the lists or ask for help at iirc (irc.freenode.org/#fedora-l10n).
- </para>
+<section id="sn_accounts">
+ <title>Accounts and Subscriptions</title>
+ <para>
+ To become a Fedora Translator, you must sign up for accounts and
+ subscriptions as described in this chapter. If you have questions,
+ post them on the fedora-trans-list, or ask for help via Internet
+ Relay Chat, or <acronym>IRC</acronym>, at <systemitem
+ class="fqdomainname">irc.freenode.org</systemitem> on channel
+ <systemitem>#fedora-l10n</systemitem>.
+ </para>
<section id="signup-ml">
- <title>Sign up to the mailing list</title>
- <procedure>
- <step>
- <para>
- Visit <ulink url="https://listman.redhat.com/mailman/listinfo/fedora-trans-list/"/> and subscribe to the main translation mailing list.
- </para>
- </step>
- <step>
- <para>
- You will receive a confirmation email which contains a link. Click it!
- </para>
- </step>
- <step>
- <para>
- Check out <ulink url="http://fedoraproject.org/wiki/L10N/Teams/"/> to see if there is a special mailing list for your language. If yes, subscribe to that too.
- </para>
- </step>
- </procedure>
+ <title>Subscribing to the Mailing List</title>
+ <procedure>
+ <step>
+ <para>
+ Visit <ulink
+ url="https://listman.redhat.com/mailman/listinfo/fedora-trans-list/"/>
+ and subscribe to the main translation mailing list.
+ </para>
+ </step>
+ <step>
+ <para>
+ Wait for the confirmation email which contains a link to
+ confirm your subscription. Click the link to confirm your
+ subscription.
+ </para>
+ </step>
+ <step>
+ <para>
+ Check <ulink url="http://fedoraproject.org/wiki/L10N/Teams/"/>
+ to see if there is a special mailing list for your language.
+ If so, subscribe to that list too.
+ </para>
+ </step>
+ </procedure>
</section>
- <section id="sn-ssh-key">
- <title>Making a SSH Key</title>
+ <section id="sn-ssh-key">
+ <title>Making a SSH Key</title>
- <para>
+ <para>
If you already have an existing SSH key, you can use it for Fedora
work. In that case, proceed to <xref
linkend="st-change-permissions"/> in the following procedure. If
you do not have a SSH key yet, start with the first step below:
- </para>
+ </para>
- <procedure>
- <step>
- <para>
- Enter the following command:
- </para>
+ <procedure>
+ <step>
+ <para>
+ Enter the following command:
+ </para>
-<screen>
-<command>ssh-keygen -t dsa</command>
-</screen>
+ <screen><command>ssh-keygen -t dsa</command></screen>
+ <para>
+ Accept the default location
+ (<filename>~/.ssh/id_dsa</filename>) and enter a passphrase.
+ </para>
+ <caution>
+ <title>Remember Your Passphrase</title>
<para>
- Accept the default location
- (<filename>~/.ssh/id_dsa</filename>) and enter a passphrase.
- </para>
- <caution>
- <title>Remember Your Passphrase</title>
- <para>
- You must have your passphrase to access to the CVS
- repository. It cannot be recovered if you forget it.
- </para>
- </caution>
- </step>
- <step id="st-change-permissions">
- <para>
- Change permissions to your key and <filename>.ssh</filename>
- directory:
+ You must have your passphrase to access to the CVS
+ repository. It cannot be recovered if you forget it.
</para>
+ </caution>
+ </step>
+ <step id="st-change-permissions">
+ <para>
+ Change permissions to your key and <filename>.ssh</filename>
+ directory:
+ </para>
-<screen>
-<command>chmod 700 ~/.ssh</command>
-<command>chmod 600 ~/.ssh/id_dsa</command>
-<command>chmod 644 ~/.ssh/id_dsa.pub</command>
-</screen>
+ <screen><command>chmod 700 ~/.ssh
+chmod 600 ~/.ssh/id_dsa
+chmod 644 ~/.ssh/id_dsa.pub</command></screen>
- </step>
- <step>
- <para>
- Copy and paste the SSH key in the space provided in order to
- complete the account application.
- </para>
- </step>
- </procedure>
- </section>
+ </step>
+ <step>
+ <para>
+ Copy and paste the SSH key in the space provided in order to
+ complete the account application.
+ </para>
+ </step>
+ </procedure>
+ </section>
<section id="sn-gpg-key">
- <title>Making a GPG Key</title>
- <procedure>
- <step>
- <para>
- Generate a key by typing in a command line:
- </para>
-<screen>
-<command>gpg --gen-key</command>
-</screen>
- <para>
- A series of prompts guides you through the process. The default values are usually OK. Choose a good password. Finally, your key will be created.
- </para>
- </step>
- <step>
- <para>
- Search for the part saying something like "pub 1024D/1B2AFA1C". Your Key ID is the 8-digit-long hex word after the '/' (in this example, the GPG Key ID is "1B2AFA1C"). Yours will be different; write it down.
- </para>
- </step>
- <step>
- <para>
- Export your public key to a public server (so that others can find it) by typing in a command line (substitute GPGKEYID with your key ID):
- </para>
-<screen>
-<command>gpg --keyserver pgp.mit.edu --send-keys GPGKEYID</command>
-</screen>
- </step>
- </procedure>
+ <title>Making a GPG Key</title>
+ <procedure>
+ <step>
+ <para>
+ Generate a key by typing in a command line:
+ </para>
+ <screen><command>gpg --gen-key</command></screen>
+ <para>
+ A series of prompts guides you through the process. The
+ default values suffice in almost all cases. Remember to choose
+ a good password.
+ </para>
+ <tip>
+ <title>Choosing a Good Password</title>
+ <para>A good password:</para>
+ <itemizedlist>
+ <listitem>
+ <para>consists of uppercase and lowercase letters,
+ numbers, punctuation, and other characters</para>
+ </listitem>
+ <listitem>
+ <para>does not include any words or names, with or without
+ substitutions</para>
+ </listitem>
+ <listitem>
+ <para>is not the same as any other password used for other
+ systems</para>
+ </listitem>
+ </itemizedlist>
+ </tip>
+ </step>
+ <step>
+ <para>
+ In the resulting text, find your key ID in the statement that
+ resembles "pub 1024D/1B2AFA1C". Your key ID is the 8
+ character "word" after the slash (<literal>/</literal>). In
+ the previous example, the GPG Key ID is
+ <literal>1B2AFA1C</literal>. Write down your key ID.
+ </para>
+ </step>
+ <step>
+ <para>
+ Export your public key to a public server so that others can
+ find it with the following command, substituting your key ID:
+ </para>
+ <screen><command>gpg --keyserver pgp.mit.edu --send-keys <replaceable>GPGKEYID</replaceable></command></screen>
+ </step>
+ </procedure>
</section>
<section id="sn-apply-account">
- <title>Apply for an account</title>
- <procedure>
- <step>
- <para>
- You need to sign up for a &FED; account. Visit <ulink url="https://admin.fedoraproject.org/accounts/"/> and select the link <guilabel>Apply for a new account</guilabel>.
- </para>
- </step>
- <step>
- <para>
- Fill in the form and choose a password for your Fedora account. You should now have a GPG keyID and an SSH key to use on the form. Also, in the Comments field write the languages you are planning on working on.
- </para>
- </step>
- </procedure>
+ <title>Applying for an Account</title>
+ <procedure>
+ <step>
+ <para>
+ To sign up for a &FED; account, first visit <ulink
+ url="https://admin.fedoraproject.org/accounts/"/> and select
+ <guilabel>Apply for a new account</guilabel>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Fill in the form and choose a password for your &FED; account.
+ Enter information for your GPG key ID and SSH key in the form.
+ In the <guilabel>Comments</guilabel> field, write the
+ languages you plan to work on.
+ </para>
+ </step>
+ </procedure>
</section>
<section id="sn-sign-cla">
- <title>Sign the CLA</title>
- <para>
- You must complete the Contributors License Agreement (<acronym>CLA</acronym>).
- </para>
- <procedure>
- <step>
- <para>Visit: https://admin.fedoraproject.org/accounts/send-cla.cgi. You should be able to authenticate using the username/password from the previous process.
- </para>
- </step>
- <step>
- <para>Check your emails. You should have received an email with an attachment. You are now going to sign this file and reply to the email. Save the attachment to your local computer (say, your Desktop).
- </para>
- </step>
- <step>
- <para>Edit the file with your favourite text editor (double-click on it). Type in it "I agree" and your full name.
- </para>
- </step>
- <step>
- <para>
- Digitally sign the text file using your GPG key (by providing your GPG password) with following command:
- </para>
-<screen>
-<command> gpg -a --sign fedora-icla-{username}.txt </command>
-</screen>
- <para>You now have another file on your Desktop that ends with .asc.
- </para>
- </step>
- <step>
- <para>
- Open again your email client and Reply to the CLA email. Attach the file which ends with .asc, and send the email.
- </para>
- </step>
- </procedure>
+ <title>Signing the CLA</title>
+ <para>
+ You must complete the Contributors License Agreement, or
+ <acronym>CLA</acronym>.
+ </para>
+ <procedure>
+ <step>
+ <para>Visit <ulink
+ url="https://admin.fedoraproject.org/accounts/send-cla.cgi"/>.
+ Authenticate using your username and password from the previous
+ process.
+ </para>
+ </step>
+ <step>
+ <para>Wait for receipt of an email with an attachment. The
+ attachment is an agreement you can sign and return. Save the
+ attachment to your Desktop.
+ </para>
+ </step>
+ <step>
+ <para>Double-click the file on your Desktop to open it with an
+ editor. Add the phrase "I agree" and your full name.
+ </para>
+ </step>
+ <step>
+ <para>
+ Digitally sign the text file using your GPG key with the
+ following command, providing your password when prompted:
+ </para>
+ <screen><command> gpg -a --sign fedora-icla-{username}.txt </command></screen>
+ <para>There is now a new file on your Desktop that ends with
+ <filename class="extension">.asc</filename>. This file is the
+ signed version of the CLA.
+ </para>
+ </step>
+ <step>
+ <para>
+ Open your email client again and reply to the CLA email.
+ Attach the signed file which ends with <filename
+ class="extension">.asc</filename>, and send the email.
+ </para>
+ </step>
+ </procedure>
</section>
<section id="sn-join-cvsl10n">
- <title>Join the cvsl10n group</title>
- <procedure>
- <step>
- <para>
- Visit: https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1
- </para>
- </step>
- <step>
- <para>
- Go to <guilabel>Add new membership</guilabel> at the bottom of the page. In the field <guilabel>Groupname</guilabel>, enter <userinput>cvsl10n</userinput> and select <guilabel>Add</guilabel>.
- </para>
- </step>
- <step>
- <para>
- At this point, an admin will be notified and will offer to sponsor you. This might take from some minutes up to a day or two.
- </para>
- </step>
- </procedure>
- <caution>
- <para>
- The rest of the steps help you test your access and grant you privileges to all the Fedora infrastructure you might need in the near future. Language maintainers and people starting new languages should follow them. Although they are optional for translations, everyone is encouraged to follow them.
- </para>
- </caution>
- <important>
- <para>
- Some of the Fedora modules are still hosted on the i18n.redhat.com system, which is not enabled to work with the cvsl10n group. To translate modules hosted there, please visit: http://i18n.redhat.com/cgi-bin/i18n-signup. This warning will probably be deprecated soon.
- </para>
- </important>
+ <title>Joining the <systemitem>cvsl10n</systemitem> Group</title>
+ <procedure>
+ <step>
+ <para>
+ Visit <ulink
+ url="https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1"/>.
+ Select <guilabel>Add new membership</guilabel> at the bottom
+ of the page. In the field <guilabel>Groupname</guilabel>,
+ enter <userinput>cvsl10n</userinput> and select
+ <guilabel>Add</guilabel>.
+ </para>
+ </step>
+ <step>
+ <para>
+ An administrator is notified of your application, and offers
+ to sponsor you. This may take between an hour and a few days.
+ </para>
+ </step>
+ </procedure>
+ <caution>
+ <para>
+ The rest of the steps help you test your access and grant you
+ privileges to all the &FED; infrastructure you might need in
+ the near future. Language maintainers and people starting new
+ languages should follow them. Although they are optional for
+ translations, everyone is encouraged to follow them.
+ </para>
+ </caution>
+ <important>
+ <para>
+ Some of the &FED; modules are still hosted on the <systemitem
+ class="fqdomainname">i18n.redhat.com</systemitem> system,
+ which is not enabled to work with the
+ <systemitem>cvsl10n</systemitem> group. To translate modules
+ hosted there, please visit <ulink
+ url="http://i18n.redhat.com/cgi-bin/i18n-signup"/>. This
+ warning may be deprecated soon.
+ </para>
+ </important>
</section>
<section id="sn-test-access">
- <title>Test your access</title>
- <procedure>
- <step>
- <para>
- # Install cvs (if you don't already have it) by typing in a command-line:
- </para>
-<screen>
-<command>su -c 'yum install cvs' </command>
-</screen>
- </step>
- <step>
- <para>
- Do a cvs checkout of some PO files by typing the following in a command-line (and substituting 'username' with your username). You will be asked the password for your SSH key.
- </para>
-<screen>
-<command>export CVSROOT=:ext:username at cvs.fedoraproject.org:/cvs/l10n
- cvs co web
- ls web/flpweb/po
-</command>
-</screen>
- </step>
+ <title>Testing Your Access</title>
+ <procedure>
+ <step>
+ <para>
+ Install the <package>cvs</package> package, if it is not
+ already installed, with the following command:
+ </para>
+ <screen><command>su -c 'yum install cvs'</command></screen>
+ </step>
+ <step>
+ <para>
+ Checkout some PO files with the following command, substituting your
+ username and providing your SSH key passphrase when prompted:
+ </para>
+ <screen><command>export CVSROOT=:ext:<replaceable>username</replaceable>@cvs.fedoraproject.org:/cvs/l10n
+cvs co web
+ls web/flpweb/po</command></screen>
+ </step>
</procedure>
</section>
<section id="sn-create-wikiacct">
- <title>Create a wiki account</title>
- <procedure>
- <step>
- <para>
- Visit <ulink url="http://fedoraproject.org/wiki/UserPreferences/"/>. As a username, choose something like 'FirstnameLastname' and click <guilabel>Create Profile</guilabel>.
- </para>
- </step>
- <step>
- <para>
- At this point, someone should give you Edit access on the wiki. Either contact someone from the Edit Group <ulink url="http://fedoraproject.org/wiki/EditGroup/"/> or add your name to the EditGroupQueue <ulink url="http://fedoraproject.org/wiki/EditGroupQueue/"/> and someone will add you shortly.
- </para>
- </step>
- <step>
- <para>
- If you are starting a new language, or want to step up as the maintainer of one, add your information on the L10N/Teams <ulink url="http://fedoraproject.org/wiki/L10N/Teams/"/> page.
- </para>
- </step>
- </procedure>
- </section>
+ <title>Creating a Wiki Account</title>
+ <procedure>
+ <step>
+ <para>
+ Visit <ulink
+ url="http://fedoraproject.org/wiki/UserPreferences/"/>. For
+ your username, choose a name like 'FirstnameLastname' and
+ select <guilabel>Create Profile</guilabel>.
+ </para>
+ </step>
+ <step>
+ <para>
+ A current wiki user can now give you Edit access on the wiki.
+ Contact someone from the Edit Group at <ulink
+ url="http://fedoraproject.org/wiki/EditGroup/"/>, or add
+ your name to the EditGroupQueue at <ulink
+ url="http://fedoraproject.org/wiki/EditGroupQueue/"/>, and
+ someone will add you shortly.
+ </para>
+ </step>
+ <step>
+ <para>
+ If you are starting a new language, or want to become the
+ maintainer of one, add your information on the L10N/Teams page
+ at <ulink url="http://fedoraproject.org/wiki/L10N/Teams/"/>.
+ </para>
+ </step>
+ </procedure>
+ </section>
<section id="sn-intro-yourself">
- <title>Introduce yourself</title>
- <procedure>
- <step>
- <para>
- Once you have edit access on the wiki, create a personal page at a URL like this: <ulink url="http://fedoraproject.org/wiki/FirstnameLastname/"/>. This is very useful for Fedora contributors to get to know and contact each other.
- </para>
- </step>
- <step>
- <para>
- Post a short self introduction <ulink url="http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/"/> to the <systemitem>fedora-trans-list</systemitem> mailing list and to the list of your local team.
- </para>
- </step>
+ <title>Introducing Yourself</title>
+ <procedure>
+ <step>
+ <para>
+ Once you have edit access on the wiki, create a personal
+ page.
+ at a URL like this: <ulink
+ url="http://fedoraproject.org/wiki/FirstnameLastname/"/>.
+ This is very useful for Fedora contributors to get to know and
+ contact each other.
+ </para>
+ </step>
+ <step>
+ <para>
+ Post a short self introduction <ulink
+ url="http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/"/>
+ to the <systemitem>fedora-trans-list</systemitem> mailing list
+ and to the list of your local team.
+ </para>
+ </step>
</procedure>
-</section>
+ </section>
<section id="sn-bugzilla-account">
- <title>Create a Bugzilla account</title>
- <para>
- Visit <ulink url="https://bugzilla.redhat.com/bugzilla/createaccount.cgi/"/> to create a Bugzilla account.
- </para>
+ <title>Create a &BZ; account</title>
+ <para>
+ Visit <ulink
+ url="https://bugzilla.redhat.com/bugzilla/createaccount.cgi/"/>
+ to create a &BZ; account.
+ </para>
</section>
<section id="sn-check-list">
- <title>Checklist</title>
- <para>
- At the end, you should have the following:
- </para>
- <itemizedlist>
- <listitem><para>Subscription to fedora-trans-list mailing list and, if there is one, to your own language's one</para></listitem>
- <listitem><para>One SSH key</para></listitem>
- <listitem><para>One GPG key</para></listitem>
- <listitem><para>A Fedora account</para></listitem>
- <listitem><para>Membership to the 'cvsl10n' group</para></listitem>
- <listitem><para>A wiki account</para></listitem>
- <listitem><para>Your language and translation team appear on <ulink url="http://fedoraproject.org/wiki/L10N/Teams/"/></para></listitem>
- <listitem><para>A bugzilla account</para></listitem>
- <listitem><para>A personal homepage on the wiki</para></listitem>
- <listitem><para>A self introduction sent to the mailing list</para></listitem>
- </itemizedlist>
- </section>
-
- <section id="sn-final">
- <title>Finally!</title>
- <para>
- Sit back and enjoy your achievement.
-
- You are now a fully recognized member of the Fedora community, capable of digitally signing documents and emails, submitting contributions to our CVS, publishing content on the wiki, submitting bugs, following the discussions of our groups and joining other Fedora teams!
- </para>
+ <title>Checklist</title>
+ <para>
+ You should now have the following:
+ </para>
+ <itemizedlist>
+ <listitem><para>Subscription to fedora-trans-list mailing list
+ and your locale-specific mailing list, if there is
+ one</para></listitem>
+ <listitem><para>A SSH key</para></listitem>
+ <listitem><para>A GPG key</para></listitem>
+ <listitem><para>A &FED; account</para></listitem>
+ <listitem><para>Membership in the <systemitem>cvsl10n</systemitem>
+ group</para></listitem>
+ <listitem><para>A wiki account</para></listitem>
+ <listitem><para>Your language and translation team appear on
+ <ulink
+ url="http://fedoraproject.org/wiki/L10N/Teams/"/></para></listitem>
+ <listitem><para>A &BZ; account</para></listitem>
+ <listitem><para>A personal homepage on the wiki</para></listitem>
+ <listitem><para>A self-introduction sent to the mailing
+ list</para></listitem>
+ </itemizedlist>
+ <para>
+ Sit back and enjoy your achievement. You are now a fully
+ recognized member of the Fedora community, capable of digitally
+ signing documents and emails, submitting contributions to our CVS,
+ publishing content on the wiki, submitting bugs, following the
+ discussions of our groups and joining other Fedora teams.
+ </para>
</section>
</section>
- Previous message (by thread): release-notes/devel/po release-notes.pot, 1.16, 1.17 bn_IN.po, 1.10, 1.11 ca.po, 1.14, 1.15 cs.po, 1.13, 1.14 da.po, 1.16, 1.17 de.po, 1.48, 1.49 el.po, 1.71, 1.72 es.po, 1.60, 1.61 fi.po, 1.39, 1.40 fr.po, 1.22, 1.23 gu.po, 1.13, 1.14 hr.po, 1.16, 1.17 hu.po, 1.25, 1.26 it.po, 1.57, 1.58 ja.po, 1.50, 1.51 ms.po, 1.15, 1.16 nb.po, 1.16, 1.17 nl.po, 1.33, 1.34 pa.po, 1.47, 1.48 pl.po, 1.37, 1.38 pt_BR.po, 1.66, 1.67 pt.po, 1.82, 1.83 ru.po, 1.31, 1.32 sr at Latn.po, 1.8, 1.9 sr.po, 1.53, 1.54 sv.po, 1.55, 1.56 ta.po, 1.13, 1.14 uk.po, 1.32, 1.33 zh_CN.po, 1.47, 1.48 zh_TW.po, 1.9, 1.10
- Next message (by thread): release-notes/devel/po es.po,1.61,1.62
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Fedora-docs-commits
mailing list