Key milestones

Be ready for Software Translation Deadline

The second key milestone is the string freeze, ideally, all upstream project will have to use the translation platform by then. Translators need time to translate, going too much beyond the Software String Freeze deadline would prevent correct translation level, and thus, impacting user experience for non english speakers.

Be ready for System Wide Changes proposal deadline

Changing our translation platform is an important change for translators, but the impact on packages is minor. Release can technically be done whatever successfull the migration is. Failing the migration would mean waste of contributor ressources and demotivation.

It requires coordination with:

all upstream maintainer using Zanata will have to migrate,

website team will have to migrate,

documentation team will have to finish i18n support.

As this largely impact our community, visibility is important for teams to coordinate, and the change to be noticed outside of our community.

We'll have to be ready by then. Which mean ask the community to confirm the move, and projects to confirm they understood the new way to interact with the translators and the new translator platform.

Agree on the System Wide Changes proposal

A test phase with pilot projects and translators would be useful, as the philosophy of the translation platform will be really different of what we currently have.

This test phase already happened with some positive feedback about the documentation translation system internationalization.

A GO/NO GO should probably be handled in December.

Key activities

Communicate the reasons of the migration.

Develop the mandatory Fedora specific features

Explain to project maintainers the impact on source management (Zanata uses command line interface to push/pull while Weblate interact with a git repository).

Roll-out of the Fedora websites. Adapt continuous deployment to confirm behaviour on staging. Then deploy on production.

Roll-out of the Fedora documentation. Deploy in production the current staging continuous deployment scripts which are running in staging. Note: it currently uses a demonstration Weblate instance [1].

Roll-out of the Fedora packages. Confirm the git repository to use and connect Weblate to each projects. This doesn't require much upstream contribution (only the branch or branches to use are to be known).

List of projects and status

Why a migration status? Some Zanata projects are tests, other projects can freely decide to decide to change the way they structure their translation or move to any translation platform of their choice.