update the "Applying to Become a New Maintainer" section, with review

by Raphael Hertzog, closes: #133965

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@1432 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/common.ent b/common.ent
index 16b61b8aa45450f3806898826618901674502bad..61d5ae1071db067eebffc2d01d97c63a8027f00e 100644 (file)
--- a/common.ent
+++ b/common.ent
@@ -56,6 +56,9 @@
 <!entity url-newmaint-db "http://nm.debian.org/">
 <!entity url-newmaint-advocate "http://&www-debian-org;/devel/join/nm-advocate">
 <!entity url-newmaint-amchecklist "http://&www-debian-org;/devel/join/nm-amchecklist">
 <!entity url-newmaint-db "http://nm.debian.org/">
 <!entity url-newmaint-advocate "http://&www-debian-org;/devel/join/nm-advocate">
 <!entity url-newmaint-amchecklist "http://&www-debian-org;/devel/join/nm-amchecklist">

+<!entity url-newmaint-apply "http://nm.debian.org/newnm.php">
+<!entity url-newmaint-id "http://&www-debian-org;/devel/join/nm-step2">
+<!entity url-gpg-coord "http://nm.debian.org/gpg.php">

 
 <!entity url-debian-keyring "ftp://&ftp-debian-org;/debian/doc/debian-keyring.tar.gz">
 <!entity url-readme-non-us "ftp://&ftp-debian-org;/debian/README.non-US">
 
 <!entity url-debian-keyring "ftp://&ftp-debian-org;/debian/doc/debian-keyring.tar.gz">
 <!entity url-readme-non-us "ftp://&ftp-debian-org;/debian/README.non-US">

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 0c7c09b4ac8204a83ef62896ef9842666f25b6b9..ad1efc628674067e6b2127b2539f61385c492d72 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->

-  <!entity cvs-rev "$Revision: 1.75 $">
+  <!entity cvs-rev "$Revision: 1.76 $">

 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->


@@ -112,71 +112,68 @@ id="mentors"> for details.  The IRC channel <tt>#debian</tt> on the
 Linux People IRC network (e.g., <tt>irc.debian.org</tt>) can also be
 helpful.
 
 Linux People IRC network (e.g., <tt>irc.debian.org</tt>) can also be
 helpful.
 

+       <p>
+When you know how you want to contribute to the Debian Project, you
+should get in contact with existing Debian maintainers who are working
+on similar tasks.  That way, you can learn from experienced developers.
+For example, 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 he
+is 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 <ref id="sponsoring">
+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.
+ 

 
       <sect id="registering">Registering as a Debian developer
        <p>
 Before you decide to register with the Debian Project, you will need
 
       <sect id="registering">Registering as a Debian developer
        <p>
 Before you decide to register with the Debian Project, you will need

-to read the <url id="&url-social-contract;" name="Debian Social
-Contract">.  Registering as a developer means that you agree with and
+to read all the information available at the <url id="&url-newmaint;"
+name="New Maintainer's Corner">.  It describes exactly the preparations
+you have to do before you can register to become a Debian developer.
+
+For example, before you apply, you have to to read the
+<url id="&url-social-contract;" name="Debian Social Contract">.
+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
 GNU/Linux.  Reading the <url id="&url-gnu-manifesto;" name="GNU
 Manifesto"> would also be a good idea.
        <p>
 The process of registering as a developer is a process of verifying
 pledge to uphold the Debian Social Contract; it is very important that
 maintainers are in accord with the essential ideas behind Debian
 GNU/Linux.  Reading the <url id="&url-gnu-manifesto;" name="GNU
 Manifesto"> would also be a good idea.
        <p>
 The process of registering as a developer is a process of verifying

-your identity and intentions.  As the number of people working on
-Debian GNU/Linux has grown to over &number-of-maintainers; people 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.
-       <p>
-Registration requires that the following information be sent in
-appropriate steps described at <url id="&url-newmaint-checklist;"
-                                   name="Checklist for applicants">
-after the initial contact to &email-new-maintainer:
+your identity and intentions, and checking your technical skills.
+As the number of people working on Debian has grown to over
+&number-of-maintainers; people 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.
+       <p>
+Before you actually register you should have shown that you can do
+competent work and will be a good contributor.  You can show this by
+submitting patches through the Bug Tracking System or having a package
+sponsored by an existing maintainer for a while.  Also, we expect that
+contributors are interested in the whole project and not just in
+maintaining their own packages.  If you can help other maintainers by
+providing further information on a bug or even a patch, then do so!
+       <p>
+Registration requires that you are familiar with Debian's philosophy
+and technical documentation.  Furthermore, you need a GPG key which
+has been signed by an existing Debian maintainer.  If your GPG key
+is not signed yet, you should try to meet a Debian maintainer in
+person to get your key signed.  There's a <url id="&url-gpg-coord;"
+name="GPG Key Signing Coordination page"> which should help you find
+a maintainer close to you (If you cannot find a Debian maintainer
+close to you, there's an alternative way to pass the ID check.  You
+can send in a photo ID signed with your GPG key.  Having your GPG
+key signed is the preferred way, however.  See the
+<url id="&url-newmaint-id;" name="identification page"> for more
+information about these two options.)

 
 

