Note: This would be the very first Wikimedia language project where the Wikipedia is not the first project to be created. Could there be any unforeseen consequences to that (if we knew, they wouldn't be unforeseen, but you know what I mean)?

@Aklapper Why that change in task relations?

Yes, per Amir's comments adding it with the code ccp (withotu script identifier) is fine.

Thanks for creating this, @fdans!

In T237375#5635188, @Michael wrote:

This is unrelated to Wikidata Bridge, which is a feature still in early development.

For the record, I'm fine with adding these. However I believe the correct language code for Kalinago is crb – car is a different, though related, living language spoken in mainland South American countries, while crb was spoken in Caribbean islands just like Taíno.

OK from LangCom.

As long as it's not an official ISO 639-3 code, this will be declined. Feel free to re-open if the application to the SIL is successful.

I think it makes sense, but would like to hear what @Amire80 says as well. :-)

I was sitting next to @Lucas_Werkmeister_WMDE right now, and he told me that we can use the same solution that is used for the plurals of English octopus, which is to add the different spellings as new forms with the same grammatical categories. However, this feel very counter-intuitive to me: I feel like the different spelling variants are what should have different forms, and then the various spellings in the same spelling variant should go together in the same form.

The standard for country-based community user groups (and chapters) is to use contrycode.wikimedia.org.

I believe this is all done now.

In T235739#5587205, @Urbanecm wrote:

@jhsoby Do you plan to do the DNS thingie too? See https://wikitech.wikimedia.org/wiki/Add_a_wiki#DNS for details.

Though it is resolved, this task is still linked from [[Special:Userlogin]] when you get an "incorrect password" error message, which I'm getting a lot (see T229227#5585969).

In T235739#5585502, @Dcljr wrote:

Just a heads-up: The last wiki created, banwiki, has had issues with imported pages not showing up in categories. A null edit fixes the problem for each affected page. This seems to suggest that importing was done before the wiki was properly configured to recognize the local prefix "Kategori:" as equivalent to "Category:". If this is the case, we should be careful to prevent this from happening again with mnwwiki (and in the future).

I'm getting the same error as well. Wikitech automatically logs me out annoyingly often (like after 1 or 2 days), even though I always check the "remember me" option. Every time I try to log in, it says my password is invalid, and I have to reset it.

In T235739#5584266, @Ninjastrikers wrote:

Project talk namespace should be ဝဳကဳပဳဒဳယာ_ဓရီုကျာ

@KartikMistry With the above patches merged, can this be closed, or is there something that remains to be done?

There have been no objections in more than a month, so I think this is good to go. I'll add it to the European mid-day SWAT.

In T174601#5579618, @Nikerabbit wrote:

I don't like the idea of "figure out later". It just piles more unplanned work on us (or worse, mess is left behind). Let's make a proper plan and get it resourced.

I was chatting with @Nikerabbit and @Raymond about this yesterday in #mediawiki-i18n. My proposed action plan in order to move this language from ais to szy is as follows:

1. Disable translations into ais.
2. Enable translation into szy.
3. Move all existing /ais messages on Translatewiki to /szy by bot.
   1. This will duplicate everything to szy.json files, but will have no effect on the ais.json files. As Niklas mentioned, this will lead to the content from ais.json files being imported back into Translatewiki from the still-existing ais.json files. However, if translating into ais is disabled on Translatewiki, I don't think this will be a significant problem (and it shouldn't be a blocker). Yes, there will exist duplicate pages, but they can't really be changed (perhaps by editing by hand, but not via Special:Translate), so there is no real danger of conflicting edits.
4. Then figure out what and how to do anything with the ais.json files.

The most important thing here is to get the szy.json files up and running, so I think this should suffice as first steps.