Make assigning participation essential limited to certain groups of users
Bug #1052130 reported by
Chris Johnston
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently, setting a user (or yourself) as participation essential is open to anyone. This has started causing problems with over-usage at UDS events.
Fix:
Change the ability for participation essential to be set to people related to the blueprint/project drivers.
Related branches
lp:~cjohnston/launchpad/part-essential
On hold
for merging
into
lp:launchpad
- Curtis Hovey (community): Approve (code)
-
Diff: 125 lines (+7/-63)2 files modifiedlib/lp/blueprints/stories/standalone/subscribing.txt (+3/-58)
lib/lp/security.py (+4/-5)
Changed in launchpad: | |
assignee: | nobody → Chris Johnston (chrisjohnston) |
status: | New → In Progress |
Changed in launchpad: | |
importance: | Undecided → Low |
Changed in launchpad: | |
status: | Fix Committed → In Progress |
Changed in launchpad: | |
assignee: | Chris Johnston (chrisjohnston) → nobody |
status: | In Progress → Triaged |
tags: | removed: qa-bad |
To post a comment you must log in.
Fixed in stable r15972 <http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ stable/ revision/ 15972>.