Formerly active in various development and janitorial areas/activities here on Phabricator and Gerrit, but I am no longer.
Sat, Oct 24
Fri, Oct 16
Fri, Oct 9
Thanks @valhallasw. Do you think it takes a while since the web gets updated? Because it looks #mw1.32.0-wmf.999 is still there :-)
Thu, Oct 8
I looked for the typo as posted in this task. https://codesearch.wmcloud.org/search/?q=Summaray&i=nope&files=&repos= only shows "notification-bs-readconfirmation-remind-summary": "Summaray of the notification that states, that a user reminds the receiving user to read a page\n* $1 - Name of the user, that reminds the receiving user\n* $2 Real name of the user, that reminds the receiving user\n* $3 - Name of the page, the receiving user has to read confirm on".
I'll patch this in a while.
This was reversed as RelEng would prefer that the extension get security and performance reviewed before it starts getting branched.
I do not understand this Task. If you want those pages deleted you need an administrator to delete them. There are several ones https://test.wikipedia.org/wiki/Special:ListUsers?group=sysop. Thanks.
I can try to delete the previous releases/tags, but I feel installing and approving the webhook should be 'okayed' by RelEng. Pings to @thcipriani for opinions.
Wed, Oct 7
Mon, Oct 5
As per https://www.mediawiki.org/wiki/Extension:AbuseFilter#anchor-Emergency_throttling, even if a filter is throttled, so-called "safe" actions are still allowed (and I assume that safe actions means those not in $wgAbuseFilterRestrictions (e.g. block, rangeblock, blockautopromote, degroup) so warn, disallow, tag, etc. would, in theory, still work (ping @Daimona who knows better).
Default branch changed to master.
I will change the default branch to master as that seems uncontroversial. Regarding the webhook, I do not think I have done anything like that before, so I'd like to ask the Release-Engineering-Team for advice.