-<list>
-           <item>
-Your name.
-           <item>
-Your preferred login name on <tt>master</tt> (eight characters or
-less), as well as the email address at which you'd prefer to be
-subscribed to &email-debian-private; (typically this will be either
-your primary mail address or your new <tt>debian.org</tt> address).
-           <item>
-A phone number where we can call you.  Remember that the new
-maintainer team usually calls during evening hours to save on long
-distance tolls.  Please do not give a work number, unless you are
-generally there in the evening.
-           <item>
-A statement of intention, that is, what package(s) you intend to work
-on, which Debian port you will be assisting, or how you intend to
-contribute to Debian.
-           <item>
-A statement that you have read and agree to uphold the <url
-id="&url-social-contract;" name="Debian Social Contract">.
-           <item>
-Some mechanism by which we can verify your real-life identity. For
-example, any of the following mechanisms would suffice:
-<list>
-                 <item>
-An OpenPGP key signed by any well-known signature, such as:
-<list>
-                       <item>
-Any current Debian developer you have met <em>in real life</em>.
-                       <item>
-Any formal certification service (such as Verisign, etc.) that
-verifies your identity.  A certification that verifies your email
-address, and not your identity, is not sufficient.
-                     </list>
-                 <item>
-Alternatively, you may identify yourself with a scanned (or physically
-mailed) copy of any formal documents certifying your identity (such as
-a birth certificate, national ID card, U.S. Driver's License, etc.).
-If emailed, please sign the mail with your OpenPGP key.
-               </list>
-         </list>

        <p>
 If you do not have an OpenPGP key yet, generate one. Every developer
 needs a OpenPGP key in order to sign and verify package uploads. You
        <p>
 If you do not have an OpenPGP key yet, generate one. Every developer
 needs a OpenPGP key in order to sign and verify package uploads. You


@@ -200,13 +197,6 @@ much less secure.  Your key must be signed with at least your own user
 ID; this prevents user ID tampering.  <prgn>gpg</prgn> does this
 automatically.
        <p>
 ID; this prevents user ID tampering.  <prgn>gpg</prgn> does this
 automatically.
        <p>

-Also remember that one of the names on your key must match the email
-address you list as the official maintainer for your packages.  For
-instance, I set the maintainer of the
-<package>developers-reference</package> package to ``Adam Di Carlo
-&lt;aph@debian.org&gt;''; therefore, one of the user IDs on my key is
-that same value, ``Adam Di Carlo &lt;aph@debian.org&gt;''.
-       <p>

 If your public key isn't on public key servers such as &pgp-keyserv;,
 please read the documentation available locally in &file-keyservs;.
 That document contains instructions on how to put your key on the
 If your public key isn't on public key servers such as &pgp-keyserv;,
 please read the documentation available locally in &file-keyservs;.
 That document contains instructions on how to put your key on the


@@ -227,28 +217,28 @@ cryptography <em>qua</em> cryptography in any manner.  If you live in a
 country where use of cryptography even for authentication is forbidden
 then please contact us so we can make special arrangements.
        <p>
 country where use of cryptography even for authentication is forbidden
 then please contact us so we can make special arrangements.
        <p>

-Once you have all your information ready, and your public key is
-available on public key servers, send a message to
-&email-new-maintainer; to register as an offical Debian developer so
-that you will be able to upload your packages.  This message must
-contain your name and your valid e-mail address.  All the information
-discussed above is required after your Application Manager is
-assigned.  Application Manager is your agent in the registration
-process, and you can always ask him about the status of your
-application. You can check the <url id="&url-newmaint-db;"
-name="Application StatusBoard"> as well.
+When you are ready to apply, you need an existing Debian maintainer
+to verify your application (an <em>advocate</em>).  After you have
+contributed to the Project and when you want to apply to become a
+registered developer, an existing developer with whom you
+have worked over the past months has to express his belief that you
+can contribute to the Project successfully.
+       <p>
+When you have found an advocate, have your GPG key signed and have
+already contributed to Debian for a while, you're ready to apply.
+You can simply register on our <url id="&url-newmaint-apply;"
+name="application page">.  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 the <url id="&url-newmaint-db;"
+name="applications status board">.

        <p>
 For more details, please consult <url id="&url-newmaint;" name="New
        <p>
 For more details, please consult <url id="&url-newmaint;" name="New

-Maintainer's Corner"> at the Debian web site.
-       <p>
-Once this information is received and processed, you should be
-contacted with information about your new Debian maintainer account.
-If you don't hear anything within a month, please send a followup
-message asking if your original application was received.  Do
-<em>not</em> re-send your original application, that will just confuse
-the New Maintainer Group. Please be patient, especially near release
-points; mistakes do occasionally happen, and people do sometimes run
-out of volunteer time.
+Maintainer's Corner"> at the Debian web site.  Make sure that you
+are familiar with the necessary steps of the New Maintainer process
+before actually applying.  If you are prepared well, you can save
+a lot of timer later on.

 
 
       <sect id="mentors">Debian Mentors
 
 
       <sect id="mentors">Debian Mentors


@@ -2060,7 +2050,7 @@ list.
 This chapter describes procedures that existing Debian developers should
 follow when it comes to dealing with wannabe developers.
 
 This chapter describes procedures that existing Debian developers should
 follow when it comes to dealing with wannabe developers.
 

-      <sect>Sponsoring packages
+      <sect id="sponsoring">Sponsoring packages

        <p>
 Sponsoring a package means uploading a package for a maintainer who is not
 able to do it on their own, a new maintainer applicant. Sponsoring a package
        <p>
 Sponsoring a package means uploading a package for a maintainer who is not
 able to do it on their own, a new maintainer applicant. Sponsoring a package