I agree that this is a problem. Since the linked page is about managing contributors, I think the simple and best option is to change the label to "Collaborators".
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fix label of "Manage" button to avoid confusion | mediawiki/extensions/Newsletter | master | +5 -5 |
| 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 | T116353 Design feedback on the Newsletter extension | |||
| Duplicate | Tinaj1234 | T131457 "Manage" label in Newsletter detail page is confusing |
Event Timeline
Comment Actions
Change 280837 had a related patch set uploaded (by Tinaj1234):
Fixing label of "Manage" button to avoid confusion
Comment Actions
I think the actual issue which MZMcBride pointed out is that it linked to Special:ManageNewsletters which showed all the newsletters. We killed that page since then and it now links to a specific manage page for each newsletter.
If we are changing the "Manage" term to "Collaborators", I think we should use that consistently, not just in a few places.
Comment Actions
I don't have any strong opinion about the term we use. Publishers/Managers/Collaborators all of these fine by me. I just want us to use it consistently :) (at least on user facing UI; we have been using "manage" in the code/messages/docs so far).
Comment Actions
Closing this down, and adding it to the task T131489. This would mean that we keep Special:Newsletter/<id> readonly, and have a Special:Newsletter/<id>/manage, which would allow:
- Editing of Newsletter-name
- Editing of Newsletter Main page
- Editing of Newsletter description, and
- Editing of Publishers
We had most of this implemented before too though!