Change #1193403 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@master] Log using a DeferredUpdate in onEmailAuthRequireToken

https://gerrit.wikimedia.org/r/1193403

Change #1193403 had a related patch set uploaded (by STran; author: STran):

[mediawiki/extensions/WikimediaEvents@master] Log using a DeferredUpdate in onEmailAuthRequireToken

https://gerrit.wikimedia.org/r/1193403

This is done!

Slight side note; IMO it might be a good idea to have something similar to WikimediaEvents' OWNERS.md for the new extension, to ensure that the stewardship information for each part of the code is documented/easily accessible :)

In T401939#11214024, @Tgr wrote:

In T401939#11198305, @Jdforrester-WMF wrote:

Could we make it more specific? WikimediaOverrides? WikimediaCustomConfig?

No objections in theory although those sound less specific to me.

In T401939#11198305, @Jdforrester-WMF wrote:

Could we make it more specific? WikimediaOverrides? WikimediaCustomConfig?

What if instead of making a 4th extension (and a 5th place overall for WMF deployed changes) the 3 existing extensions were merged into a single "WikimediaCustomizations" extension?

Big +1 to this end goal. FWIW I do think we could retain git history using sub directories and git remote.

This is merged now and requests are coming through, so I'm calling this particular task Resolved. There remains some confusion on T390657.

Sorry for the confusion here as a result of T399749. I'm not sure merging the pages makes sense, since the audiences are probably slightly different: The Meta page is for immediate help getting back into an account (and is Wikimedia-specific) while the MW page is more about the extension itself.

In T401939#11198304, @Tgr wrote:

Let's go with the more generic WikimediaCustomizations name, and leave it to the future whether WikimediaMessages etc. gets merged. I don't want to block this task on that (there are some relatively urgent motivations for it), and the CI issue seems potentially disruptive.

Let's go with the more generic WikimediaCustomizations name, and leave it to the future whether WikimediaMessages etc. gets merged. I don't want to block this task on that (there are some relatively urgent motivations for it), and the CI issue seems potentially disruptive.

Change #1189245 had a related patch set uploaded (by Mmartorana; author: Mmartorana):

[mediawiki/extensions/WikimediaMessages@master] Add on-page form for EmailAuth recovery requests

https://gerrit.wikimedia.org/r/1189245

In T401939#11184117, @Samwilson wrote:

Is the Wikisource extension the only Wikimedia project-specific extension so far? Splitting by project like that seems like a reasonable way to limit an extension's scope — although of course lots of what's in question here is globally-applicable stuff.

It does sound like a general Wikimedia extension makes lots of sense, better than splitting things into separate Wikimedia* extensions based on implementation detail. It could perhaps become a tempting place to put things that might be better built to be wiki-agnostic (i.e. easier than setting up a new extension), but if the alternative is mediawiki-config then it'd definitely be an improvement.

Is the Wikisource extension the only Wikimedia project-specific extension so far? Splitting by project like that seems like a reasonable way to limit an extension's scope — although of course lots of what's in question here is globally-applicable stuff.

There are btw a bunch of other extensions named WikimediaSomething (WikimediaEditorTasks, WikimediaIncubator, WikimediaBadges, WikimediaApiPortalOAuth, WikimediaCampaignEvents) but I think those are more like normal extensions that provide some self-contained feature without interacting a lot with other extensions, that feature just happens to be something that's probably only of interest to Wikimedia wikis. (Or maybe not? I'm not really familiar with most of them.)

In T401939#11183014, @bd808 wrote:

What if instead of making a 4th extension (and a 5th place overall for WMF deployed changes) the 3 existing extensions were merged into a single "WikimediaCustomizations" extension?

In T401939#11183014, @bd808 wrote:

We have three Wikimedia* extensions that are for adapting other extensions' behavior to Wikimedia policies/expectations/brand/whatever:

What if instead of making a 4th extension (and a 5th place overall for WMF deployed changes) the 3 existing extensions were merged into a single "WikimediaCustomizations" extension? I don't care about the name, but generally the idea would be have one spot to put all the MediaWiki internals changes (message customization, analytics integration, maintenance scripts, miscellaneous hook implementations) and operations/mediawiki-config for LocalSettings.php configuration things.

We have three Wikimedia* extensions that are for adapting other extensions' behavior to Wikimedia policies/expectations/brand/whatever:

https://www.mediawiki.org/wiki/Gerrit/New_repositories/Requests#mediawiki/extensions/WikimediaHooks

Change #1187511 merged by jenkins-bot:

[mediawiki/extensions/WikimediaMessages@master] WikimediaOverrides: Add Special:MyLanguage to meta link in wikimedia-emailauth-login-help

https://gerrit.wikimedia.org/r/1187511

Change #1187511 had a related patch set uploaded (by Reedy; author: Reedy):

[mediawiki/extensions/WikimediaMessages@master] WikimediaOverrides: Add Special:MyLanguage to meta link in wikimedia-emailauth-login-help

https://gerrit.wikimedia.org/r/1187511

T390657: Documentation: Create and link to https://www.mediawiki.org/wiki/Help:Extension:EmailAuth was requesting a link to https://www.mediawiki.org/wiki/Help:Extension:EmailAuth like the non overridden version has... Is this still warranted with the change here?

T399749: Link to Zendesk form from EmailAuth failure message has added a link to https://meta.wikimedia.org/wiki/Help:Account_recovery