| 2011-11-21 16:48:56 |
Curtis Hovey |
description |
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. |
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. |
|
