Hello, the Fedora project migrates its translation platform to Weblate [1].
This tool directly interact with your git repository, and requires us to know:
Please note:
[1] https://communityblog.fedoraproject.org/fedora-localization-platform-migrates-to-weblate/ [2] https://docs.weblate.org/en/latest/admin/continuous.html#avoiding-merge-conflicts [3] https://docs.weblate.org/en/latest/user/checks.html#translation-checks
kind reminder, zanata removal is coming in a few weeks: https://fedoraproject.org/wiki/Changes/Zanata_removal
Sure, please provide the following information for the migration to the new Fedora translation platform. screen mirroring netflix
Development Branch (Git repository's development branch): Merged Latest Translations from Zanata and Project Lock (Yes/No): Translation License (if applicable, provide SPDX code from https://spdx.org/licenses/): Announcements/Warnings for Translators (if any): Specific Checks to Activate (if any): Automatic Detection of New Translation Files (Yes/No):
@smash karts, Hi! The Fedora project has migrated to the Weblate translation platform. Please confirm your development branch and whether you have merged the latest translation from Zanata. Thanks!
Thanks for the detailed update on migrating Fedora translations to Weblate. The clarification around branches, Zanata locking, and how Weblate handles POT/PO updates is especially helpful for project maintainers planning the move. Clear communication like this really reduces friction for contributors and translators. In a completely different space, we’ve seen similar benefits from streamlined platforms in other fields too—whether it’s software localization or even coordinating something like a Pool cleaning service Abu Dhabi, having the right tools and clear processes makes collaboration much smoother for everyone involved.