Translation platform migration to Weblate
This migration was decided at Flock 2019 in Budapest, it is mandatory as development and maintenance of Zanata — the previous translation platform — ceased in 2018. More information are available here: https://communityblog.fedoraproject.org/fedora-localization-platform-migrates-to-weblate/
Link to release process is to make sure the information is spread across all dependent projects, including Documentation and Websites.
- Owner: the L10N group (#fedora-i18n on freenode)
- Primary contact: Jean-Baptiste Holcroft
- Email: localization mailing list
- Targeted release: Fedora 32
- Last updated: 2019-11-07
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Make sure all existing Zanata project have been informed (upstream ticket created) and that all priority packages have migrated.
Benefit to Fedora
First objective is to lower the risk of having no translation platform if Zanata crashes.
Second objective is to provide a suited tool for localization community to be part of our processes again:
- be closer to upstream activity by directly interacting with git repositories
- this also lower upstream requirements to interact with our translation platform (no dependencies required as it interact with git repos)
- this helps upstream to see localization contributions
- this allows translator to get notification when new strings
- be able to localize our documentation (we decided to make it compatible with Weblate directly)
- the tool will publish on Fedora messaging
- allows community statistics
- allows badges creation
- Proposal owners:
Open a ticket for each upstream project.
- Other developers:
answer the message for upstream project and eventually create appropriate git repositories:
- Release engineering: #8947
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
N/A (this change impacts our processes, not our deliverable)
How To Test
For projects using the translation platform: make sure translation commits are part of the release included in Fedora 32.
Example for DNF:
- Open the DNF git repository
- Find folder containing localization file (usually the po folder)
- Look at commit history and search for, commits will start with: "Translated using Weblate" (example with French language on ibus typing booster
N/A (not a System Wide Change)
- Contingency mechanism: Localization team will keep using Zanata
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? Yes, if websites and priority packages do not use the new translation platform.
- Blocks product? Yes