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

Re: Developer Status

Lucas Nussbaum wrote:

> On 22/10/08 at 23:33 +0200, Joerg Jaspert wrote:
>> and keyring managers
>> would like to remain the authoritative source for "who is in Debian".
> Indeed, that's a problem. What about changing the DM process so that
> keyring managers are responsible for this keyring as well?

That's what he said:

> Changes to the DM Keyring
>  -------------------------
>  Keyring management will be moved to the control of keyring-maint.  The
>  NM committee will decide who will be added or removed, similiar to the
>  way keyring-maint and DAM currently work together.

>> They are allowed to upload their own (source) package. The allowed list
>> of (source) packages to upload can be edited by any member of the NM
>> committee[NMC], who will do a package check before they add new packages
>> to the DM's list.
> There's a problem with DM currently: it doesn't work well with massively
> comaintained packages. For example, if you have:
> - a team with DMs DMa and DMb
> - DMa became DM to maintain Pa
> - DMb became DM to maintain Pb
> - DMa wants to help with the maintainance of Pb, but should not be given
>   upload rights for Pb
> - DMb wants to help with the maintainance of Pa, but should not be given
>   upload rights for Pa

That's not a problem which should be solved by a technical "workaround". If you
are not confident enough that either DMa won't upload Pb or DMb won't upload Pa
then why are you giving her/him rights to change anything in either Pa or Pb?

It's like if you wanted to limit what packages DDs can upload and which not.

> Then you have a problem.
> If you are maintaining a centralized list for DM upload rights, please
> implement it as a list of (DM, Package), not just as a list of
> (Package). Or even better, a list of (DM, Package, DD who endorsed this
> DM for this Package).

Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net

Reply to: