#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:11
msgid ""
-"So, you've read all the documentation, you've gone through the <ulink "
-"url=\"&url-newmaint-guide;\">Debian New Maintainers' Guide</ulink>, "
-"understand what everything in the <systemitem "
-"role=\"package\">hello</systemitem> example package is for, and you're about "
-"to Debianize your favorite piece of software. How do you actually become a "
-"Debian developer so that your work can be incorporated into the Project?"
+"So, you've read all the documentation, you've gone through the <ulink url="
+"\"&url-newmaint-guide;\">Debian New Maintainers' Guide</ulink>, understand "
+"what everything in the <systemitem role=\"package\">hello</systemitem> "
+"example package is for, and you're about to Debianize your favorite piece of "
+"software. How do you actually become a Debian developer so that your work "
+"can be incorporated into the Project?"
msgstr ""
#. type: Content of: <chapter><section><para>
"word <literal>subscribe</literal> in the <literal>Subject</literal> of an "
"email to &email-debian-devel-req;. In case of problems, contact the list "
"administrator at &email-listmaster;. More information on available mailing "
-"lists can be found in <xref linkend=\"mailing-lists\"/>. "
-"&email-debian-devel-announce; is another list which is mandatory for anyone "
-"who wishes to follow Debian's development."
+"lists can be found in <xref linkend=\"mailing-lists\"/>. &email-debian-"
+"devel-announce; is another list which is mandatory for anyone who wishes to "
+"follow Debian's development."
msgstr ""
#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:34
msgid ""
"Another good list to subscribe to is &email-debian-mentors;. See <xref "
-"linkend=\"mentors\"/> for details. The IRC channel "
-"<literal>#debian</literal> can also be helpful; see <xref "
-"linkend=\"irc-channels\"/>."
+"linkend=\"mentors\"/> for details. The IRC channel <literal>#debian</"
+"literal> can also be helpful; see <xref linkend=\"irc-channels\"/>."
msgstr ""
#. type: Content of: <chapter><section><para>
"if you are interested in packaging existing software for Debian, you should "
"try to get a sponsor. A sponsor will work together with you on your package "
"and upload it to the Debian archive once they are happy with the packaging "
-"work you have done. You can find a sponsor by mailing the "
-"&email-debian-mentors; mailing list, describing your package and yourself "
-"and asking for a sponsor (see <xref linkend=\"sponsoring\"/> and <ulink "
-"url=\"&url-mentors;\"></ulink> for more information on sponsoring). On the "
-"other hand, if you are interested in porting Debian to alternative "
-"architectures or kernels you can subscribe to port specific mailing lists "
-"and ask there how to get started. Finally, if you are interested in "
-"documentation or Quality Assurance (QA) work you can join maintainers "
-"already working on these tasks and submit patches and improvements."
+"work you have done. You can find a sponsor by mailing the &email-debian-"
+"mentors; mailing list, describing your package and yourself and asking for a "
+"sponsor (see <xref linkend=\"sponsoring\"/> and <ulink url=\"&url-mentors;"
+"\"></ulink> for more information on sponsoring). On the other hand, if you "
+"are interested in porting Debian to alternative architectures or kernels you "
+"can subscribe to port specific mailing lists and ask there how to get "
+"started. Finally, if you are interested in documentation or Quality "
+"Assurance (QA) work you can join maintainers already working on these tasks "
+"and submit patches and improvements."
msgstr ""
#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:57
msgid ""
"One pitfall could be a too-generic local part in your mailadress: Terms like "
-"mail, admin, root, master should be avoided, please see <ulink "
-"url=\"&url-debian-lists;\"></ulink> for details."
+"mail, admin, root, master should be avoided, please see <ulink url=\"&url-"
+"debian-lists;\"></ulink> for details."
msgstr ""
#. type: Content of: <chapter><section><title>
"to that list and an experienced developer will volunteer to help."
msgstr ""
+#
#. FIXME - out of order
#. Those who are seeking a
#. sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/">
#. </ulink>.
-#
#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:76
msgid ""
"all the information available at the <ulink url=\"&url-newmaint;\">New "
"Maintainer's Corner</ulink>. It describes in detail the preparations you "
"have to do before you can register to become a Debian developer. For "
-"example, before you apply, you have to read the <ulink "
-"url=\"&url-social-contract;\">Debian Social Contract</ulink>. Registering "
-"as a developer means that you agree with and pledge to uphold the Debian "
-"Social Contract; it is very important that maintainers are in accord with "
-"the essential ideas behind &debian-formal;. Reading the <ulink "
-"url=\"&url-gnu-manifesto;\">GNU Manifesto</ulink> would also be a good idea."
+"example, before you apply, you have to read the <ulink url=\"&url-social-"
+"contract;\">Debian Social Contract</ulink>. Registering as a developer "
+"means that you agree with and pledge to uphold the Debian Social Contract; "
+"it is very important that maintainers are in accord with the essential ideas "
+"behind &debian-formal;. Reading the <ulink url=\"&url-gnu-manifesto;\">GNU "
+"Manifesto</ulink> would also be a good idea."
msgstr ""
#. type: Content of: <chapter><section><para>
msgid ""
"The process of registering as a developer is a process of verifying your "
"identity and intentions, and checking your technical skills. As the number "
-"of people working on &debian-formal; has grown to over "
-"&number-of-maintainers; and our systems are used in several very important "
-"places, we have to be careful about being compromised. Therefore, we need "
-"to verify new maintainers before we can give them accounts on our servers "
-"and let them upload packages."
+"of people working on &debian-formal; has grown to over &number-of-"
+"maintainers; and our systems are used in several very important places, we "
+"have to be careful about being compromised. Therefore, we need to verify "
+"new maintainers before we can give them accounts on our servers and let them "
+"upload packages."
msgstr ""
#. type: Content of: <chapter><section><para>
"SHA-1 hash of some key material, so they are 40 hex digits, usually grouped "
"in blocks of 4. Fingerprints of older key format versions used MD5 and are "
"generally shown in blocks of 2 hex digits. For example if your fingerprint "
-"looks like "
-"<literal>5B00 C96D 5D54 AEE1 206B AF84 DE7A AF6E 94C0 9C7F</literal> then "
-"it's a v4 key."
+"looks like <literal>5B00 C96D 5D54 AEE1 206B AF84 DE7A AF6E 94C0 9C7F</"
+"literal> then it's a v4 key."
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
#: new-maintainer.dbk:182
msgid ""
"If your public key isn't on a public key server such as &pgp-keyserv;, "
-"please read the documentation available at <ulink "
-"url=\"&url-newmaint-id;\">NM Step 2: Identification</ulink>. That document "
-"contains instructions on how to put your key on the public key servers. The "
-"New Maintainer Group will put your public key on the servers if it isn't "
-"already there."
+"please read the documentation available at <ulink url=\"&url-newmaint-id;"
+"\">NM Step 2: Identification</ulink>. That document contains instructions "
+"on how to put your key on the public key servers. The New Maintainer Group "
+"will put your public key on the servers if it isn't already there."
msgstr ""
#. type: Content of: <chapter><section><para>
msgid ""
"When you have found an advocate, have your GnuPG key signed and have already "
"contributed to Debian for a while, you're ready to apply. You can simply "
-"register on our <ulink url=\"&url-newmaint-apply;\">application "
-"page</ulink>. After you have signed up, your advocate has to confirm your "
+"register on our <ulink url=\"&url-newmaint-apply;\">application page</"
+"ulink>. After you have signed up, your advocate has to confirm your "
"application. When your advocate has completed this step you will be "
"assigned an Application Manager who will go with you through the necessary "
"steps of the New Maintainer process. You can always check your status on "