-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
please migrate to the new Fedora translation platform #198
Comments
This repository doesn't use Zanata. The correct repository according to zanata project home page is https://github.com/fedora-selinux/selinux - fedora-selinux/selinux#59 |
Thank you for moving this issue, but I'm unsure what to do here. I know
Fedora mindset is: upstream first.
As this is a dedicated project for fedora, it probably means there is
good reasons for this.
But should we do the same for translations?
To content really looks the same to me:
https://github.com/SELinuxProject/selinux/tree/master/policycoreutils/po
https://github.com/fedora-selinux/selinux/tree/master/policycoreutils/po
If you, as upstream project would like us to host your project, I'll
migrate the Zanata project to Weblate.
If you don't would like to do it, then I'll just ask the Zanata project
to be locked.
If you expect distribution specific selinux projects to have specific
content to translate, we can host both.
What makes sense for you?
|
The problem with translations is that they generate big patches. In Fedora we don't patch the repository directly but we create tarball from downloaded translations from Zanata, and use them during build, see https://src.fedoraproject.org/rpms/policycoreutils/blob/master/f/README.translations Also we split translation in Fedora into subproject to follow the directory and release tarballs structure. In this project, the translations haven't been updated for several releases, there are just minor type fixes. It needs to be reconsidered and this discussion should happen on SELinux mailing list - [email protected]. |
So my suggestion is to migrate fedora-selinux/selinux project (which uses https://fedora.zanata.org/project/view/selinux) first, and then start a discussion about translation in this project on its mailling list |
Yes, this is a common issue for big projects.
I suggest you to follow what other big projects do: a dedicated
translation repository.
From there, either you take the translation and commit it in your repo
or just include it with your releases.
One example: cockpit-project/cockpit#13319
|
@Jibec Is there any advantage in having a dedicated translation repository if we only intend to include the translations with our releases (and not store them in the source repository)? I was thinking of just using weblate client to download the latest translations when we need them (as opposed to having it push updates to a dedicated repository). |
weblate requires to be informed a new version of pot file is available for translation.
either you commit it in your repository and you don't need a dedicated l10n repo, either you create an l10n repo.
if you create an l10n repo, giving write access for weblate is not an issue.
keep it simple, create an l10n repo, it will make everything easier. Newcomers will understand easily how to contribute, and you'll be able yo measure contribution.
please hurry your migration, Zanata will be totally removed in a month.
--
Jean-Baptiste
|
I don't get it. Why we need a new repo when weblate is able to use .pots file from our existing repo and we can download translations from weblate? |
Anyway, this discussion should be in fedora-selinux/selinux#59 |
you have a specific way of organizing your repositories that I don't understand, and you didn't explain how you work. Fedora contribute upstream. If for some reasons, the fork is the only way to do, then we could add both to the translation platform, so that translators contribute both projects (Weblate handles this nicely). Fedora moved to Weblate, Zanata will stop. You want smaller patches? I can remove line numbers in po files, saving a lot in diffs. You don't want translators contribution in your repository and/or your github organization? Note it looks like selinux:
why should each distribution have to translate the same thing? |
#198 (comment) and #198 (comment) are still valid. I'm willing to implement/propose/update/maintain translations in this repository later when it's implemented for fedora-selinux/selinux and when it's clear how it works. |
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
The text was updated successfully, but these errors were encountered: