See T401939: Create a Wikimedia* extension for site customizations for context.
New extensions deployed to production need a WMF team to take ownership of them.
The intent with this extension is to replace WikimediaMessages (unowned), MediaWiki-extensions-WikimediaEvents (owned by Product-Analytics), MediaWiki-extensions-WikimediaMaintenance (unowned) and some code in mediawiki-config (owned by Release-Engineering-Team, maybe?).
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Open | BUG REPORT | Tgr | T397244 Private mitigation blocks registration from certain email domains but gives misleading error about rate limits | ||
| Open | Tgr | T401939 Create a Wikimedia* extension for site customizations | |||
| Open | Tgr | T410515 Deploy WikimediaCustomizations | |||
| Resolved | Tgr | T411727 Determine owner of WikimediaCustomizations extension |
(context: IRC discussion about possible releng ownership)
RelEng cares about mediawiki-config, but we have no knowledge of the other extensions this extension is meant to roll up. RelEng couldn't own this in any sense of "own" that would be useful for folks looking for an owner.
Per team discussion today, MediaWiki-Platform-Team will own the extension as a framework. The individual hooks etc. will be owned by the team that needs them, similar to how it's today for WikimediaEvents with its OWNERS.md file.
Out of interest, should/would WikimediaCustomizations be added to {H425} as a result of this? (If not, should MediaWiki-Platform-Team be added manually to any future tasks that concern the extension as a framework/that might benefit from code steward input?)
Probably should be added to Herald although I don't expect a lot of tasks. @OWresch-WMF @JTweed-WMF what do you think?
(for what it's worth, if WikimediaCustomizations is replacing WikimediaMessages, it might mean that the Phab project might get tagged on a number of tasks that involve (e.g.) adding/modifying/deleting a Wikimedia message override)