In T180771#7228271, @Esc3300 wrote:

Seems to be live, at least nan-hani

@Amire80 @jhsoby @Esc3300 @Nikki Could you please reach an agreement on what the desired language code is going to be? I'll make a new patch then.

In T155419#7195690, @Amire80 wrote:

I think the discussion here becomes more complex than it should be. How many labels do we actually expect to have here? If we just start with "mix", and then we get a lot of them, can they be later divided by someone who understands these languages well?

In T286031#7220116, @Esc3300 wrote:

@Mbch331 can you review the patch?

@Amire80 @jhsoby Now we have en-us, is this acceptable too?

In T286862#7219730, @Aklapper wrote:

@Bugreporter: Add where? Which codebase is this about?

In T286031#7193481, @Esc3300 wrote:

It's actually missing in LocalNamesEn which probably explains why we get the Spanish version.

@Amire80 What's your view on this?

In T215032#7200368, @Amire80 wrote:

@Mbch331, I see mvf in the code of WikibaseLexeme, but I cannot actually add lexemes in it. And I don't see it in the code of Wikibase at all. Can you add it please?

@Amire80 @jhsoby What's your view on this?

In T70207#7195691, @Esc3300 wrote:

I'd close this (as incomplete or invalid), it seems to be a pre-phabricator request and https://en.wikipedia.org/wiki/User:Geekemad doesn't exist.

In T180771#7191533, @Addshore wrote:

As the current Wikidata-Campsite (Wikidata-Campsite-Iteration-∞) unstaller, what is this task stalled on?

This is blocked on LangCom approval for the remaining languages.

In T284808#7183772, @Lydia_Pintscher wrote:

Don't we already have this? I don't think we allow adding terms for simple for example? Or am I missing something?

@Esc3300 My patch was denied for 2 reasons:

