You can add task relationships... But https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment

The extension only exists in GitHub, and needs dragging up to date with things like dev tooling etc

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.

(Sorry to war over parent-subtask relations but I think this is the correct ontology)

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.

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.

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.

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.

@Tbodt judging by the (now-reversed) addition of T404457 as a parent task to this; to clarify, do you think that this extension should/needs to be approved prior to the wiki being created? /genq

I thought so, since the pages that use it would be broken otherwise. But it sounds like this is more of a task for between creating the wiki and opening it (like importing pages?)

I think it can be done after setting up the wiki? All that'll break without it enabled is that __NIMI_SULI_O_AWEN__ will parse as plaintext rather than a magic word, which is a little annoying but not a huge deal.

Hm, theoretically, but now I'm worried about this task getting stuck for an indefinite period of time and having to live with the regression. Ideally I'd like to at least get the commitment to host the extension before we create the wiki to avoid that.

I agree that that would be nice to get a commitment now (and will ping @cscott to ask if there's been any movement on that front), but in either case, this is not a blocker because the wiki will still work without this being resolved.

It's time?!

See https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment for requirements.

In T404461#11411552, @Aklapper wrote:

See https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment for requirements.

Expanding on this: it would be good to have https://github.com/tbodt/mediawiki-MultiTitle moved to gerrit, and a README.md written for the repository. The checklist also includes the process to getting the extension supported by translatewiki. I note that the i18n/ directory does not have a tok.json although MultiTitle.i18n.magic.php includes an entry for tok.

I'd also recommend that the magic words in MultiTitle.i18n.magic.php be made case-sensitive (first entry in the array 1 rather than 0); cf T389029: Case-insensitive parser functions/magic words should be deprecated.

Basically, despite the checklist saying "get a WMF steward first", I think there's a little bit of work needed first. When you get to https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Preparing_for_deployment Content-Transform-Team is willing to give reviews and otherwise facilitate.

EDIT: I'd like to clarify that I'm speaking in my individual capacity here: *I* looked at the checklist and I found a number of things mentioned in the checklist that could be done and would, in my personal opinion, make it easier to advocate for official adoption of the extension, and *I* am willing to provide reviews and otherwise try to facilitate a meeting of those responsible at WMF to formally endorse.

In T404461#11424175, @cscott wrote:

In T404461#11411552, @Aklapper wrote:

See https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment for requirements.

Expanding on this: it would be good to have https://github.com/tbodt/mediawiki-MultiTitle moved to gerrit, and a README.md written for the repository. The checklist also includes the process to getting the extension supported by translatewiki. I note that the i18n/ directory does not have a tok.json although MultiTitle.i18n.magic.php includes an entry for tok.

I'd also recommend that the magic words in MultiTitle.i18n.magic.php be made case-sensitive (first entry in the array 1 rather than 0); cf T389029: Case-insensitive parser functions/magic words should be deprecated.

Basically, despite the checklist saying "get a WMF steward first", I think there's a little bit of work needed first. When you get to https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Preparing_for_deployment Content-Transform-Team is willing to give reviews and otherwise facilitate.

All of this is done now. Will create another task to get it enabled on translatewiki.net

https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Preparing_for_deployment says:

1. Create a production deployment tracking task within Phabricator (in the Wikimedia-Extension-setup and Wikimedia-extension-review-queue projects) to get an extension into the review queue. This task should only concern deployment itself. Any issues which block deployment should be separate subtasks (listed under "Task Graph") that block this parent task.
2. Your deployment tracking bug should point to on-wiki community consensus (and/or community support/desire) for having the extension installed on a particular wiki, if applicable.
3. Request and incorporate feedback from the following reviews. These can be included as a "checklist" within the production deployment tracking task's description, (e.g. phab:T190716) or as substasks of the production deployment tracking task. Also note that not every review listed below is a hard requirement for production deployment and that there is no specific order of reviews which need be followed.

Is this task going to be that "production deployment tracking task"? If so, perhaps you could edit the task description to include a checklist such as that described on mediawiki so we can keep track of progress and what still needs to be done. (Otherwise you could open another task to be the tracking task.)

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

[integration/config@master] zuul: Enable basic CI for MultiTitle extension

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

Change #1214548 merged by jenkins-bot:

[integration/config@master] zuul: Enable basic CI for MultiTitle extension

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

In T404461#11428904, @cscott wrote:

Is this task going to be that "production deployment tracking task"? If so, perhaps you could edit the task description to include a checklist such as that described on mediawiki so we can keep track of progress and what still needs to be done. (Otherwise you could open another task to be the tracking task.)

Added the checklist. Does this look like the right set of items?

Mentioned in SAL (#wikimedia-releng) [2025-12-03T16:50:24Z] <Reedy> Reloading Zuul to deploy https://gerrit.wikimedia.org/r/1214575 T404461

https://doc.wikimedia.org/cover-extensions/MultiTitle/Hooks.php.html

93.33% and 14/15 lines is pretty good.

Security review passed, going to send CLs to enable extension in beta cluster.

Change #1224780 had a related patch set uploaded (by Tbodt; author: Tbodt):

[mediawiki/extensions@master] Register MultiTitle

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

Change #1224782 had a related patch set uploaded (by Tbodt; author: Tbodt):

[integration/config@master] zuul: [mediawiki/extensions/MultiTitle] Promote to Wikimedia prod section

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

Change #1224793 had a related patch set uploaded (by Tbodt; author: Tbodt):

[operations/mediawiki-config@master] Add MultiTitle to extension list

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

Change #1224795 had a related patch set uploaded (by Tbodt; author: Tbodt):

[operations/mediawiki-config@master] Enable MultiTitle on beta cluster testwiki

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

Change #1224796 had a related patch set uploaded (by Tbodt; author: Tbodt):

[operations/mediawiki-config@master] Load MultiTitle on beta cluster

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

Change #1224794 had a related patch set uploaded (by Tbodt; author: Tbodt):

[operations/mediawiki-config@master] Add config variable for MultiTitle

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

tbodt opened https://gitlab.wikimedia.org/repos/releng/release/-/merge_requests/231

make-release: Start branching MultiTitle

Change #1224780 abandoned by Tbodt:

[mediawiki/extensions@master] Register MultiTitle

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

Change #1224782 merged by jenkins-bot:

[integration/config@master] zuul: [mediawiki/extensions/MultiTitle] Promote to Wikimedia prod section

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

thcipriani merged https://gitlab.wikimedia.org/repos/releng/release/-/merge_requests/231

make-release: Start branching MultiTitle