Open bachradsusi opened 4 years ago
I asked questions to upstream in SELinuxProject/selinux#198 Please share your thoughts, as I don't know how your projects are organized, I don't know what to do.
[mandatory] which branch is your development branch?
This project follows branching in Fedora dist-git - master for Rawhide, f32 for Fedor 32, ...
Also Zanata project has 7 different versions - master, rhel-8, rhel-7, ...
[mandatory] have you merged latest translation from Zanata and locked the project?
We don't merge translations from Zanata to this repository. We pack translations as astgz files which are used in src.rpm.
[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 and gitlab hosted projects, Weblate open pull request. For other git hosting, you'll have to add a key to allow commits.
As said above, we don't merge translations into this repository, and we are not going create a new one just for translations. weblate should ba able to provide translation directly for download
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.
There are 4 different components/pot files in this project, see https://fedora.zanata.org/iteration/view/selinux/master/documents?dswid=6471
@Jibec we want configuration as simple as possible. Just a project with 4 components. Even though we track pot files in the repository we will update translation sources manually as we do it now in Zanata. And we will download translations during release process directly from weblate - no intermediate repo, no write access to our repository. We would do it on our own but we are not allowed to create a new project in translation.fedoraproject.org.
instead of saving a few pot files in your repository and letting github/weblate do all the automation work, you want to work manually?
fine, your project was created and you are admin: https://translate.fedoraproject.org/projects/fedora-selinux/
Thanks.
I've migrated master version to weblate https://translate.fedoraproject.org/projects/selinux/ and marked https://fedora.zanata.org/project/view/selinux read only.
@Jibec Is there a way how to migrate other Zanata versions rhel-8 and rhel7 to weblate? Or do we have to track it on our own somewhere else?
I suggest to have:
gui-master gui-rhel7 gui-rhel8
It will take a few minutes for you to configure, but Weblate will automatically propagate translators' work.
But if it is named fedora-selinux, it's weird to have rhel branches :p
It work for like that for Cockpit: https://translate.fedoraproject.org/projects/cockpit/
From https://github.com/SELinuxProject/selinux/issues/198 :
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
Concerned project: https://fedora.zanata.org/project/view/selinux
Reported by @Jibec