Comment 3 for bug 696956
Revision history for this message
| Francis J. Lacoste (flacoste) wrote Re: Allow users in project roles to access private branches | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have doubts about that requirement. Branches have a dual ownership project and owner. What you are suggesting here is that one owner (the project) preempts the other (the person owning the branch).
Wouldn't this precludes use cases like a team is working on an upstream project for an under-the-radar feature (exclusive launch then merged upstream, like we do in some OEM projects). The work should be in a private branch, but the upstream project owner shouldn't necessarily have access to it until the sponsor feels it's ready to merge back.
With this constraint in place, that use case would have to be serviced by creating a 'fork project' only to manage the maybe temporary secret fork.
If that requirement only applies to private projects, I think it could work. (Since by definition, nobody else can create branches on such a project).