X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=pkgs.dbk;h=baec071708b82f55b5f4c7439f430c6c0593d5ca;hp=f40e7f3d873b5a7b04cb75db6106ebac6590711c;hb=39be11fbe9478b9a5d6fb527f78d54a053b6e7bb;hpb=c7d61e4985455a42c953a58a661b26f1f9c679af
diff --git a/pkgs.dbk b/pkgs.dbk
index f40e7f3..baec071 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -2194,6 +2194,21 @@ the new version (see ).
+
+NMUs vs team uploads
+
+
+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 ) 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: * Team upload.
.
+
+
+
+
@@ -2268,11 +2283,17 @@ moderation for non-subscribers).
+
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
) 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 ). Conversely, it it a bad idea to keep a
+package with only the mailing list address as a Maintainer and no
+Uploaders.