1. I used da instead of nl (which has been fixed)
2. There is not enough proof of consensus in this task (this is something I can't fix.

Added missing translations. Language codes that are present in CLDR need to be updated upstream, language codes not present in CLDR can be added to LocalNamesNl.php

Since there is only approval for mix in case of Mixtepec Mixtec and no approval for mix-und, this isn't ready to go. Still needs LangCom approval. @jhsoby @Amire80 is mix-und a good alternative for this case where it's unknown which form of Mixtec is used?

In T262922#7178793, @Bouzinac wrote:

Another wonder : monolingual language code does not necessarily mean there would be a new line "gsw-fr" as labels for items, does it?

No. It's only available for monolingual properties. Labels/aliases/descriptions aren't properties and thus not supported. If it's needed, a new ticket is needed for that.

In T215032#7167462, @Popolon wrote:

Which kind of sample do you want.

As an exemplle, from :
https://fr.wikipedia.org/wiki/Mongol_bitchig

{{lang|cmg-Mon|ᠮᠣᠩᠭᠣᠯ ᠪᠢᠴᠢᠭ}} this is the name of the Mongolian script in classical and modern Mongolian.

In T245927#7164813, @Esc3300 wrote:

I updated the task for LocalNamesRu.php and added the usual one week for patches as due dates. It may still be fixed/communicated to CLDR as well.

In T157809#7164833, @Esc3300 wrote:

seems to be ready to go. I add the usual one week for patches as "due date".

In T285076#7164682, @Esc3300 wrote:

If I understand correctly, T162406 is about CLDR. Ideally, all these changes should eventually be in upstream CLDR and not in local MediaWiki code.

It's about LocalNamesSco.php only.

Ideally these changes should be added to Cldr

@jhsoby @Amire80: What do you say?

In T284276#7160260, @Esc3300 wrote:

In T280774#7153111, @Esc3300 wrote:

Can we add it to the Wikidata's sitewide css?

In T262922#7153044, @Esc3300 wrote:

@Mbch331 Thanks. Would you add the language names as well (see description) or is this already done?

Language name is correct in CLDR (in LocalNamesEn.php).

Not used for Lexemes, but added as a monolingual language code. Will remove it there.

Since this was created by a langcom member, I assume this can be considered as approved by LangCom

@jhsoby @Amire80 What do you say?

Looks like the language dropdown is using ULS and not the monolingual language dropdowns from Wikidata. So this is more for the SDC team and not for the Language codes team.

I think the list of disallowed languages can be something like:

In T44396#7150835, @Esc3300 wrote:

Is there a blacklist feature or would that need to be created?

! In T44396#7150849, @Esc3300 wrote:

@Mbch331 what do you think?

In T157809#7150763, @Esc3300 wrote:

LocalNames/LocalNamesDa.php hasn't been created yet

In T212313#7150692, @Esc3300 wrote:

In T212313#6611768, @Nirmos wrote:

What system message would be different in Indian English compared to British English?

Can we have en-in for labels/descriptions without having it as an interface language?

In T284276#7148337, @Esc3300 wrote:

Well, test is after deployment (i.e. ensure it actually works). Ideally this is done by the person who requested the new code.

In T284276#7148299, @Esc3300 wrote:

Which steps can run parallel ?

I think there are two possibilities:

• steps that can't technically done in parallel
• steps that can technically be done in parallel

For the later, there may be reasons to do them before or after some step. Obviously, it doesn't mean they have to be done in parallel.

Current estimate for the entire process seems to be 5 weeks (if you are available). This seems a lot for a somewhat basic task even for the volunteer part of our organization.

Which steps can run parallel ?

First langcom approval is needed, than a patch can be made

I've used Wyandot as the name of the language in English, since that's what most sources use.

In T284276#7133623, @Esc3300 wrote:

I noticed that the quickest step usually is Mbc331 .

• As creation of these codes is a basic Wikidata maintenance step, I suppose we should also plan for when Mbc331 isn't available and it has to be done by WMDE.

If I'm not around, any other volunteer coder can do this. These are quite simple changes.

• For code review, I added a few open ones I found into "Wikidata (consider for next sprint)". Is this the correct place or should be in "Wikidata (in progress)" ?

If there is actually a patch, Wikidata-Campsite (Wikidata-Campsite-Iteration-∞) is the correct tag and peer review is the correct status.

Coding done by volunteer -> 1 week after langcom approval (should be shorter, but depends on when the volunteer (usually mee) has time). (Doesn't matter which of the three it is.)
Coding done by WMDE: Don't know if they want to spend "expensive" paid resources when it can easily be done by a volunteer
code review: usually done within 1 week after delivery of the code
After code review the deployment is with the next train (code deployment)
Lydia review nowadays not needed as long as there is langcom approval. @Amire80 / @jhsoby can comment on the langcom approval part.
Maybe @Lydia_Pintscher has something to say about the WMDE side (if my assumptions are correct and maybe I missed something)

In T265297#7131893, @Esc3300 wrote:

I doubt they have much of a view on this. The initial request seems to be concerned primarily with "osa-latn", maybe we could just do that.

In T265468#7131765, @Esc3300 wrote:

@Mbch331 are you interested in doing this one?

In T265297#6984108, @Linguoboy wrote:

That's a fair assessment based on what I've seen and this seems like a fine solution to me. If you'd like, I'm willing to contact the Osage Nation to get their input.

@jhsoby @Amire80 Is this a go/no-go or do you want to follow the track laid out by @Jdforrester-WMF?

@jhsoby @Amire80: What's the verdict?

@Manuel: Any examples yet? @Amire80: Is cdo-hani ok as well, or do you still want to wait?

In T282512#7080302, @Mahir256 wrote:

In T282512#7076823, @Amire80 wrote:

OK, and mvf is OK, too. Is there such a task for mvf? I thought it's added already.

For a reminder of the controversies involving a code for Mongolian in its native script, see T215032 and (described as having a negative effect on one participant) T137810.

@Amire80: Still ok with mvf?

@jhsoby @Amire80 What do you say?

A lot of deleted items/Lexemes still appear in the triple store:
Q106520057
Q106680490
Q106687398
Q106532286
Q106532522
Q106533307
Q106549635
Q106705896
Q106734065
Q106915489
L480205
Q106644086
(Probably more, but these are the ones my bot finds, because there would be a constraint violation for P2397)

I'll make a patch to add the correct language to LocalNamesSv.php

@jhsoby / @Lea_Lacroix_WMDE Can you confirm that Pashto is the official Swedish name for the language and not just the preference for Swedish Wikidata users?