automatically merge updated translations from Transifex when producing master builds

[Be]

This is currently a manual process that is done sporadically. It would be nice if no one had to worry about it.

[Sébastien BLAISOT (sblaisot)]

well, the discussion was not to automatically merge the translations to git repo, but to merge translations in jenkins workplace on every build.

I don't think we should automatically merge translations into git without human control but ship master builds with updated translations seems ok.

[Sébastien BLAISOT (sblaisot)]

I mean workspace, not workplace ;)

[Sébastien BLAISOT (sblaisot)]

My plan for this is :
- Automatically update interface and installer translations from transifex before build for CI builds (appveyor and travis-ci)
- Automatically update interface and installer translations before nightly builds on jenkins
- DO NOT update automatically translations before release builds (release branch, 2.1 for example). For release, we want a stable translation (not necessarily the last available) manually validated and pushed into git.

Are everybody ok with this plan ?

[jus (jus)]

Im fine with that.

But we have to make sure the latest translation is the most stable, there is no versioning on Transifex.

How should the manual check be done?

I propose the following path:
* Perform quality checks on existing files once. Now. Basically to check where we are. This can be automated. Possible checks are for *Text, Segment, File verification, *Length, *Inline Codes, *Patterns, *Characters

* Output results to html (for readability). Post link to results as announcement on Transifex. A link to the announcement is automatically emailed to all our translators.

* Make it clear that we need to check the quality of the translation, as well as to review existing translations. Once a translation is approved, change translated strings is restricted. This protects against accidental/inconsistent change, as well as vandalism (which rarely occurs)

* Review translations, approval of strings, and change of approved strings can be done by admins, team managers, and & reviewers. Since the first member of a language translation team is automatically the team manager (who might be even active anymore), we have to call for additional reviewers. As of today, only a few reviewers are active (e.g. Cz with 90%+ approval).

* Merge language translation teams. Currently there are different teams for website, manual, and application/installer. This is for historical reasons, we started with two-letter ISO codes for Locales (e.g. fr refers to French) in the app & manual, only to later use four-letter ISO codes (e.g. fr_CA refers to Canadian French) in the website & installer. To solve this, manually clean up the teams, and use four-letter ISO codes wherever possible.

* Post 2.1 goal should be to have one team, where a member can translate all resources of the Mixxx project.

If we are able to reduce the number of unapproved strings, then nothing speaks against automating the merge to the release branch too.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8966