Can I haz private project?

Asked by Guilherme Salgado on 2011-09-19

We would like to have at least private branches for https://launchpad.net/linaro-infrastructure-shared-credentials but if it can be made into a private project that'd be even better. :)

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Last query:
2011-09-20
Last reply:
2011-09-20
David Ames (thedac) said : #1

We have three things the specific branch, the team and the project:

I have set the branch to private.

The team linaro-infrastructure currently has its default branch visibility set to private. It can have its default branch visibility set to Forbidden as a default except for the linaro-infrastructure team. This would affect the default for all branches the team produces and can be overridden on a branch by branch basis.

The project has only one option regarding the privacy of bugs. A project itself cannot be private.

Let me know what you want to do.

--
David Ames

Guilherme Salgado (salgado) said : #2

Oh, I thought it was possible to have all branches of a given project
private by default, but maybe there isn't?

On Mon, 2011-09-19 at 23:55 +0000, David Ames wrote:
[...]
> The team linaro-infrastructure currently has its default branch
> visibility set to private.

But shouldn't that have caused the branch I created[1] to be private?

> It can have its default branch visibility set
> to Forbidden as a default except for the linaro-infrastructure team.

except for the team itself? I'm not sure I understand that.

> This would affect the default for all branches the team produces and can
> be overridden on a branch by branch basis.

What would the default be in this case?

Oh, boy, so many questions... I clearly have no clue about any of this
stuff.

[1] https://code.launchpad.net/~linaro-infrastructure/linaro-infrastructure-shared-credentials/trunk

Guilherme Salgado (salgado) said : #3

On Tue, 2011-09-20 at 00:55 +0000, Guilherme Salgado wrote:
[...]
> > It can have its default branch visibility set
> > to Forbidden as a default except for the linaro-infrastructure team.
>
> except for the team itself? I'm not sure I understand that.

If this means we can only push branches for this project under
~linaro-infrastructure (which are then by default private), then this
works for us.

David Ames (thedac) said : #4

> > It can have its default branch visibility set
> > to Forbidden as a default except for the linaro-infrastructure team.
>
> except for the team itself? I'm not sure I understand that.

If this means we can only push branches for this project under
~linaro-infrastructure (which are then by default private), then this
works for us.

That is correct. The default branch visibility is set on the team or user not the project.

--
David Ames

Can you help with this problem?

Provide an answer of your own, or ask Guilherme Salgado for more information if necessary.

To post a message you must log in.