On 28/01/08 at 14:00 +0100, Mike Hommey wrote: > On Mon, Jan 28, 2008 at 07:55:25AM +0100, Lucas Nussbaum <[EMAIL PROTECTED]> > wrote: > > On 27/01/08 at 23:00 +0100, Bill Allombert wrote: > > > On Fri, Jan 25, 2008 at 07:31:02PM +0100, Raphael Hertzog wrote: > > > > On Fri, 25 Jan 2008, Bill Allombert wrote: > > > > > On Fri, Jan 25, 2008 at 09:31:32AM +0100, Lucas Nussbaum wrote: > > > > > > In the ruby-extras team, we use: > > > > > > Maintainer: the team member "mainly" responsible for the package > > > > > > Uploaders: the team mailing list, and the other team members who > > > > > > keep a > > > > > > look on the package. > > > > > > > > > > > > And I think that makes perfect sense ;) > > > > > > > > > > It does ? How a mailing list can upload package ? It seems you are > > > > > using > > > > > a functional field for documentation purpose. > > > > > > > > I'm sorry, Uploaders has no "function" except when combined with > > > > DM-Upload-Allowed. One can perfectly upload a package without being in > > > > the > > > > Uploaders in the default case. > > > > > > Not true, Uploaders is used by the archive software to determine whether > > > an > > > upload is an NMU or not, and whether bugs Closes:ed in the changelog > > > should > > > be marked as closed or marked as 'fixed in NMU' in the BTS. That is > > > actually its raison d'être. > > > > ... which only applies to packages uploaded with a Changed-By pointing > > at the team. Most teams don't do that. > > > > The main use of mailing-list-in-Uploaders is to be able to list all > > packages (co-)maintained by the team, on DDPO, in dd-list, etc. > > Hum... like in [1], where the ML is NOT in Uploaders for webkit... See [2]. > You'll need to find another reason for ML in Uploaders ;) > > Mike > 1. http://qa.debian.org/[EMAIL PROTECTED] ? > 2. http://packages.qa.debian.org/w/webkit.html
So your only solution for not adding the list in Uploaders is to put it in Maintainer:? ;) In the ruby-extras team, we felt that using the list as Maintainer made people feel less responsible about their packages (the "it's the team's package, not my package, so I don't have to fix that bug" problem). That's why we chose the situation described in the beginning of that mail. So your solution doesn't solve everything. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
