[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#573110: developers-reference: Team uploads.

Package: developers-reference
Version: 3.4.3
Severity: wishlist
Tags: patch

Dear all,

following discussions on debian-devel, still ongoing, I propose the
attached patch for team uploads (http://wiki.debian.org/TeamUpload).

The formalisation of team uploads would help team members to show the priority
they have in the packages maintained by their team, by being Uploader for some
but not all.

Here is the summary of the patch:

 - NMUs whose changelog entry starts by “ * Team upload.” are normal uploads.
 - Do a team upload only if it is a practice agreed with in your team.
 - Do not let a package with no human uploader.

Have a nice day,

Charles Plessy
Tsurumi, Kanagawa, Japan
Index: pkgs.dbk
--- pkgs.dbk	(révision 7096)
+++ pkgs.dbk	(copie de travail)
@@ -2194,8 +2194,22 @@
+<section id="nmu-team-upload">
+<title>NMUs vs team uploads</title>
+Sometimes you are informed about a package's state because you are member of a
+packaging team who uses a mailing list as Maintainer or Uploader, (<xref
+linkend="collaborative-maint"/>). 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 can start your changelog entry with the following
+line: <code> * Team upload.</code>. 
 <section id="collaborative-maint">
 <title>Collaborative maintenance</title>
@@ -2268,11 +2282,15 @@
+Team members can perform regular uploads without being listed as Uploaders
+(<xref linkend="nmu-team-upload"/>).
 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
 <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. Conversely, it it a bad idea to keep
+a package with only the mailing list address as a Maintainer and no UPloaders.

Reply to: