[dpl-helpers] draft release team delegation

[Lucas Nussbaum]

On 12/12/13 at 16:14 +0000, Neil McGovern wrote:
> > > 2) Setting the NMU delay policy
> > 
> > I don't think that this should be part of the release team's delegated
> > powers. I feel that the NMU procedures are already open enough, as I
> > argued in https://lists.debian.org/debian-devel/2013/12/msg00011.html .
> > Could you follow-up in that thread, maybe?
> > 
> 
> It has, however, been so, see dev-ref 5.11.1 and #625449, particularly
> message 90. I know you don't agree with this, but if you wish to
> essentially remove the current practice, then I think that this needs
> much more explicit statement in the mail.

OTOH, in #625449, the release team did not _decide_ on a new NMU policy.
Instead, the team announced its intention to change the policy in
https://lists.debian.org/debian-devel-announce/2011/03/msg00016.html,
then filed a bug against dev-ref, then argued a bit in the bug, then the
topic was raised on -devel@, and as a result, the policy was changed.
That's a very reasonable way to make such changes, that does not require
any delegated power.

> Perhaps something like:
> Note - this does not include the practice that the release team may set
> rules for NMU delays. Instead, this will be handled by [dev-ref
> maintainers/policy/ftp-masters/someone else].
> 
> Personally though, I would oppose the removal of this de-facto state.

Why do you feel that it is so important for the release team to have
that power?

Other opinions on this?

I would also like to argue that, in terms of scope, this is quite far
from the other powers of the release team, as it would deal with general
package uploads to unstable (even if not said explicitely). I wouldn't
mind so much if this was about NMUs to t-p-u (but I know there are good
reasons not to use t-p-u too much).
 
Lucas