No concerns from me.
Sun, Oct 21
In that case, the patch for closing the wiki is already uploaded on Gerrit, should ops feel inclined to close it now. Otherwise, as I've said, I can wait.
AIUI the method we requested in the task above was to be applied when a page had a high number of revisions, not for all page deletions. If batched deletions are happening for all pages, we can certainly slow maintenance a lot. CC @BPirkle and @tstarling.
OTOH, does locking prevent exporting of content? I don't think so, so we can just close and let @Raystorm fetch and retrieve any content. If locking does prevent Special:Export usage, then I don't mind to continue waiting (in fact I'm mostly afk these days so this can continue waiting).
Mon, Oct 15
With follow-up at https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/WikimediaMessages/+/467423/ as well.
This made the test pass, but I'm not sure if this is the desired solution? Please advice.
npm ERR! Failed at the @ test script 'grunt test'. 11:41:34 npm ERR! Make sure you have the latest version of node.js and npm installed. 11:41:34 npm ERR! If you do, this is most likely a problem with the package, 11:41:34 npm ERR! not with npm itself. 11:41:34 npm ERR! Tell the author that this fails on your system: 11:41:34 npm ERR! grunt test 11:41:34 npm ERR! You can get information on how to open an issue for this project with: 11:41:34 npm ERR! npm bugs 11:41:34 npm ERR! Or if that isn't available, you can get their info via: 11:41:34 npm ERR! npm owner ls 11:41:34 npm ERR! There is likely additional logging output above. 11:41:34 11:41:34 npm ERR! Please include the following file with any support request: 11:41:34 npm ERR! /src/npm-debug.log
This is weird. I don't know why this is suddenly failing. As far as I can see from the eslint docs, this might be caused by the extends: wikimedia from the .eslintrc.json file, which applies https://github.com/wikimedia/eslint-config-wikimedia
Sun, Oct 14
@D3r1ck01 Hi. Thanks, it seems to be working again. Regards.
Sat, Oct 13
Fri, Oct 12
Documentation update is cherry-picked to REL1_31 as well.
Thu, Oct 11
Extension still deployed, but disabled on all wikis.
I have updated the README file on master at https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Lockdown/+/466788/ - I'll cherry-pick to REL1_31 as soon as it's merged.
I think that maybe an empty PHP entry point as explained at would be a good idea. Do you think we need one?
@Cyber1000 It looks like the file was renamed at https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Lockdown/+/8b582f6f62f7c9d1055446ae386960d3196a6ba8
Due to ongoing personal/health issues.
Stalling given that this cannot be actioned until the monthly period has passed. Thanks.
Wed, Oct 3
Due to ongoing health and family issues I am resigning from this task as I am very much likely to not be able to handle this soon.
Tue, Oct 2
Mon, Oct 1
Thu, Sep 27
I will try to have this done today.
Tue, Sep 25
Mon, Sep 24
This is pending DBA review. Per the Datacenter-Switchover-2018 guidelines we were given via wikitech-l, we're adviced not to deploy any extension or service that adds tables or does schecha changes unless DBA says it is okay to do so. The translate extension needs some tables to operate.
Currently weekly portal deploys happen thanks to @Jdrewniak - how's the current process? Thanks.
After some years without any comments, I move that this is approved and a HTML-5 tag is created.
No actual patch for review (1 abandoned, 1 merged).
Sun, Sep 23
On the other hand, if purge_checkuser detects CheckUser is not installed it will just print that the CheckUser extension is not installed and will move along. It's just a bit of logspam instead of potential privacy issues.
Sep 22 2018
Done. All OCG-related repos have been emptied and archived on Gerrit/Diffusion and its GitHub mirrors deleted. Code still avalaible on Gerrit browsing their histories if needed.