branch multi-tenancy causes confusion about ownership
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
William Grant |
Bug Description
Branch multi-tenancy undermines the primary communities ability to manage it's data. Project maintainers want to set a policy of who has access to project's private data, but it is not necessarily true that the primary contributors (the maintainers) own the project data.
The project maintainers can, and do, make their branches private, which makes all stacked branches transitively private. Thus while a policy might permit another community to create private branches, it is not possible because they do not have access to the base branch. Branch multi-tenancy assumes that all branches are public, that users have access to base branches, which has not been the case since branch stacking was introduced. It is clear that Lp does recognise that the project maintainer does have the right to control their branch data, but it implies that this is not true.
summary: |
- Allow users in project roles to access private branches + the feature where different groups can have mutually invisible private + branches on a project leaves single-organisation projects with isolated + assets |
description: | updated |
summary: |
- the feature where different groups can have mutually invisible private - branches on a project leaves single-organisation projects with isolated - assets + branch multi-tenancy causes confusion about ownership |
tags: | added: sharing |
Changed in launchpad: | |
assignee: | nobody → William Grant (wgrant) |
Changed in launchpad: | |
status: | Triaged → In Progress |
Changed in launchpad: | |
status: | In Progress → Fix Released |
They don't need a subscription today, do they?
On 4/01/2011 9:40 AM, "Curtis Hovey" <email address hidden> wrote:
Public bug reported:
project maintainers, drivers, bug supervisors, and security contacts
should always have access to private branches. They should not need a
subscription to access their own project's private artefacts.
** Affects: launchpad
Importance: High
Status: Triaged
** Tags: disclosure
-- /bugs.launchpad .net/bugs/ 696956
You received this bug notification because you are subscribed to
Launchpad Suite.
https:/
Title:
Allow users in project roles to access private branches