Mention rationale for including the description in ITPs. Closes: #494332

diff --git a/debian/changelog b/debian/changelog
index 45b1a47d93111006cc8edd13317676420b3e4849..b59cd242a4d3d3b1fc97fd69af86a3a17b104b57 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,8 @@ developers-reference (3.4.14) UNRELEASED; urgency=medium
   * Drop section on debsums as this functionality is now integrated in
     dpkg. Closes: #750990
   * Mention other types of checksums besides MD5. Closes: #750994
+  * Mention rationale for including the description in ITPs. Closes:
+    #494332
 
  -- Paul Wise <pabs@debian.org>  Wed, 20 Aug 2014 18:43:04 -0700
 

diff --git a/pkgs.dbk b/pkgs.dbk
index ba53ef0daf47d5f0a1b7c30defd6335072f2179f..5a34b950251cfa603fddece657ba553e4f4e8561 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -23,8 +23,9 @@ pages</ulink> for more information.
 Assuming no one else is already working on your prospective package, you must
 then submit a bug report (<xref linkend="submit-bug"/>) against the
 pseudo-package <systemitem role="package">wnpp</systemitem> 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
+plan to create a new package, including, but not limiting yourself to, the
+description of the package (so that others can review it),
+the license of the prospective package, and the
 current URL where it can be downloaded from.
 </para>
 <para>