Launchpad itself

Making a private project

Asked by Franck Fitoussi

Hello,

I'm a little confused about how to set up a private project. We got the commercial subscription and would like to restrict the access to our project to the members of a team we made (and preferably make anything that could be added hidden by default -except for members of said team-).
The project is : https://launchpad.net/numerink and the team I would like to restrict the acces to is : https://launchpad.net/~numerink-team

Any help would be appreciated.

Thanks in advance.

Question information

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

Hi Frank,

In Launchpad you cannot have a completely private project. You can have the bug tracker set to make all bugs private at creation time and you can have private code hosting. The overview page of your project and Blueprints, Translations, and Answers will be publicly visible.

For me to turn on private bugs you must do the following:
1) Setup your project to do bug tracking in Launchpad,
2) Set the 'Bug supervisor' team to the team you want to have access to the private bugs. In your case that would be ~numerink-team.

Once those steps are taken I can then finish setting up the bug tracker for you.

Likewise, for private code hosting, you need to first configure your project to do code hosting in Launchpad. I can then set it up so that hosted branches are only visible to the members of the ~numerink-team.

Please let me know when you've done those two things and I'll see that those privacy options are enabled for you.

Revision history for this message
Franck Fitoussi (franck-fitoussi) said : 		#2

Thank you very much !

We went ahead and did what you asked. Let us know if there is anything more we can/should do.
Thanks in advance for setting it up for us.

Take care.

Revision history for this message
Brad Crittenden (bac) said : 		#3

Frank I have set up private bugs and private code. I note you already have a branch defined and it is public. As the project maintainer you may be able to change it to private. If not, you'll need to delete it and create a new branch which will follow the new privacy policy. Sorry for that bit of extra work. It is advisable to push a branch with no proprietary code the first time just to ensure the visibility is set as you expect.

Let me know if I can help further.

Revision history for this message
Franck Fitoussi (franck-fitoussi) said : 		#4

Thank you for everything !

Could I have a couple clarifications regarding private projects ?

First off, I noticed that the ssh keys we set up in launchpad are public. Does this not pose a security threat? (I realize this isn't a launchpad oriented question so a simple yes/no answer is enough)

Are the licenses per private project or per account?

Thanks again.

Revision history for this message
Brad Crittenden (bac) said : 		#5

Hi Frank,

The SSH keys you see are only the public part of the pair so there is really no harm in having them visible.

The commercial licenses are per project. It is a little confusing because when you buy a *voucher* it is linked to your account but then you redeem the voucher for a license on a project.

Thanks,
Brad

Can you help with this problem?

Provide an answer of your own, or ask Franck Fitoussi for more information if necessary.

To post a message you must log in.