Hello, the Fedora project migrates its translation platform to Weblate .
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 
* [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 )
* [optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page)
* 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 email@example.com
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
The translations repository for dnf-plugins core has been created: https://github.com/rpm-software-management/dnf-plugins-core-l10n. Weblate bot should have been given write access.
why did you create a dedicated repository as you still have po files in https://github.com/rpm-software-management/dnf-plugins-core/tree/master/po ?
configuration is done: https://translate.fedoraproject.org/projects/dnf/dnf-plugins-core-l10n-master/
We need po files to be part of the source tarball for building rpms. Our workflow is now following:
- we regularly synchronize *.pot files in -l10n repo with source codes repo
- weblate automatically pushes translations updates to -l10n repo (we do not want to have all those commits in our git history therefore separate repo)
- before release we sync the translations back to source repo and translations become part of the release