In T25216#3340841, @Verdy_p wrote:

In T25216#3226963, @Liuxinyu970226 wrote:

@Verdy_p:

It would be simpler to first create a CNAME alias redirection of the subdomain

Are you absolutely sure that non of our Wikimedians have knowledge of Narom?

Currently no, given that the expected users that would use it, i.e. native Narom users, are simply blocked from using Wikimedia in their language. And all others seem to assume (incorrectly) that nrm refers to Norman (a large majority of them also don't know what is Norman).
So the current issue does not serve any one, not those Norman and Narom users or none of other users which have some knowledge or expertise of either languages.
The "nrm" code is bad for everyone.

"native Narom users, are simply blocked from using Wikimedia in their language" Malaysia has GFW? For other sentences, I need time to research.
But even the Norman language is also not having a good status (per Ethnologue: Jèrriais language status: 8a (Moribund), while Guernsey status: 8b (Nearly extinct), although in "Mainland" France status: 6a (Vigorous)).

I only suggested creating a CNAME domain name alias as a helper for a transition period (that should not exceed one year). During that time we'll fix all the remaining items using "nrm" to replace them with "nrf". Bots can also help fixing various things, including in interwiki links found in pages or in Wikidata. The rest is only fixing a few templates manually. Then some consilidation to check if there are remaining items.
Wikimedia can monitor the usage of links using the old "nrm" subdomain in interwikis (it can monitor referers, get some statistics over a monthly period, and maintain a list of what has been found). Bots can also help fixing translations found in Wiktionnary using incorrect codes.

Due to T133548, do you still believe that redirects that even only about CNAMEs are easy? Changing href of "nrm:" Interwiki links are also not easy, see https://gerrit.wikimedia.org/r/#/c/236966/ .

Some templates will need some temporary fixes to support the transition, these may be complex in some tricky templates (or modules) but there should not be a lot.

Just change them to query either Q33850, or when possible, the CLDR nrf locale name entry.

Another task to perform will be to use a bot to rename codes in User babel boxes, after the Babel templates have been fixed (if needed to support both codes with "nrf" becoming the prefered default form).

For those who are using {{#babel:nrm}}, T101086, then just wait for the patch that T25216#3337767 mentioned to be merged (or are you asking that we must also add nrm to $wgDummyLanguageCodes?). Local Babel templates can just be editable by you!

A final monitoring should look for remaining accesses (webserver access logs) to see if they are refered from Wikimedia sites or some wellknown sites (including translatewiki.net) that could be fixed to use the new domain name. We can ignore small external websites (personal pages or blogs). But we can contact maintainers of wellknown community pages on social networks (Facebook, Twitter,...) to inform them of the new site to use.

+1

The old "nrm" wikis being accessible from "nrf" could also display a notice on their home page about the transition. Users registered on "nrm" and having some admin privileges shoudl also be informed by a notification to their talk page.

Just mention this task in Tech news (User-notice) is already enough (I really don't know why it's important that a MassMessage is needed for this single task).

After that time, we can discard the "nrm" aliases in CNAME domain names and start removing the old "nrm" aliases kept in templates/modules but keep "nrf" there.

See a.2, not very easy.

Note that translatewiki.net is about to rename "nrm" to "nrf": wikimedia will need to change the translation source for its "nrm" wikis.

Yes, TWN should rename codes that i18n files are using first.

This should also be announced in community portals of international wikis (Commons, Wikidata, Meta) where their local admins will take in charge the conversion of templates/modules (first the compatiblity transition by making "nrm" an alias of "nrf" now prefered, then later the removal of the old aliases).

a.6, and what else should be renamed? In ContentTranslation? (maybe T112285, T129470) "nrm XXXX" part of Wikidata items links? (T112647) pywikibot.Link? (T113461 or ask zhuyifei1999 if more help needed) SiteMatrix? (a bit hard, see T111876 and T134348, maybe several decades later as per a.2)

At that point "nrm" will be useless and can be cleared. Narom suers can then request the addition of "nrm" for their language. A new wiki will be created for them, the new wiki will start with a homepage saying that the Norman wikis have been moved elsewhere. After about one year, that notice will be droppable.

Changing 'nrm' => 'Nouormand', # Norman -- not a valid code, for compatibility. See nrf. to 'nrm' => 'Narom', # Was assigned to Norman for compatibility in early years, See nrf. isn't enough?