Merge lp:~jml/launchpad/db-distro-level-ppa-privacy into lp:launchpad/db-devel
| Status: | Rejected |
|---|---|
| Rejected by: | Jonathan Lange on 2012-06-08 |
| Proposed branch: | lp:~jml/launchpad/db-distro-level-ppa-privacy |
| Merge into: | lp:launchpad/db-devel |
| Diff against target: |
28 lines (+12/-1) 2 files modified
database/schema/comments.sql (+1/-1) database/schema/patch-2209-22-1.sql (+11/-0) |
| To merge this branch: | bzr merge lp:~jml/launchpad/db-distro-level-ppa-privacy |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Curtis Hovey | entitlement | 2012-06-08 | Pending |
| Robert Collins | db | 2012-06-08 | Pending |
| Stuart Bishop | db | 2012-06-08 | Pending |
| Launchpad code reviewers | 2012-06-08 | Pending | |
|
Review via email:
|
|||
Commit Message
Add private_
Description of the Change
Adds a column to Distribution to control who can create private archives (i.e. P3As, private PPAs) for that distribution (currently Ubuntu only).
The plan is to follow this up with patches that:
* allow certain folk to view and update this value via the API
* update tests to say "I need to permissions to create private PPAs" rather than "I must be a commercial admin"
* change PPA creation to consult this value rather than the commercial_admin celebrity
* (possibly) make this value control whether launchpad.
No restrictions on when this lands, afaik.
| Jonathan Lange (jml) wrote : | # |
| Jonathan Lange (jml) wrote : | # |
On IRC, wgrant strongly insisted that sinzui should be consulted about this.
Also, my email logs say that lifeless suggested a celebrity (See email May 1st to launchpad-dev). I have no idea how it became a database column in my todo list.
| Jonathan Lange (jml) wrote : | # |
I've spoken with sinzui on IRC. In a nutshell, here's the behaviour we want
1. if the team owning the PPA is private, and you're in the team:
a) you are allowed to create a private PPA
b) you are not allowed to create a public PPA
2. if you are allowed to create private things on LP, then you are be allowed to create private PPAs for public teams
* "you are allowed to create private things" == you.checkAllowV
* True if admin, commercial admin or they have a commercial subscription
* used currently for whether to show checkbox on private teams
3. otherwise, you are not allowed to create private PPAs
This does not require a database patch and does not require a celebrity. I'll proceed with this implementation approach on Monday if I don't hear otherwise.
Unmerged revisions
- 11659. By Jonathan Lange on 2012-06-08
-
Add column to control who can create private PPAs.

I should add that the goal here is for my team to be able to create PPAs without hassling existing commercial admins and without acquiring the v. high level of privilege and permission that commercial_admin grants.