This tag is for requesting code review for extensions to be deployed on Wikimedia wikis. It replaces the tracking task T33235: [DO NOT USE] Extensions awaiting code review to be deployed on Wikimedia wikis (tracking) [superseded by #wikimedia-extension-review-queue]
How to request code review/what is the process for getting a new extension deployed to Wikimedia wikis? See: https://www.mediawiki.org/wiki/Review_queue
Yes, my advice is to treat this as a special purpose (and tiny!) extension /for the special needs of toki pona/ and I'm suggesting the language team as the stewards because they have the language context to understand the specific linguistic task this extension is intended to address. I'm not /opposed/ to CTT owning it (because it is tiny) but it doesn't clearly fit into our team's "content transform" scope. We'll set up a discussion with Language to try to come to agreement.
As I explained at in T397999#11086062, this is not a problem, because the things you are listing are not what the extension exists to address. This extension is not trying to do away with the concept of pages having a single canonical title. It does one specific thing, which is alter the title that is displayed to the reader; there is no need for it change anything else.
solves this problem
I never treat it as a proper solution. As I said in another task, this does not solve what is displayed in category or special page, nor how category is named. Search engines can only index the page in canonical page name too.
I'm boldly tagging Content-Transform-Team & Language and Product Localization on this task for their consideration, as the two teams that (from reading the comments on T397999: Have a way to include wikicode in a redirect that will be displayed at the top of the target page when the redirect is followed) seem (to me) like they might be most likely to be potentially interested in stewarding this extension/helping to get it deployed.
(Sorry to war over parent-subtask relations but I think this is the correct ontology)
I haven't done the work because that page says to get someone willing to provide WMF stewardship before doing anything else. I can own going through the process if I get the go-ahead.
The extension only exists in GitHub, and needs dragging up to date with things like dev tooling etc
You can add task relationships... But https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment
Change #1173926 merged by jenkins-bot:
[operations/mediawiki-config@master] [beta] cswiki: Enable CommunityConfigurationExample
Change #1173925 merged by jenkins-bot:
[operations/mediawiki-config@master] [beta] Add wmgUseCommunityConfigurationExample
Mentioned in SAL (#wikimedia-operations) [2025-08-12T09:49:35Z] <urbanecm@deploy1003> Finished scap sync-world: Backport for [[gerrit:1173924|Add CommunityConfigurationExample to extension-list (T372049)]] (duration: 43m 21s)
Mentioned in SAL (#wikimedia-operations) [2025-08-12T09:06:13Z] <urbanecm@deploy1003> Started scap sync-world: Backport for [[gerrit:1173924|Add CommunityConfigurationExample to extension-list (T372049)]]
Change #1173924 merged by jenkins-bot:
[operations/mediawiki-config@master] Add CommunityConfigurationExample to extension-list
This is now unblocked, as CommunityConfigurationExample has 2+ deployment branches:
Waiting on Aug 05 before this can proceed.
Change #1173926 had a related patch set uploaded (by Urbanecm; author: Urbanecm):
[operations/mediawiki-config@master] [beta] cswiki: Enable CommunityConfigurationExample
Change #1173925 had a related patch set uploaded (by Urbanecm; author: Urbanecm):
[operations/mediawiki-config@master] [beta] Add wmgUseCommunityConfigurationExample
Change #1173924 had a related patch set uploaded (by Urbanecm; author: Urbanecm):
[operations/mediawiki-config@master] Add CommunityConfigurationExample to extension-list
I can confirm the newly-created wmf.12 branch is present in CC example:
Start branching CommunityConfigurationExample