decouple branch naming from branch access control
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
(Bug to track an open issue, needs discussion.)
At the moment the standard naming of a branch in Launchpad is
/~owner/
and these components must be, respectively, a Launchpad Person (including groups), a project, and an arbitrary unique name.
Only the owner can write to the branch.
The owner can be changes, but this implicitly changes the name of the branch. Objects (bugs, specs etc) attached to the branch inside Launchpad will remain attached, but things outside Launchpad will lose their reference.
This is probably reasonable if the branch really is intended to be renamed, or moved from one project to another.
However, if the user just wants to change who can write to the branch, for example allowing one group or not, this is unnecessarily disruptive. People using hosted branches for packaging would commonly like to change access rules on them.
| Matt Zimmerman (mdz) wrote | #1 |
| Martin Pool (mbp) wrote | #2 |
| Aaron Bentley (abentley) wrote | #3 |
| Changed in launchpad-bazaar: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: acl |
| Changed in launchpad: | |
| importance: | Medium → Low |
| tags: |
added: branches removed: acl |
I agree, this is counter-intuitive in its side effects. With other web content, the notion of access control is managed separately from the notion of namespace, and I think that's healthy.