Hide Forgot
Hello, the Fedora project migrates its translation platform to Weblate [1]. This tool directly interact with your git repository, and requires us to know: * [mandatory] which branch is your development branch? * [mandatory] have you merged latest translation from Zanata and locked the project? * [info] Weblate will handle updates when pot file changes, don't edit po files for this [2] * [optional] what is the license of translation? (please use a code from https://spdx.org/licenses/) * [optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate) * [optional] do you need us to activate any specific checks? (this is a setting per component [3]) * [optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page) Please note: * For github hosted projects, Weblate open pull request. For other project, you'll have to add a key to allow commits. * In Weblate's vocable, one project is a group of component. Each component is a translation file. You can have many projects or many components or both. * You can change your mind over time, just reach trans@lists.fedoraproject.org [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
Hi, > * [mandatory] which branch is your development branch? We have 3 development branches at this moment: rhel7-branch, rhel8-branch and master. In rhel7-branch we develop code compatible with RHEL7 version of Anaconda, in rhel8-branch we develop code compatible with RHEL8 version of Anaconda and in master we add changes for the latest Anaconda. We need to maintain translations for all 3 branches. Currently in Zanata we have translations for all 3 branches. > * [mandatory] have you merged latest translation from Zanata and locked the project? No, we never merge the translations, we keep only the POT file in our repository. We upload the POT file to Zanata and we download fresh updates from Zanata each time an upstream release is done. [1] > * [optional] what is the license of translation? (please use a code from https://spdx.org/licenses/) I think the translation inherit the project's license, which is GNU GPL v2.0. > * [optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate) No. > * [optional] do you need us to activate any specific checks? (this is a setting per component [3]) No. > * [optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page) No. [1] https://github.com/OpenSCAP/oscap-anaconda-addon/wiki/Release-Guide
I understand, could you please provide a dedicated project the same way the people from Cockpit or DNF or Blivet? https://github.com/cockpit-project/cockpit-weblate
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Hello Jean, here is the empty repository for translations: https://github.com/OpenSCAP/oscap-anaconda-addon-weblate
well, I'm sure you know there is more to do ;) please tell me when and where to find you on IRC. You can find me as jibec on fedora-i18n. But as a contributor, I don't know when we'll have matching agendas. Evening and lunch times are fine for me.