ubuntu-community

Bug #174375
Comment #16

Comment 16 for bug 174375

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-11-04: Re: [Bug 174375] Re: Distribution drivers permissions may need redesign

#16

On Thu, 2010-11-04 at 13:29 +0000, Colin Watson wrote:
> > This is great news. To be clear, are all 45 members permitted to
> create
> > a series?
>
> I would not want the entire current drivers team to have this
> permission, no, but we were talking about reducing it anyway, weren't
> we? Many folks are in that team in order to be able to manage bug
> nominations, notably canonical-qa with its 13 members.
>
> Ideally, the team with this permission would be ubuntu-release, but it
> would be acceptable for it to be that subset of the current
> ubuntu-drivers team who are responsible for feature planning (i.e.
> managers, tech leads, and the TB). Removing uds-organizers from
> ubuntu-drivers might be difficult, though, and there are a lot of
> people
> in that who aren't normally involved in the task of creating a new
> release.
>
> I notice that we currently have ubuntu-drivers in both the Maintainer
> and Driver slots. Could you clarify the precise difference between
> those? Perhaps ubuntu-release could occupy one of them.

Ubuntu has an odd story. Owners can change everything in a project,
drivers can change items related to planning. The driver of a series is
a release manager can has extra power to create, edit, and delete
milestones. Since We do not want dozens of people to have the power to
change the Ubuntu page, or edit every series and milestone in Ubuntu,
Ubuntu owners have very little power to make changes.

Other distro owners can change their distro page and manage series and
milestones without the assistance of an admin. The driver of another
distro is like the driver of a project--change work items.

I want a single set of rules for all projects and distros:
owner can see and change everything.
release managers set goals for a series (super drivers)
drivers are trusted to update project items to meet goal
bug supervisors are like drivers, but have extra bug permissions.

The release manager role can be the owner, but project often run
concurrent series and the owner often delegates to a smaller group to
meet each series' goals.

In the next few months owner and drivers will be permitted to see all
private bugs and branches for their distro/project. They will not need
to be subscribed to individual bugs and branches, they do not need to be
members of the bug supervisor team.

--
__Curtis C. Hovey_________
http://launchpad.net/

On Thu, 2010-11-04 at 13:29 +0000, Colin Watson wrote:
> > This is great news. To be clear, are all 45 members permitted to
> create
> > a series?
> 
> I would not want the entire current drivers team to have this
> permission, no, but we were talking about reducing it anyway, weren't
> we?  Many folks are in that team in order to be able to manage bug
> nominations, notably canonical-qa with its 13 members.
> 
> Ideally, the team with this permission would be ubuntu-release, but it
> would be acceptable for it to be that subset of the current
> ubuntu-drivers team who are responsible for feature planning (i.e.
> managers, tech leads, and the TB).  Removing uds-organizers from
> ubuntu-drivers might be difficult, though, and there are a lot of
> people
> in that who aren't normally involved in the task of creating a new
> release.
> 
> I notice that we currently have ubuntu-drivers in both the Maintainer
> and Driver slots.  Could you clarify the precise difference between
> those?  Perhaps ubuntu-release could occupy one of them.

Other distro owners can change their distro page and manage series and
milestones without the assistance of an admin. The driver of another
distro is like the driver of a project--change work items.

The release manager role can be the owner, but project often run
concurrent series and the owner often delegates to a smaller group to
meet each series' goals.

-- 
__Curtis C. Hovey_________
http://launchpad.net/