Hi everyone, I'm Anaconda developer responsible for the weblate
migration. I'll try to give you some insights.
On Tue, 2020-01-14 at 13:58 +0000, Michal Konecny wrote:
I'm adding Anaconda developer to this discussion, maybe he will
shed
some light on this.
Thanks!
Best regards,
Zlopez
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, January 14, 2020 2:12 PM, Jean-Baptiste Holcroft <
jean-baptiste(a)holcroft.fr> wrote:
> Dear translators,
>
> Anaconda[1] and DNF[2] gave the same answer today:
> "Please can you delay migration and start after February 18? We are
> in
> the middle of RHEL 8.2 localization cycle, our team is working in
> Zanata
> and I want to minimize potential risk. Thanks."
>
> It kinda bothers me a little bit. Please share your thoughts.
>
> First assumption: the answer only concerns Anaconda and DNF
> projects.
>
> 1. Aren't we suppose to be upstream translation community for DNF
> and
> Anaconda? What does the RHEL localization cycle have to do
> here? Why
> March?
That day is a good day related to RHEL localization cycle. The reason
is that we have RHEL and Fedora translations both in one place. That is
helpful for Fedora because translators can use strings created by paid
professionals from RHEL. And they can translate strings to CentOS/RHEL
easily.
Another point of view is because of us developers. It's easier to
migrate RHEL & Fedora translations together instead of part and part.
>
> 2. Fedora 32 schedule says string freeze is supposed to be reached
> at
> end of January [3]
I don't know about priority for migration related to Fedora string
freeze. Do we need to be migrated to Weblate before F32 string freeze?
If yes, then we can break the migration to parts but it would be
slightly more complicated for us (devels).
>
> 3. Whatever external translators are helping RHEL:
> why wouldn't they be able to upload translations using Weblate?
> Same
> if centralized by a Red Hat employee.
> why wouldn't dev team use po merge features?
Translators in RHEL using their tools. One of the benefit is that this
way they can share translations between products. That is not possible
in Weblate as far as I understand.
>
> 4. Migrating to Weblate for a translation team means to have a git
> repository to host translation, which only implies development
> teams
Yes and no. As I said RHEL translators are giving their translations
(at least in Anaconda and DNF) back to community. So we devels are
trying to find the best way to satisfy both worlds.
Adding DNF devel and RHEL translator to this thread.
Best Regards,
Jirka
>
> Anyone with insights or advice on how to handle this?
>
> [1]
https://bugzilla.redhat.com/show_bug.cgi?id=1785028#c9
> [2]
https://bugzilla.redhat.com/show_bug.cgi?id=1787204#c4
> [3]
https://fedoraproject.org/wiki/Releases/32/Schedule
>
>
> trans mailing list -- trans(a)lists.fedoraproject.org
> To unsubscribe send an email to trans-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
>
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org