Requests for comment/Brainstorming of ideas to improve the global rename tools

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

The following request for comments is closed. This discussion has been dormant for a long period, and has served its purpose, resulting in some helpful suggestions and feedback. Effeietsanders (talk) 19:37, 27 January 2019 (UTC)Reply[reply]

Brainstorming of ideas to improve global rename tools
As suggested by my colleagues on our mailing list, I'd like to call for ideas about how the Special:GlobalRenameRequest and Special:GlobalRenameQueue could be improved.
Please submit new ideas by creating a new section so we can discuss each idea in its own section!

Submitted proposals[edit]

Lock requests being addressed[edit]

In order to avoid clashes in criteria, the system should detect if any steward or global renamer is addressing a request for rename and temporary prevent others from addressing it. —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

  • Support Support. I once or twice would have found this useful. Litlok (talk) 17:39, 4 June 2017 (UTC)Reply[reply]
  • Not sure if I understand. "Addressing" means that the request is opened by some user but it's not yet being processed? Stryn (talk) 16:24, 9 June 2017 (UTC)Reply[reply]
    @Stryn: Yes, that's right. —MarcoAurelio 10:08, 11 June 2017 (UTC)Reply[reply]
  • Support Support. RadiX∞ 00:22, 24 July 2017 (UTC)Reply[reply]
  • Comment Comment FlaggedRevs already has a built-in function to let other reviewers know that you're taking care of that revision. I guess something similar could be thought for this. —MarcoAurelio (talk) 08:18, 24 July 2017 (UTC)Reply[reply]
  • Support Support.--Alexmar983 (talk) 13:52, 5 August 2017 (UTC)Reply[reply]

Boilerplate responses[edit]

Tracked in Phabricator:
Task T171439

Boilerplate responses via dropdown, configurable on-wiki via MediaWiki: namespace, for the most used messages when declining. —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

Prevent users from submit rename requests if they have already one rename request pending[edit]

Tracked in Phabricator:
Task T172604

This is being abused. —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

  • Support Support Would prevent abuse in cases if a user send repeatedly global rename requests. —Alvaro Molina (✉ - ✔) 11:14, 2 June 2017 (UTC)Reply[reply]
  • Support Support--Biplab Anand (Talk) 08:26, 4 June 2017 (UTC)Reply[reply]
  • Support Support, only if the users can cancel their requests -an error is always possible. Litlok (talk) 17:37, 4 June 2017 (UTC)Reply[reply]
  • Oppose I don't think this should be done. Users accidentally filing an erroneous request can only fix it by resubmission, unless I am mistaken. Thus, I would prefer a different approach, such as the one Litlok pointed to above. --Vogone (talk) 20:58, 5 June 2017 (UTC)Reply[reply]
    @Vogone and Litlok: Yes, that was what I had in mind. Sorry for not being clear enough. —MarcoAurelio 10:07, 11 June 2017 (UTC)Reply[reply]
  • I agree with Vogone. Stryn (talk) 16:25, 9 June 2017 (UTC)Reply[reply]
  • Support Support CreativeC38 (talk) 21:06, 3 July 2017 (UTC)Reply[reply]
  • Support Support. Excellent idea. RadiX∞ 00:16, 24 July 2017 (UTC)Reply[reply]
  • Support Support This is only sensible. Requesters should not be allowed to flood the queue with requests, and they should be able to view and cancel any pending requests they have submitted, if necessary. —k6ka 🍁 (Talk · Contributions) 14:57, 5 August 2017 (UTC)Reply[reply]
  • Support Support--Alexmar983 (talk) 03:45, 8 August 2017 (UTC)Reply[reply]

Allow users to cancel pending rename requests[edit]

Tracked in Phabricator:
Task T172601

Could be useful. —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

Allow banning some users (temporary/permanently) to submit more rename requests[edit]

Tracked in Phabricator:
Task T101615

Prevent, via a similar feature as blocks, users to submit indefinitely or temporary any new rename requests. This is being abused. —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

Allow searching by "performer" on the closed requests queue[edit]

Tracked in Phabricator:
Task T111837

Being able to search more efficiently using a new "performer" param. —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

Better page design[edit]

Do you like it, what improvements would you make? —MarcoAurelio 10:41, 2 June 2017 (UTC)Reply[reply]

Add confirmation box in Special:GlobalRenameRequest[edit]

I propose add a confirmation box at the end of global rename requests where indicated that the user confirms make the request and may not re-request to new global rename in a while wise. This will allow the user can be aware of the situation and know that there may re-request each time. —Alvaro Molina (✉ - ✔) 13:13, 2 June 2017 (UTC)Reply[reply]

  • I'd support the checkbox with other content: something about recognizing that you think that your rename request complies with the rename policy, that we may deny it with or without cause and, specially due to privacy policy and terms of use, that all requests will be kept logged and that there's no way to avoid that. —MarcoAurelio 10:06, 11 June 2017 (UTC)Reply[reply]

Make a form in case of renaming problems with an auto-submitting at Steward requests/Username changes[edit]

That's a detail but it would save time for a lot of people. CreativeC38 (talk) 21:12, 3 July 2017 (UTC)Reply[reply]

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Requests_for_comment/Brainstorming_of_ideas_to_improve_the_global_rename_tools&oldid=20105712"