not MediaWiki-General, these requests should go through Wikimedia-Site-requests

Change 286168 had a related patch set uploaded (by Urbanecm):
Creation of page mover userright

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

My patch includes increasing rate limit to 100/60 for page movers, creating page mover user right which can move subpages and supressredirect.

I am scheduling this to May 2 for Morning SWAT window (15:00 - 16:00 UTC), if there will be something which should be added to this patch, please notice me in this task. Thanks.

@Urbanecm I don't think you should roll it out before the RfC is closed. The place is a stickler for formalities and it'd be better if you can do all of it together, whatever there are.

@Ankit-Maity Ok, I reverted my scheduling and we'll wait until the RFC ends.

I added the RFC to MediaWiki:Watchlist-details, so that the entire Wikipedia editorial community can place their input into the proposal. The earliest a patch can be scheduled is after 19 May 2016. Currently there isn't support for rolling out an increase in the page move rate limit.

@Coffee So should I schedule it on some day after May 19? Or wait?

Considering the steady consensus so far I think it should be fine to schedule it for after the 19th.

Considering that there's a steady increase for page movers to be able to move move-protected pages, you might need to make a new patch.
Also, rate limits will be limited to 20/60 - 30/60 as most people opposing it want a compromise and it won't pass without a majority.

@Ankit-Maity @Coffee Hi, can I make final patch for this? If so, can anybody tell me how the current settings should be changed?

Settings changed by my patch

• Rate limit for extendedmovers will be increased to 100/60
• Extendedmovers will be able to supress redirect and move subpages
• Sysops will be able to grant or remove this user group

Anything to add/remove/change?

Ratelimit was removed from the patch. Anything else?

@Coffee Is it ok to schedule this to Wednesday, May 18 (or to Monday, May 16 if you want)? I know that somebody requested scheduling after May 19 but I think that it's fine if RFC'll be closed before deploying. No matter what date you'll choose, it'll be deployed between 15:00 - 16:00 UTC.

@Urbanecm Just for clarity: what's the first date after the 18th it could be scheduled for?

@Coffee For the 23rd.

@Urbanecm Ok, since it's only 4 days out from the advertised close date let's schedule it for the 23rd. Like I said, I doubt any major changes in consensus are going to happen by the 19th. But, at least this way, we should be able to ensure there won't need to be another ticket opened a day after implementation.

@Coffee Ok, I'll schedule it immediately after deployment calendar for week of 23rd will be available.

@Urbanecm There's sufficient consensus for editors with this user right to move pages with move-protection (as I expected).
@Coffee Shouldn't we take a lower threshold of ratelimits and push a patch for that (something better than nothing policy) since we have people who want ratelimits increased, some with 100/60, others with 20/60, etc. Although there might be accusations of bias, there's safety as well as a support with a lower limit and there's no reason for discontentment from the supporters of that proposal either.

@Urbanecm Do crats have all admin rights per se?

@Ankit-Maity

No, if someone is a crat and not a sysop, he is not able to grant any usergroup which can be granted by sysops. But if enwiki's community wants settings to be changed this way, please open new ticket and give community consensus.

I didn't understand the request about move-protection. Do you want to add new moving protection level called "move-protection" and allow extendedmovers to move pages protected with this? Or do you want to allow extendedmovers to move all protected pages which can currently be moved only by sysops?

@Ankit-Maity - First, I'm not going to have anything with less than 75% support turned on, and there is only 67.7% support for giving extendedmovers their own protection category. So, no, there is not currently enough support to add that to the patch. Second, I won't turn on any level of the throttle increase because there simply isn't consensus yet, and any level decided upon by myself or any other admin would have to be at least somewhat arbitrary. And seeing there is no immediate need for it, we can wait till support is garnered properly.

@Urbanecm - No changes to the patch are needed at this time.

@Coffee Okay, thanks. If something'll be needed till May 23, please notify me. Thanks.

The RFC has been officially closed and promoted to policy on Wikipedia. No changes to the patch are required, as all items expected to be approved or denied were closed as such in the RFC. Thank you all (especially Urbanecm) for your help in this process!

Ok, thanks. It'll be deployed on May 23 between 15:00 and 16:00 UTC.

Change 286168 merged by jenkins-bot:
Creation of page mover userright on enwiki

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

On enwiki this appears to be live, however the option for suppression of redirect creation is not being presented (at least not yet)

Created related pages:

MediaWiki:Grouppage-extendedmover
MediaWiki:Group-extendedmover-member
Wikipedia:Requests for permissions/Page mover

@Xaosflux Try purging the cache on the move page.

@Music1201 no joy, on the move dialog the new "Move subpages (up to 100), if applicable" option is now showing, however the expected "Leave a redirect behind" dialog is not.

The user right has a typo in InitialiseSettings.php.
supressredirect should be suppressredirect

Thanks @JJMC89! I'll fix it immediately.

Thank you @JJMC89 and @Urbanecm ! - "given enough eyeballs, all bugs are shallow" -LT

Change 290290 had a related patch set uploaded (by Urbanecm):
Typo in enwiki's extendedmovers settings

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

Change 290290 merged by jenkins-bot:
Typo in enwiki's extendedmovers settings

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