Note that @bearND and @Niedzielski from the (Android) Apps team already have access

@Nemo_bis You can remove my access if that's a concern.

@Nemo_bis correct. @Niedzielski is currently helping us by running import/exports manually. I'd like to not only take some of of the load off his shoulders, but also make sure the iOS team has the knowledge & permissions to manage both the TWN configuration and running the imports & exports. Up until now, localizations—specifically TWN sync—has been a bit of a mystery to our team, leading to confusion and resistance to change. My goal is to "solve" the mystery by empowering our team to do the updates and manage our configuration.

Will @Niedzielski give you a tutorial how it works or do you need that from us?

@Nikerabbit yes, I paired with @Niedzielski as he did both the Android & iOS updates, and we updated the TWN sync docs for iOS, including the addition of a link to the configuration file in the repo. My hope is that we can write one (or two) scripts and commit them to the iOS repo to automate the workflow (since we have a couple add'l steps aside from the translatewiki repo commands).

In either case, the goal is to be as autonomous as possible, only pinging you guys when we run into infrastructure-related issues, or guidance for interacting with the translator community.

I'm in!

ssh translatewiki.net
bgerstle@translatewiki:~$ echo "Hello world!"
Hello world!

I just wanted to make sure you know how to avoid stepping on anyone's toes as there are potential race conditions.

Ah, are there any guidelines I should read?

Not really. https://translatewiki.net/wiki/Repository_management has some info but looks partially outdated or incomplete.

The big thing is that processMessageChanges.php -> Special:ManageMessageGroups workflow can only handle one user at a time. So before doing imports better check that nobody else is doing that at the same time.