[dev-ref] (fr) Proofread [ Cédric Boutillier ] <20120115062330.GB32192@spin>

[developers-reference.git] / new-maintainer.dbk

diff --git a/new-maintainer.dbk b/new-maintainer.dbk
index 3f71082311098a80cb946a5d2410d4e6b3dc61eb..eac77378ffdfaa445541dff7ea575d22f3b7e5b9 100644 (file)
--- a/new-maintainer.dbk
+++ b/new-maintainer.dbk
@@ -18,10 +18,10 @@ developer so that your work can be incorporated into the Project?
 <para>
 Firstly, subscribe to &email-debian-devel; if you haven't
 already.  Send the word <literal>subscribe</literal> in the
 <para>
 Firstly, subscribe to &email-debian-devel; if you haven't
 already.  Send the word <literal>subscribe</literal> in the

-<emphasis>Subject</emphasis> of an email to
+<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
 &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"/> .
+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.
 </para>
 &email-debian-devel-announce; is another list which is
 mandatory for anyone who wishes to follow Debian's development.
 </para>


@@ -34,7 +34,7 @@ something to avoid duplicated effort.
 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
 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="irc-channels"/>.

 </para>
 <para>
 When you know how you want to contribute to &debian-formal;,
 </para>
 <para>
 When you know how you want to contribute to &debian-formal;,


@@ -77,17 +77,12 @@ In addition, if you have some packages ready for inclusion in Debian, but are
 waiting for your new maintainer application to go through, you might be able
 find a sponsor to upload your package for you.  Sponsors are people who are
 official Debian Developers, and who are willing to criticize and upload your
 waiting for your new maintainer application to go through, you might be able
 find a sponsor to upload your package for you.  Sponsors are people who are
 official Debian Developers, and who are willing to criticize and upload your

-packages for you.
-<!-- FIXME - out of order
-Those who are seeking a
-sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/"></ulink>.
--->
-Please read the unofficial debian-mentors FAQ at <ulink
+packages for you. Please read the debian-mentors FAQ at <ulink

 url="&url-mentors;"></ulink> first.
 </para>
 <para>
 If you wish to be a mentor and/or sponsor, more information is available in
 url="&url-mentors;"></ulink> first.
 </para>
 <para>
 If you wish to be a mentor and/or sponsor, more information is available in

-<xref linkend="newmaint"/> .
+<xref linkend="newmaint"/>.

 </para>
 </section>
 
 </para>
 </section>
 


@@ -147,19 +142,20 @@ human error than to software failure or high-powered spy techniques.  See <xref
 linkend="key-maint"/> for more information on maintaining your public key.
 </para>
 <para>
 linkend="key-maint"/> for more information on maintaining your public key.
 </para>
 <para>

-Debian uses the <command>GNU Privacy Guard</command> (package <systemitem
+Debian uses the <literal>GNU Privacy Guard</literal> (package <systemitem

 role="package">gnupg</systemitem> version 1 or better) as its baseline
 standard.  You can use some other implementation of OpenPGP as well.  Note that
 OpenPGP is an open standard based on <ulink
 url="&url-rfc2440;">RFC 2440</ulink>.
 </para>
 <para>
 role="package">gnupg</systemitem> version 1 or better) as its baseline
 standard.  You can use some other implementation of OpenPGP as well.  Note that
 OpenPGP is an open standard based on <ulink
 url="&url-rfc2440;">RFC 2440</ulink>.
 </para>
 <para>

-You need a version 4 key for use in Debian Development.  Your key length must
-be at least 1024 bits; there is no reason to use a smaller key, and doing so
-would be much less secure.  <footnote><para> Version 4 keys are keys conforming
+You need a version 4 key for use in Debian Development. <ulink
+url="http://lists.debian.org/20090520092534.GG22906@earth.li">Your key length must
+be greater than 1024 bits</ulink>; there is no reason to use a smaller key, and doing so
+would be much less secure.<footnote><para> Version 4 keys are keys conforming

 to the OpenPGP standard as defined in RFC 2440.  Version 4 is the key type that
 has always been created when using GnuPG.  PGP versions since 5.x also could
 to the OpenPGP standard as defined in RFC 2440.  Version 4 is the key type that
 has always been created when using GnuPG.  PGP versions since 5.x also could

-create v4 keys, the other choice having beein pgp 2.6.x compatible v3 keys
+create v4 keys, the other choice having been pgp 2.6.x compatible v3 keys

 (also called legacy RSA by PGP).  </para> <para> Version 4 (primary) keys can
 either use the RSA or the DSA algorithms, so this has nothing to do with
 GnuPG's question about which kind of key do you want: (1) DSA and Elgamal, (2)
 (also called legacy RSA by PGP).  </para> <para> Version 4 (primary) keys can
 either use the RSA or the DSA algorithms, so this has nothing to do with
 GnuPG's question about which kind of key do you want: (1) DSA and Elgamal, (2)


@@ -167,7 +163,7 @@ DSA (sign only), (5) RSA (sign only).  If you don't have any special
 requirements just pick the default.  </para> <para> The easiest way to tell
 whether an existing key is a v4 key or a v3 (or v2) key is to look at the
 fingerprint: Fingerprints of version 4 keys are the SHA-1 hash of some key
 requirements just pick the default.  </para> <para> The easiest way to tell
 whether an existing key is a v4 key or a v3 (or v2) key is to look at the
 fingerprint: Fingerprints of version 4 keys are the SHA-1 hash of some key

-matieral, so they are 40 hex digits, usually grouped in blocks of 4.
+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>
 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>


@@ -196,7 +192,7 @@ can make special arrangements.
 </para>
 <para>
 To apply as a new maintainer, you need an existing Debian Developer to support
 </para>
 <para>
 To apply as a new maintainer, you need an existing Debian Developer to support

-your application (an <emphasis>advocate</emphasis>).  After you have
+your application (an <literal>advocate</literal>).  After you have

 contributed to Debian for a while, and you want to apply to become a registered
 developer, an existing developer with whom you have worked over the past months
 has to express their belief that you can contribute to Debian successfully.
 contributed to Debian for a while, and you want to apply to become a registered
 developer, an existing developer with whom you have worked over the past months
 has to express their belief that you can contribute to Debian successfully.