MediaWiki-extensions-WebDAV created. Repository in gerrit and maintainer willing to use phabricator to track issues/development. Done.
https://iso639-3.sil.org/code/trv says Taroko.
Per https://iso639-3.sil.org/code/xsy Saisiyat is the name of the language. I'll make a patch today.
Hello @Ladsgroup. It was @Reedy and @Jdforrester-WMF if I remember rightly. And there's T212881: addWiki.php broken creating ES tables documenting the issue, which was discovered when Sam was creating the test-commons project. Regards.
@dbarratt Feel free to reschedule for Feb. 19. My question is in my personal capacity, and do not represent the Meta-Wiki feelings on the matter. Maybe after using/testing it even I could change of mind ;-)
I am not sure we need partial blocks on Meta to be honest. Will projects be allowed to opt-out from partial blocks? Thanks.
Just in case it is needed:
@Tgr has helped us in the past, too, with stuck global renames.
According to https://wikitech.wikimedia.org/wiki/Stuck_global_renames the system should try to restart failed jobs several times. I'm not sure about jobs stuck "in progress" though.
Rename is ongoing: https://meta.wikimedia.org/wiki/Special:GlobalRenameProgress/Wilfredor
I am free to do it today if @Marostegui or other DBA is willing to have a look while the rename is ongoing.
It looks we'll start to have rolled it on wmf wikis starting from tomorrow (so by Thursday the message should be there for all Wikimedia wikis).
Will be rolled during the next MediaWiki trains, depending on the wmf branch this patch is included to. Expect one or two weeks (a bot will tell us shortly when).
I am not so sure. We've been seen these again:
The default message (centralauth-error-locked) comes from CentralAuth. However in order to implement the suggested customization we'll need to create a Wikimedia override in WikimediaMessages indeed. However I'll probably change the wording of the message and point to [[m:Special:Contact/stewards]] instead given that we don't want locked users to appeal with IP addresses on Meta and elsewhere.
Sun, Feb 17
Sat, Feb 16
Tested with base pages, translated pages and translation units. No results.
beta-update-databases-eqiad seems also affected
Ignoring it as it was suggested elsewhere is not an option. The system provides very bad translations, unusable in the 99% of the cases. If someone starts to "translate" using this feature we'll spend more time fixing the translations than doing our work. Thank you.
Fri, Feb 15
Hello @herron - Since the merge of the patch that got to be reverted (Feb 5/6) I've not received any spam email of the type reported. Not sure if other mailing lists were affected though.
Could I have my botflag at sr.wikinews removed, please? Until T122705 is resolved I won't be able to handle this, and at this point I think that the maintenance script path will be a better approach. Thank you.
I have resigned maintainership of this tool.
Thu, Feb 14
It looks like "projects" works fine now: https://tools.wmflabs.org/stewardbots/hat-web-tool/projects.php
No defined process other than create a task and wait for someone to action. There are two types of admins: sysop and contentadmin. With the creation and rollout of interface admins probably the segregation doesn't make much of the sense that it had in the past, though; although probably still makes sense. Usually @bd808 or @scfc handled user rights requests in the past for me, so I'm taking the liberty to mention them in here. Regards.
We should probably figure a way to keep Special:Log/usermerge entries even after the extension is undeployed, because this feature was used and it keeps important data (specially on Wikivoyages). Thanks.
It is a tool that we host but whose code is hosted in another tools project IIRC. I'll take a look at the repos and get back to you with an answer. Regards.
Mon, Feb 11
Looks like it works now: https://integration.wikimedia.org/ci/job/scap-beta-deb/14/console
What about a personal email to the affected users instead to the whole lists? This is not very relevant for the majority of our subscribers :)
Note that you should issue those jobs and crontab via login-stretch.tools.wmflabs.org :)