On Wed, 2006-05-03 at 09:28 -0700, Matt Zimmerman wrote: > On Wed, May 03, 2006 at 11:58:40AM -0400, Brad Bollenbach wrote: > > I see another possibility: > > > > * Allow a configuration option to define a release management team. Then > > two options (more thought needed on the wording, just putting forth the > > idea): > > > > (*) Allow only members of the release management team to target bugs > > ( ) Allow any logged-in user to target a bug, subject to approval from > > the release management team > > > > Without making this configurable, I think it will be extremely difficult > > for Malone to scale from small, release early, release often, > > anyone-can-have-a-commit-bit projects all the way to large projects, > > which rely on heavyweight processes and workflows to coordinate hundreds > > of contributors or more. > > That seems excessively complex to me; it's already getting rather unclear > who can do what in Launchpad based on the roles attached to the distribution > (which are usually unclear in the contexts where they take effect). > > Driver? Registrant? Members?
If there were a configurable "release management" team, I think this question would have been easier to answer. As I noted in another email, I don't think any non-implementer can be expected to equate "Drivers" to "Release Managers". The additional radio buttons may indeed be unnecessary complexity, since the Release Managers would, of course, bypass the nomination/approval process anyway. Brad -- launchpad-users mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/launchpad-users
