As per the MVP plan, we will have the creator of the Newsletter as the only one having right to edit the Newsletter basics, create a new issue and announce a new issue.
Managing a Newsletter for the publisher would include:
It should preferably go to the bottom of Special:NewsletterPublishers as a separate section.
Maybe we can discuss on the various user rights we should have for Newsletter ? @01tonythomas, @Qgil
Quick thought: we can start keeping it very simple.
Roles:
The creator of the newsletter acquires Owner rights automatically.
Change 228789 had a related patch set uploaded (by Tinaj1234):
Add publishers to existing newsletters
@Tinaj1234, please make sure that the newly added publishers too are able to create new issues in https://gerrit.wikimedia.org/r/#/c/228789/
Oh oh. I dont think we can close this now, as we got
Left.
If Changing access rights for Collaborators is indeed not high priority, we can create a task for it and leave it for later. However, I agree that removing collaborators should be still part of the current scope of this task.
Change 230141 had a related patch set uploaded (by Tinaj1234):
Removing collaborators from an existing newsletter
Looking at http://newsletter-test.wmflabs.org/wiki/Special:NewsletterManage, I was thinking of a more integrated UI for adding/removing contributors and also for managing their permissions:
| Newsletter | Contributors | Permissions |
|---|---|---|
| The Wiki Tribune | @Tinaj1234 | Owner - Publisher |
| @01tonythomas | Owner - Publisher - [ Remove ] | |
| Add [...................] | ||
| Pedianers | @QuimGil | Owner - Publisher |
| Add [...................] | ||
However, while I was typing this table I realized that the implementation might be complex for many reasons and we have a very few days of GSoC left. So maybe I can create a task proposing this enhanced UI, but we would leave it for later?
Change 230141 merged by jenkins-bot:
Removing collaborators from an existing newsletter