WikimediaMaintenance extension, containing WMF-specific maintenance scripts
Details
Fri, Oct 10
Thu, Oct 9
Fri, Oct 3
Sep 10 2025
This probably needs the SecurePoll schema files to be split in two, one for the tables on all wikis and one for the tables on wikis with local elections only?
Sep 9 2025
Sep 6 2025
Aug 21 2025
Aug 14 2025
Re-reading my first response, I realize I might have been a bit unclear. Indeed my focus was to respond to number 2, namely should it contain the shell username of whoever made the wiki? , not to question sending the email in the first place. I agree that this should still be sent. It's a notification as you say, not an auditing mechanism.
Aug 13 2025
Sorry yes, I wrote that misleadingly, but I think @akosiaris and I are both addressing the question of whether the username needs to be in the email body. No objections to sending an email notification.
I think we are mixing two questions here:
I agree with @akosiaris (and thanks for the archaeology). It wouldn't be hard to implement this, but I think it's the wrong approach -- especially if addWiki.php is the only script using SUDO_USER, we should update the script rather than add an anachronism to pretend we're still using sudo.
BTW, on the technical side, mw-script does indeed keep the username in the labels of the job and the pod, e.g.
This functionality was added 10 years ago in https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/WikimediaMaintenance/+/a17c2ef30e0e85ced460f304cf481cdb7d924486%5E%21
@RLazarus Do you have any thoughts on how to tackle this one, please?
Aug 12 2025
T393444 reports that (likely since this change?) emails are not being sent anymore to the newprojects mailing list when addWiki.php runs.
Jun 25 2025
Jun 12 2025
I think this is done. If there are any remaining issues, they can be split out into separate tasks.
May 21 2025
May 9 2025
I dropped api_feature_usage, bot_passwords and globalimagelinks in nupwiki. Someone in TSP says securepoll_log should actually exists and it's weird it's not in enwiki.
May 6 2025
May 5 2025
Not sure about securepoll_log but the rest of nupwiki tables missing in enwiki I'm sure needs fixing and removal.
May 3 2025
Comparing it to enwiki, on enwiki there are following tables which are not on nupwiki:
Currently the following tables are created on wiki creation (nupwiki created in T390384):
Apr 24 2025
Apr 8 2025
Apr 1 2025
Mar 28 2025
Mar 19 2025
Maybe all extensions listed as todo in T348573: All Wikimedia extensions that store their data outside the main database should use a virtual database domain can cause creation of tables in the wrong database, when the extensions is enabled at the install step.
Mar 17 2025
bounce_records now fixed thanks to @Reedy and only cn_notice_projects left.
Mar 11 2025
For both bounce_records and cn_notice_projects they can't be fixed because they are not migrated to virtual domains and have their own ad-hoc way.
Mar 2 2025
Mar 1 2025
Feb 28 2025
Change #1123643 merged by jenkins-bot:
[mediawiki/extensions/ApiFeatureUsage@master] Fix wiring of schema change updates
Change #1123643 had a related patch set uploaded (by Ladsgroup; author: Amir Sarabadani):
[mediawiki/extensions/ApiFeatureUsage@master] Fix wiring of schema change updates
Feb 27 2025
Feb 26 2025
I had to drop so many tables created incorrectly in new wikis:
globaljsonlinks ['arbcom_zhwiki', 'idwikivoyage', 'kncwiki', 'satwiktionary', 'sylwiki', 'tigwiki'] globaljsonlinks_target ['arbcom_zhwiki', 'idwikivoyage', 'kncwiki', 'satwiktionary', 'sylwiki', 'tigwiki'] globaljsonlinks_wiki ['arbcom_zhwiki', 'idwikivoyage', 'kncwiki', 'satwiktionary', 'sylwiki', 'tigwiki'] cn_notice_projects ['idwikivoyage', 'kncwiki', 'satwiktionary', 'sylwiki', 'tigwiki'] api_feature_usage ['arbcom_zhwiki', 'idwikivoyage', 'kncwiki', 'satwiktionary', 'sylwiki', 'tigwiki'] bounce_records ['arbcom_zhwiki', 'idwikivoyage', 'kncwiki', 'satwiktionary', 'sylwiki', 'tigwiki']
Mentioned in SAL (#wikimedia-operations) [2025-02-26T16:19:57Z] <Amir1> dropping incorrectly created tables in new wikis (T352113)