Page MenuHomePhabricator

Managing an existing Newsletter
Closed, ResolvedPublic

Description

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:

  1. Adding collaborators to an Existing newsletter
  2. Removing collaborators from an Existing newsletter
  3. Changing access rights for Collaborators ( not high priority )

It should preferably go to the bottom of Special:NewsletterPublishers as a separate section.

Related Objects

StatusSubtypeAssignedTask
DuplicateQgil
ResolvedQgil
ResolvedQgil
DeclinedNone
ResolvedAddshore
ResolvedTinaj1234
ResolvedTinaj1234
ResolvedTinaj1234
ResolvedTinaj1234
ResolvedTinaj1234
ResolvedTinaj1234
Resolvedsiebrand
ResolvedTinaj1234
ResolvedTinaj1234
ResolvedTinaj1234
ResolvedTinaj1234
Resolved01tonythomas
DuplicateTinaj1234

Event Timeline

01tonythomas raised the priority of this task from to Medium.
01tonythomas updated the task description. (Show Details)
Tinaj1234 raised the priority of this task from Medium to High.Jul 30 2015, 10:54 AM
Tinaj1234 set Security to None.

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:

  • Publisher: can announce new issues.
  • Owner: Publisher permissions + can assign/remove Publisher permissions to other users.
  • Wiki admins (bureaucrats?) can assign/remove Owner permissions to other users for specific newsletter (only needed in case of abandonment/conflict)

The creator of the newsletter acquires Owner rights automatically.

Okay, I agree. Those are the fundamental rights we require.

Change 228789 had a related patch set uploaded (by Tinaj1234):
Add publishers to existing newsletters

https://gerrit.wikimedia.org/r/228789

Roles:

  • Publisher: can announce new issues.
  • Owner: Publisher permissions + can assign/remove Publisher permissions to other users.

Should the publishers and owners be confirmed users (confirmed email id) ?

@Tinaj1234, please make sure that the newly added publishers too are able to create new issues in https://gerrit.wikimedia.org/r/#/c/228789/

Change 228789 merged by jenkins-bot:
Add new publishers to existing newsletters

https://gerrit.wikimedia.org/r/228789

Oh oh. I dont think we can close this now, as we got

  1. Removing collaborators from an Existing newsletter
  2. Changing access rights for Collaborators ( not high priority )

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

https://gerrit.wikimedia.org/r/230141

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:

NewsletterContributorsPermissions
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?

Thanks @Qgil for this one. It looks great, but will take a bit long to get done.

@Qgil : we should be moving this to a separate task, and lets see if we get enough time to complete this one too.

Change 230141 merged by jenkins-bot:
Removing collaborators from an existing newsletter

https://gerrit.wikimedia.org/r/230141