Document the notion of "team upload"

[developers-reference.git] / pkgs.dbk

diff --git a/pkgs.dbk b/pkgs.dbk
index 40ace63772f27819c5a533f4a79e5800c5b3caf3..baec071708b82f55b5f4c7439f430c6c0593d5ca 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -37,15 +37,15 @@ Please send a copy to &email-debian-devel; by using the X-Debbugs-CC
 header (don't use CC:, because that way the message's subject won't
 indicate the bug number). If you are packaging so many new packages (>10)
 that notifying the mailing list in seperate messages is too disruptive,
-do send a summary after filing the bugs to the debian-devel list instead.
+send a summary after filing the bugs to the debian-devel list instead.
 This will inform the other developers about upcoming packages and will
 allow a review of your description and package name.
 </para>
 <para>
-Please include a <literal>Closes:
-bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the
-new package in order for the bug report to be automatically closed once the new
-package is installed in the archive (see <xref linkend="upload-bugfix"/> ).
+Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></literal>
+entry in the changelog of the new package in order for the bug report to
+be automatically closed once the new package is installed in the archive
+(see <xref linkend="upload-bugfix"/>).
 </para>
 <para>
 If you think your package needs some explanations for the administrators of the
@@ -2194,6 +2194,21 @@ the new version (see <xref linkend="adopting"/>).
 
 </section>
 
+<section id="nmu-team-upload">
+<title>NMUs vs team uploads</title>
+
+<para>
+Sometimes you are fixing and/or updating a package because you are member of a
+packaging team (which uses a mailing list as Maintainer or Uploader, see <xref
+linkend="collaborative-maint"/>) but you don't want to add yourself to Uploaders
+because you do not plan to contribute regularly to this specific package. If it
+conforms with your team's policy, you can perform a normal upload without
+being listed directly as Maintainer or Uploader. In that case, you should
+start your changelog entry with the following line: <code> * Team upload.</code>.
+</para>
+
+</section>
+
 </section>
 
 <section id="collaborative-maint">
@@ -2268,11 +2283,17 @@ moderation for non-subscribers).
 </para>
 </listitem>
 </orderedlist>
+
 <para>
 In any case, it is a bad idea to automatically put all team members in the
-Uploaders field.  It clutters the Developer's Package Overview listing (see
+Uploaders field. It clutters the Developer's Package Overview listing (see
 <xref linkend="ddpo"/> ) with packages one doesn't really care for, and creates
-a false sense of good maintenance.
+a false sense of good maintenance. For the same reason, team members do
+not need to add themselves to the Uploaders field just because they are
+uploading the package once, they can do a “Team upload” (see <xref
+linkend="nmu-team-upload"/>). Conversely, it it a bad idea to keep a
+package with only the mailing list address as a Maintainer and no
+Uploaders.
 </para>
 </section>