X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=new-maintainer.dbk;h=eac77378ffdfaa445541dff7ea575d22f3b7e5b9;hb=8e5bea309b68373c2d1e2038f22cd2ce241018c0;hp=3f4a077ba3a73bf3e43971b63029da044aa141c0;hpb=e3cb6d3f6afc7f8ed94ea6021aa0f9b4fa0e5551;p=developers-reference.git
diff --git a/new-maintainer.dbk b/new-maintainer.dbk
index 3f4a077..eac7737 100644
--- a/new-maintainer.dbk
+++ b/new-maintainer.dbk
@@ -18,10 +18,10 @@ developer so that your work can be incorporated into the Project?
Firstly, subscribe to &email-debian-devel; if you haven't
already. Send the word subscribe in the
-Subject of an email to
+Subject 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 .
+available mailing lists can be found in .
&email-debian-devel-announce; is another list which is
mandatory for anyone who wishes to follow Debian's development.
@@ -34,7 +34,7 @@ something to avoid duplicated effort.
Another good list to subscribe to is &email-debian-mentors;.
See for details. The IRC channel
#debian can also be helpful; see .
+linkend="irc-channels"/>.
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
-packages for you.
-
-Please read the unofficial debian-mentors FAQ at first.
If you wish to be a mentor and/or sponsor, more information is available in
- .
+.
@@ -147,19 +142,20 @@ human error than to software failure or high-powered spy techniques. See for more information on maintaining your public key.
-Debian uses the GNU Privacy Guard (package GNU Privacy Guard (package gnupg 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 RFC 2440.
-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. Version 4 keys are keys conforming
+You need a version 4 key for use in Debian Development. Your key length must
+be greater than 1024 bits; there is no reason to use a smaller key, and doing so
+would be much less secure. 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
-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). 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)
@@ -196,7 +192,7 @@ can make special arrangements.
To apply as a new maintainer, you need an existing Debian Developer to support
-your application (an advocate). After you have
+your application (an advocate). 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.