Considering a scenario where the owner of the newsletter no more wants to continue as the owner and needs to handover the ownership of the newsletter.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Duplicate | Qgil | T125545 Phabricator Q&A session for Community Liaisons | |||
Resolved | Qgil | T116025 Goal: Align Community Liaison and Developer Relations project management practices | |||
Resolved | Qgil | T119387 Community Liaison and Developer Relation quarterly goals for January - March 2016 | |||
Declined | None | T104131 Exporting existing newsletter to the Newsletter extension | |||
Resolved | Addshore | T110170 Goal: Deploy Newsletter extension in Wikimedia | |||
Resolved | Qgil | T110642 Implement all the features required for running the Newsletter extension in Wikimedia | |||
Resolved | Tinaj1234 | T108482 Assign ownership of newsletter to another user |
Event Timeline
How about just getting rid of the concept of owners entirely? That would make things a lot simpler. Currently, it looks like the only purpose of owners is to assign publishers. IMO, we should add a new right for letting privileged users add publishers to newsletters. This would be more in line with MediaWiki's user permissions system.
Yes, reducing permissions to Publishers might make sense. We still have the problem of what happens when there are no Publishers active, who can give permissions to new publishers. I guess the admins of the site can always act?
Change 238753 had a related patch set uploaded (by Tinaj1234):
Add new user rights to Newsletter extension
Change 238753 merged by jenkins-bot:
Restrict adding publishers to 'newsletter-addpublisher' right
Change 240750 had a related patch set uploaded (by Glaisher):
Remove ownership system from Newsletter
Note: Restrict adding publishers to 'newsletter-addpublisher' right checks need to also happen in the API classes / class