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

Re: Best scheme for teams and Maintainer/Uploaders fields ?



Re: Pierre Habouzit 2007-01-08 <20070108080827.GE14579@hades.madism.org>
> > The perl team, on the other hand, uses the different scheme:
> >   Maintainer: "main responsible person for the package"
> >   Uploaders: the team mailing list, + members who actually care for the
> >   package (who have touched it in the past, for example).

It doesn't matter much if the main maintainer is in the Maintainer: or
Uploaders: field as long as the package list is not overly cluttered.

> > This leads to much shorter and interesting DDPO pages, without any
> > drawback I can see (the "all packages from the team" DDPO page is still
> > available using the the team mailing list address).

Note that you can subscribe additional packages to any maintainer
view. The GIS team does that:

http://qa.debian.org/developer.php?login=pkg-grass-devel@lists.alioth.debian.org

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/

Attachment: signature.asc
Description: Digital signature


Reply to: