It is requested that Mass-message Senders group is created on Urdu Wikipedia similar to English Wikipedia as some of the non-admins are also interested in sending messages of community interest. A c ommunity resolution for this is passed here.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Urbanecm | T144701 Enable Mass-message Senders on Urdu Wikipedia. | |||
Resolved | MarcoAurelio | T147743 Typo in urwiki massmessage-sender group |
Event Timeline
(Removing Wikipedia-App-General-or-Unknown as this is unrelated to the mobile application. Setting Wikimedia-Site-requests instead.)
Change 309047 had a related patch set uploaded (by محمد شعیب):
Add massmessage-sender group to urwiki
@MuhammadShuaib Should I take this patch from you and deploy it at September 08? BTW I've fixed your patch ;).
Thanks for fixing, I assigned this to you. :)
PS: How did you fix it and how do you deploy?
Okay, will be deployed today between 15 and 16 UTC.
You didn't close the array about group. For deploying you must schedule your change at https://wikitech.wikimedia.org/wiki/Deployments and be available in #wikimedia-operations at freenode during the window. Somebody will guide you :).
Hi, I am still seeing this . Will the actual application of this deployment take some more time?
Opps, this is because mass message senders can send messages, but nobody can assign this permission. Could you tell me who should be able to grant/revoke this group? Sysops? 'Crats? Should the granter be able to revoke the group too? Currently only stewards are allowed to do this.
Okay, writing a patch. The nearest deploy window is at Monday, in the meanwhile you can ask stewards for assigning this permission (preferably a 'crat should ask as a member with high trust of the comunnity).
Change 309368 had a related patch set uploaded (by Urbanecm):
Allow sysops/'crats to assign massmessage-sender in urwiki
Change 309368 merged by jenkins-bot:
Allow sysops/'crats to assign massmessage-sender in urwiki
Nothing happened :). I closed it sooner that I may (the change was deployed only on one test server so I could test it and I couldn't break anything :)). My mistake ;).