Comment 4 for bug 696956
Revision history for this message
| Curtis Hovey (sinzui) wrote Re: Allow users in project roles to access private branches | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The underlying requirement for this bug is a statement from Canonical managers that Canonical staff should have access to Canonical's code. The subscription mechanism is a burden, see bug #474048. The goal is to minimise the number of steps and maybe their frequency so that an organisation can confidently share its code with its members.
This could apply to just private projects, but I believe Canonical would be dissatisfied. ISD and U1 will always have some public projects with private branches. Conversely, HWE will commonly be working with public projects that they do not own, but need to contribute to.
If we supported nested projects, we could build a hierarchy of projects under canonical's porject and set the policy exactly once for the Canonical team in Canonical's projects.