need an easy way to request private branch support

Bug #370170 reported by Martin Pool
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
William Grant

Bug Description

At the moment only some teams have permission to create private branches. The business policy is that it's available either to commercial subscribers or to bona fide open source projects using it for eg security fixes.

I believe both uses are active at the moment, but to do either of them you need to specially apply by eg mail to feedback@.

It would be good if there was a visible UI through which open source projects could request the second category. Perhaps this should be connected to a more general "yes this is a real open source project" review, like the licence review. There is a concept of "fair use" that open projects should generally work in the open aside from work that needs to be private.

Jonathan Lange (jml)
Changed in launchpad-code:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Robert Collins (lifeless) wrote :

This isn't in our current roadmap. I think it would be nice to get done, but we really need product direction to shape up our story around noncommercial private objects; the technical aspects are not the challenge here IMNSHO.

Changed in launchpad:
importance: High → Low
Curtis Hovey (sinzui)
tags: added: branches disclosure privacy
Curtis Hovey (sinzui)
tags: added: entitlement
William Grant (wgrant)
Changed in launchpad:
assignee: nobody → William Grant (wgrant)
Revision history for this message
Curtis Hovey (sinzui) wrote :

William, I believe your UI addition to +sharing addresses this. You can closed this bug when we enter the Sharing beta.

Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
Curtis Hovey (sinzui) wrote :

While setting policy is a day away, anyone can make a branch private, such as for a security fix. the option is hidden on the Change branch details page.

Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers