fixed orphaning/adopting instructions with regard to the new WNPP

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index e845dd939e0c182c4c50aa494e91e7db507af114..6882191f4031910547f57b81b0c6675a2c0b8bba 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 -->
-  <!entity cvs-rev "$Revision: 1.39 $">
+  <!entity cvs-rev "$Revision: 1.40 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -837,12 +837,8 @@ If you want to create a new package for the Debian distribution, you
 should first check the <url id="&url-wnpp;" name="Work-Needing and
 Prospective Packages (WNPP)"> list.  Checking the WNPP ensures that no
 one is already working on packaging that software, and that effort is
-not duplicated. Assuming no one else is already working on your
-prospective package, you must then send a short email to
-&email-debian-devel; describing your plan to create a new package.
-You should set the subject of the email to ``intent to package
-<var>foo</var>'', substituting the name of the new package for
-<var>foo</var>.
+not duplicated. Read the <url id="&url-wnpp;" name="WNPP web pages"> for
+more information.
        <p>
 There are a number of reasons why we ask maintainers to follow these
 steps:
@@ -1716,27 +1712,20 @@ that package, and the package has moved into the archive, file a bug
 against <tt>ftp.debian.org</tt> asking to remove the package with the
 obsolete name.
 
-
-
       <sect id="orphaning">Orphaning a package
        <p>
-If you can no longer maintain a package, then you should set the
-package maintainer to <tt>Debian QA Group
-&lt;debian-qa@lists.debian.org&gt;</tt> and email &email-wnpp;
-indicating that the package is now orphaned.  If the package is
-especially crucial to Debian, you should instead email
-&email-debian-devel; asking for a new maintainer.
-
+If you can no longer maintain a package, you need to inform the others
+about that, and see that the package is marked as orphaned. Read
+instructions on the <url id="&url-wnpp;" name="WNPP web pages"> for more
+information.
 
       <sect id="adopting">Adopting a package
        <p>
-Periodically, a listing of packages in need of new maintainers will be
-sent to &email-debian-devel list. This list is also available at in
-the Work-Needing and Prospective Packages document (WNPP), <url
-id="&url-wnpp;">.  If you wish to take over maintenance of any of the
-packages listed in the WNPP, or if you can no longer maintain a
-packages you have, or you simply want to know if any one is working on
-a new package, send a message to &email-wnpp;.
+A list of packages in need of a new maintainer is available at in the
+<url name="Work-Needing and Prospective Packages list (WNPP)"
+id="&url-wnpp;">. If you wish to take over maintenance of any of the
+packages listed in the WNPP, please take a look at the aforementioned
+page for more information.
        <p>
 It is not OK to simply take over a package that you feel is neglected
 -- that would be package hijacking.  You can, of course, contact the