Launchpad itself

private branches for fiecom

Asked by Bradley Friedman

Hello.

I have purchased a voucher for my project, fiecom and associated it. From looking around, it looks like the correct way to get my privacy settings set up is to ask here. If this is not correct, please do point me in the right direction.

Ideally am looking to get a three tiered privacy system set up for my code.

Three teams:

fiecom-committers
fiecom-source-code
fiecom-binaries

where:

fiecom-committers has full access to my branches and the ability to download releases.
fiecom-source-code has access to pull from but not push to my branches, and has the ability to download releases.
fiecom-binaries has no access to my branches but has the ability to download releases.

Is this granularity possible? What is the best way to manage this kind of access control?

I will likely be looking to set up similar levels of control for blueprints, bugs and answers as well. Is this also the correct place to make those requests?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Brad Crittenden (bac) said : 		#1

Hi Bradley,

We can partially do what you ask. There is no means to limit binary downloads, if by that you mean downloadable files associated with each release. If you are instead referring to PPAs then it is doable.

fiecom-committers and fiecom-source-code can be given access to your branches. If those branches are created in the fiecom-committers namespace then members of that team will be the only ones who can push to those branches.

fiecom-binaries could be subscribed to a private PPA if that is what you intend as mentioned above.

If you decide to follow such a plan I'd make three nested teams with source-code being a member of binaries, and committers being a member of source-code.

binaries > source-code > committers (where a > b indicates b is a member of a)

The access for other parts of launchpad is different.

You can get private bugs, but the team you select as the Bug Supervisor is the only one that can see the bugs initially. In your case that may be source-code or committers. Teams and people can be subscribed later to individual bugs and gain access to them.

We do not offer private blueprints. Others have managed that by putting all sensitive data in an externally controlled wiki and taking care not to include proprietary data in the blueprint itself.

Answers have no privacy controls at all.

You may want to follow up offline with Matthew Revell. He can be found on IRC as mrevell in the #launchpad channel on Freenode.

Revision history for this message
Curtis Hovey (sinzui) said : 		#2

I think this setup now after we talked on IRC.

Can you help with this problem?

Provide an answer of your own, or ask Bradley Friedman for more information if necessary.

To post a message you must log in.