From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Tue, 7 May 2002 03:37:26 +0000 (+0000)
Subject: trim the bad submit-bugs chapter; s/GPG/GnuPG/
X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=13d151e1b1915b72d6bf35be0d1ef0d8ccfae6b3;p=developers-reference.git

trim the bad submit-bugs chapter; s/GPG/GnuPG/


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

diff --git a/debian/changelog b/debian/changelog
index ef4857a..87a82ce 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -39,6 +39,7 @@ developers-reference (3.0) unstable; urgency=low
     - update copyright date
     - some simplifications on the TeX suffix rule
     - spell check
+    - s/GPG/GnuPG/
 
   * Raphael Hertzog:
     - changed -e by -m in the dpkg-buildpackage command line example.
diff --git a/developers-reference.sgml b/developers-reference.sgml
index 6a8ecb2..223db81 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.95 $">
+  <!entity cvs-rev "$Revision: 1.96 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -171,14 +171,14 @@ 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
+and technical documentation.  Furthermore, you need a GnuPG key which
+has been signed by an existing Debian maintainer.  If your GnuPG 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
+name="GnuPG 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
+can send in a photo ID signed with your GnuPG key.  Having your GnuPG
 key signed is the preferred way, however.  See the
 <url id="&url-newmaint-id;" name="identification page"> for more
 information about these two options.)
@@ -228,7 +228,7 @@ registered developer, an existing developer with whom you
 have worked over the past months has to express his belief that you
 can contribute to Debian successfully.
 	<p>
-When you have found an advocate, have your GPG key signed and have
+When you have found an advocate, have your GnuPG 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
@@ -1255,7 +1255,7 @@ The upload must be a complete Debian upload, as you would put it into
 <tt>ftp-master</tt>'s <tt>Incoming</tt>, i.e., a <tt>.changes</tt> files
 along with the other files mentioned in the <tt>.changes</tt>. The
 queue daemon also checks that the <tt>.changes</tt> is correctly
-PGP-signed by a Debian developer, so that no bogus files can find
+signed with GnuPG or OpenPGP by a Debian developer, so that no bogus files can find
 their way to <tt>ftp-master</tt> via this queue. Please also make sure that
 the <tt>Maintainer</tt> field in the <tt>.changes</tt> contains
 <em>your</em> e-mail address. The address found there is used for all
@@ -1295,7 +1295,7 @@ When a package is uploaded, an announcement should be posted to one of
 the ``debian-changes'' lists. This is now done automatically by the archive
 maintenance software when it runs (usually once a day). You just need to use
 a recent <package>dpkg-dev</package> (&gt;= 1.4.1.2). The mail generated by
-the archive maintenance software will contain the PGP/GPG signed 
+the archive maintenance software will contain the OpenPGP/GnuPG signed 
 <tt>.changes</tt> files that you uploaded with your package.
 Previously, <prgn>dupload</prgn> used to send those announcements, so
 please make sure that you configured your <prgn>dupload</prgn> not to
@@ -1984,6 +1984,12 @@ right away.
 
 
     <sect id="bug-handling">Handling package bugs
+	<p>
+Often as a package maintainer, you find bugs in other packages or else
+have bugs reported to your packages which need to be reassigned.  The
+<url id="&url-bts-control;" name="BTS instructions"> can tell you how
+to do this.  Some information on filing bugs can be found in <ref
+id="submit-bug">.
 
       <sect1>Monitoring bugs
 	<p>
@@ -2007,35 +2013,16 @@ outlining all the open bugs against your packages:
 Replace <var>address</var> with you official Debian
 maintainer address.
 
-      <sect id="submit-bug">Submitting bugs
-	<p>
-Often as a package maintainer, you find bugs in other packages or else
-have bugs reported to your packages which need to be reassigned.  The
-<url id="&url-bts-control;" name="BTS instructions"> can tell you how
-to do this.
-	<p>
-We encourage you to file bugs when there are problems.  Try to submit
-the bug from a normal user account at which you are likely to receive
-mail.  Do not submit bugs as root.
-	<p>
-Make sure the bug is not already filed against a package.  Try to do a
-good job reporting a bug and redirecting it to the proper location.
-For extra credit, you can go through other packages, merging bugs
-which are reported more than once, or setting bug severities to
-`fixed' when they have already been fixed.  Note that when you are
-neither the bug submitter nor the package maintainer, you should
-not actually close the bug (unless you secure permission from the
-maintainer).
-
       <sect1 id="bug-answering">Responding to bugs
 	<p>
 Make sure that any discussions you have about bugs are sent both to
 the original submitter of the bug, and the bug itself (e.g.,
 <email>123@bugs.debian.org</email>).
 	<p>
-You should <em>never</em> close bugs via the bug server `close'
+You should <em>never</em> close bugs via the bug server <tt>close</tt>
 command sent to &email-bts-control;.  If you do so, the original
-submitter will not receive any feedback on why the bug was closed.
+submitter will not receive any information about why the bug was
+closed.
 
       <sect1 id="bug-housekeeping">Bug housekeeping
 	<p>
@@ -2083,8 +2070,9 @@ used:
   /closes:\s*(?:bug)?\#\s*\d+(?:,\s*(?:bug)?\#\s*\d+)*/ig
 </example>
 
-The author prefers the <tt>(closes: Bug#<var>XXX</var>)</tt> syntax,
-since it stands out from the rest of the changelog entries.
+The author prefers the <tt>closes: #<var>XXX</var>)</tt> syntax, as
+one of the most concise and easiest to integrate with the text of the
+<file>changelog</file>.
 	<p>
 If you want to close bugs the old fashioned, manual way, it is usually
 sufficient to mail the <tt>.changes</tt> file to
@@ -2118,11 +2106,13 @@ the most critical thing to spend their time on.
     <sect id="submit-bug">
         <heading>Bug Reporting</heading>
         <p>
-We encourage you to file bugs as you find them in Debian packages.
+We encourage you to file bugs as you find them in Debian packages.  In
+fact, Debian developers are often the first line testers.  Finding and
+reporting bugs in other developer's packages improves the quality of
+Debian.
 	<p>
-Try to submit
-the bug from a normal user account at which you are likely to receive
-mail.  Do not submit bugs as root.
+Try to submit the bug from a normal user account at which you are
+likely to receive mail.  Do not submit bugs as root.
 	<p>
 Make sure the bug is not already filed against a package.  Try to do a
 good job reporting a bug and redirecting it to the proper location.