This is a very widely used tool that assists in administration and legal compliance, and as such needs quick resolution. Thank you @Earwig for beginning to tackle this.

In T187757#3987634, @revi wrote:

It was Unbreak now! when it was marked as resolved, so I don't think there's any need to change the priority.

I've undone @MusikAnimal 's hiding of the thank button. Button is now live again and working.

Status update? This is extremely high priority.

Note that multiple English Wikipedia admins/Wikimedia OTRS members/Wikimedia IRC Group Contacts strongly suggest that any request by Zppix for any additional tools be denied, anywhere on any Wikimedia project, based on recent prior (highly unacceptable) behavior towards Wikimedia staff.

Whenever a full ETC is available, can someone post it here? Just need to be able keep some of our customers informed. (Wikimedia OTRS)

Fantastic, thank you for the quick response!

The community should have been informed about this regardless of any technical matters before it was patched, so script owners could have worked around it. A big trout to @aaron on this.

@Urbanecm I've given you the right, just to ensure everything is gtg this time.

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!

@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 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.

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

@Urbanecm Yes at this stage you can create the patch, as I'll be formally closing the RFC in a few days and I don't see any major consensus changes happening before then.

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

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.