The ubuntu-drivers team holds a confusing mix of privileges
Bug #585807 reported by
Matt Zimmerman
This bug report is a duplicate of:
Bug #174375: Distribution drivers permissions may need redesign.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-community |
Confirmed
|
Medium
|
Ubuntu Technical Board |
Bug Description
The ubuntu-drivers team, by virtue of being the "driver" of the Ubuntu distro in Launchpad, can:
Approve(?) bug nominations
Approve blueprints
Edit all aspects of a specification
Accept blueprints for sprints
Control the agenda of a sprint
Set package bug guidelines
Set official bug tags
Remove package bug subscriptions on behalf of others
These tasks are performed by different teams within the Ubuntu project, which are currently grouped together into ubuntu-drivers out of necessity. This means that people who need any one of these privileges must be granted all of them.
visibility: | private → public |
Changed in ubuntu-community: | |
assignee: | nobody → Ubuntu Technical Board (techboard) |
Changed in ubuntu-community: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
Is this a limitation in how blueprints presents permissions? I.e. does it need to expose them in a finer grained fashion?