Transtats

In a software release cycle, localization steps like...

• extracting or updating language resources,
• pushing them to translation platform,
• pulling and packaging translations,
• translation quality and other checks etc.

seem necessary but sometimes they lack attention which results in delay.

Translation is the most fundamental in localization process and tracking its progress seems quite helpful in overall success. Looking at this more generically, translation process is distributed and at times lies with community. Whereas in-house/outsourced translation is more requirement driven. In simple words its difficult to say where translation is happening upstream vs downstream, which may introduce some redundancy (in cost, may be).

Basically an answer to following:

• Trends for language translation across packages. Irrespective of where their translations are hosted.
• Translation and i18n QA workload estimation for approaching release.
• A basis to l10n/i18n automation of a few steps, may be.
• A method to streamline translation process, upstream vs downstream.

Idea is if we can have translation status of the package for downstream (example: Fedora releases) with respect to current development. Transtats is an attempt to tie up loose ends and then, may be automate some of the steps. Concept is based on syncing with translation platform for statistics (How progress is going?), comparing stats with release streams (Is latest translations packaged?), managing translation differences (What piece of translation cause an error or left to get translated or ..?), keep upstream updated (May be update upstream with translations?) and create notifications (Based on release dates: to Developers, Quality Engineers and Managers?).

The solution is based on creation of mapping between translation platform, releases and upstream.

Keep reading docs to dive deep! If you like the idea and have some points to add/discuss please create GitHub issues.