Requests for Comment/Global renamers

Currently, global rename requests can take up to a week, and sometimes even two weeks, to be processed. The creation of a separate "Global renamers" group would help reduce turnaround time for global renames by reliving pressure from the Stewards, who currently are the only users capable of performing renames.

Please note that Proposals 2.1 and 2.2 are mutually exclusive, and as such cannot both be adopted. The only change between each is the support ratio of 80%.

Proposal 1 (Group)
Create a local group on Meta with the identifier "global-renamer", to be titled "Global renamers", with the right "centralauth-rename", which Stewards will add and remove.

Support (1)

 * 1)  Per my previous comment but decided to lean toward here. LetraSeca (talk) 21:29, 26 June 2022 (UTC)

Proposal 2.1 (Appointment)
'''Users may nominate themselves or others for the role via a request at Requests for permissions. Once the nomination is accepted (if made by another user), the request must stay open for at least seven (7) days. Community members may ask questions to the candidate. A Steward will close the request and evaluate consensus.'''

Support (2.1)

 * 1)  LetraSeca (talk) 21:31, 26 June 2022 (UTC)

Proposal 2.2 (Appointment)
'''Users may nominate themselves or others for the role via a request at Requests for permissions. Once the nomination is accepted (if made by another user), the request must stay open for at least seven (7) days. Community members may ask questions to the candidate. A Steward will close the request and evaluate consensus, generally according to a support ratio of 80%.'''

Proposal 3.1 (Revocation)
Users may be removed from the position by a Steward if they repeatedly fail to adhere to the Username Policy when processing requests.

Support (3.1)

 * 1) LetraSeca (talk) 21:33, 26 June 2022 (UTC)

Proposal 3.2 (Revocation)
Users may be removed from the position via a successful (defined as 50% support) vote of no confidence by the community, opened in good faith.

Support (3.2)

 * 1) LetraSeca (talk) 21:33, 26 June 2022 (UTC)

Proposal 4 (Inactivity)
Global renamers who go six (6) months without making edits or logged actions on Miraheze will have the right removed for reasons of inactivity.

Support (4)

 * 1) LetraSeca (talk) 21:33, 26 June 2022 (UTC)

Pre-rewrite comments/votes

 * 1) This sounds like a good idea, but is there any particular strong need for extra people who can do renames? Is there a big backlog on rename requests? FirstNoelle (talk) 14:39, 26 June 2022 (UTC)
 * There is a special page to review global rename requests - Special:GlobalRenameQueue. Cigaryno (talk) 14:47, 26 June 2022 (UTC)
 * I can't see anything on that page, because I'm not a Steward. FirstNoelle (talk) 14:51, 26 June 2022 (UTC)
 * 1) First, I would like to ask if you meant to tag this as a draft. Secondly, unlike Wikimedia, we do not have dozens of renames requested every day. At most, we sometimes have one or two per week and they usually get processed pretty fast. As such, I do not see the need for a new group dedicated solely to handling renames. Agent Isai  Talk to me! 15:28, 26 June 2022 (UTC)
 * This is utterly pointless. --DarkMatterMan4500 (talk) (contribs) 15:31, 26 June 2022 (UTC)
 * I’ve untagged the RfC as a draft, and instead have moved it to open as the RfC is in the main namespace. Not sure whether it was a mistake or intentional as a draft, but I’m about to leave a talk page message for the creator. Thanks - BrandonWM (talk • contribs • global • rights) 15:32, 26 June 2022 (UTC)
 * This group may be requested in the RFP page if created, in case someone is curious with the feature to globally rename accounts. Cigaryno (talk) 15:41, 26 June 2022 (UTC)
 * Is there any other reason for the creation of this group? Agent Isai  Talk to me! 15:46, 26 June 2022 (UTC)
 * By default, all RfCs are marked as draft. Mainspace draft RfCs are also not uncommon which is why I asked the maker of this RfC if this was a draft. I would leave it as a draft as this is malformed in that it doesn't set out the criteria for being elected, for revocation, what it's scope is, what it's assigned rights are, etc. Agent Isai  Talk to me! 15:43, 26 June 2022 (UTC)
 * ✅. Shouldn’t the comments be removed as well if this article is truly a draft? Thanks - BrandonWM (talk • contribs • global • rights) 15:51, 26 June 2022 (UTC)
 * The right is gained with future requirements and revoked in case of abuse. Cigaryno (talk) 16:05, 26 June 2022 (UTC)
 * I’m not sure you’re understanding what Agent Isai and I are trying to tell you. Basically, in order for this RfC to even be considered actively, you need to form it so there are clear guidelines for when the right can be requested. For instance, read the Stewards page. There’s clear criteria for both election and revocation, and parameters for a steward’s responsibility. Thanks - BrandonWM (talk • contribs • global • rights) 16:12, 26 June 2022 (UTC)
 * 1) Taking a look at the rename log, there are enough renames performed that I would consider the creation of a renamer group if, on average, global renames had a multi-day turnaround time. Thus, I'd like to see some statistics from the Stewards before voting. Back in April, I had a global rename, and it took about a day, but that's just my anecdote. — Chrs (talk) 19:38, 26 June 2022 (UTC)
 * Per comments on Discord from Raidarr, apparently rename requests can sometimes get forgotten and end up taking a week or two. Considering that, I think the creation of a group is probably warranted, so I'm going to work on rewriting this RfC into a proper state. — Chrs (talk) 20:23, 26 June 2022 (UTC)
 * 1) There is currently a minor issue with this when considering overall steward activity (myself roughly daily, then Doug very roughly weekly/biweekly, then the other two extremely intermittently) and the fact the global rename queue on our end is not very prominent and needs to be specifically hunted down (no sidebar link, notification, etc). Doug has been reasonably good at remembering when he does show up, so mainly the issue is me for the activity I have when I simply forget about it in the course of other things. Chrs has just added a link to the sidebar for the steward group, which I think strongly buffers both points and makes it harder to miss both for me and the other stewards when they are present. I feel an entire group for this is redundant and far too specific for an issue that can be resolved by a) me scheduling better and b) more stewards in general since I would say that's more reflective of a general steward activity issue, and what we're looking at here is a minor symptom in a much more problematic overall system that requires wider adjustments or more volunteers. Overall rename traffic is sufficiently low that I think it would hardly justify inclusion alongside IWA as a global bit. Renames also have specific conventions embedded in stewarding which I'm not sure needs to be split off. --Raidarr (talk) 00:32, 27 June 2022 (UTC)

Support

 * 1)  as proposer. Cigaryno (talk) 13:47, 26 June 2022 (UTC)
 * 2)  It's a good idea, I agree. AlPaD (talk) 18:24, 26 June 2022 (UTC)
 * 3) This should reduce stress of Stewards by allowing another group of users to rename users. --  Bukkit  [ cetacean needed ] 18:45, 26 June 2022 (UTC)

Abstain

 * 1) Not that much rename requests, but I don't see any point of this privilege being solely exclusive to stewards. LetraSeca (talk) 17:15, 26 June 2022 (UTC)

Oppose

 * , but with a question to . How big of a global rename queue is there? Are the requests backlogged, or is there a consistent request and output in a timely fashion? Thanks - BrandonWM (talk • contribs • global • rights) 15:27, 26 June 2022 (UTC)