Merge lp:~wgrant/launchpad/question-content-lockdown into lp:launchpad
Proposed by
William Grant
Status: | Merged |
---|---|
Merged at revision: | 17859 |
Proposed branch: | lp:~wgrant/launchpad/question-content-lockdown |
Merge into: | lp:launchpad |
Diff against target: |
261 lines (+89/-30) 6 files modified
lib/lp/answers/browser/tests/views.txt (+16/-9) lib/lp/answers/configure.zcml (+5/-1) lib/lp/answers/doc/notifications.txt (+2/-2) lib/lp/answers/stories/question-edit.txt (+17/-14) lib/lp/answers/tests/test_question.py (+35/-1) lib/lp/security.py (+14/-3) |
To merge this branch: | bzr merge lp:~wgrant/launchpad/question-content-lockdown |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+279069@code.launchpad.net |
Commit message
Lock down Question.
Description of the change
Lock down Question.
Question content doesn't usually evolve through the life cycle as bug content does, and there is no audit trail, so letting any user edit the title and description is mostly useless and very abusable. Those fields are now behind launchpad.Edit, which is a union of launchpad.Owner (creator) and launchpad.Append (target owner, ~admins, and now ~registry).
To post a comment you must log in.