X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developers-reference.sgml;h=a70f475adff0942cd7df80b0bfd0e3a8263292d9;hb=b9ad716105a5129cd710814f0af93ea3767c7fde;hp=af1aca2b1911645413d314b5c6f7c33ae64bd6ad;hpb=be9ea81016073be70c312fd28af026fd2fa35224;p=developers-reference.git

diff --git a/developers-reference.sgml b/developers-reference.sgml
index af1aca2..a70f475 100644
--- 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.58 $">
+  <!entity cvs-rev "$Revision: 1.59 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -874,18 +874,25 @@ not duplicated. Read the <url id="&url-wnpp;" name="WNPP web pages"> for
 more information.
         <p>
 Assuming no one else is already working on your prospective package,
-you must then submit a short bug (<ref id="submit-bug">) against the
-pseudo package <tt>wnpp</tt> and send a copy to &email-debian-devel;
+you must then submit a bug report (<ref id="submit-bug">) against the
+pseudo package <tt>wnpp</tt> 
 describing your plan to create a new package, including, but not
 limiting yourself to, a description of the package, the license of the
 prospective package and the current URL where it can be downloaded
-from.  You should set the subject of the bug to ``ITP: <var>foo</var>
+from.
+	<p>
+You should set the subject of the bug to ``ITP: <var>foo</var>
 -- <var>short description</var>'', substituting the name of the new
-package for <var>foo</var>.  The severity of the bug report must be
-set to <em>wishlist</em>.  Please include a <tt>Closes:
-bug#<var>nnnnn</var></tt> entry on the changelog of the new package in
-order for the bug report to be automatically closed once the new
-package is installed on the archive (<ref id="upload-bugfix">).
+package for <var>foo</var>.  The severity of the bug report must be set
+to <em>wishlist</em>. If you feel it's necessary, send a copy to
+&email-debian-devel; by putting the address in the X-Debbugs-CC: header
+of the message (no, don't use CC:, because that way the message's subject
+won't indicate the bug number).
+	<p>
+Please include a <tt>Closes: bug#<var>nnnnn</var></tt> entry on the
+changelog of the new package in order for the bug report to be
+automatically closed once the new package is installed on the archive
+(<ref id="upload-bugfix">).
 	<p>
 There are a number of reasons why we ask maintainers to announce their
 intentions:
@@ -1787,11 +1794,16 @@ you should set the package maintainer to <tt>Debian QA Group
 against the pseudo package <package>wnpp</package>.  The bug report should be
 titled <tt>O: <var>package</var> -- <var>short description</var></tt>
 indicating that the package is now orphaned.  The severity of the bug
-should be set to <em>normal</em>.  If the package is especially
-crucial to Debian, you should instead submit a bug against
-<tt>wnpp</tt> and title it <tt>RFA: <var>package</var> -- <var>short
-description</var></tt> and set its severity to <em>important</em>. You
-should also email &email-debian-devel; asking for a new maintainer.
+should be set to <em>normal</em>. If you feel it's necessary, send a copy
+to &email-debian-devel; by putting the address in the X-Debbugs-CC: header
+of the message (no, don't use CC:, because that way the message's subject
+won't indicate the bug number).
+	<p>
+If the package is especially crucial to Debian, you should instead submit
+a bug against <tt>wnpp</tt> and title it <tt>RFA: <var>package</var> --
+<var>short description</var></tt> and set its severity to
+<em>important</em>. Definitely copy the message to debian-devel in this
+case, as described above.
 	<p>
 Read instructions on the <url id="&url-wnpp;" name="WNPP web pages">
 for more information.