Fwd: Re: DNF and Anaconda ask to delay Zanata migration in March

Somehow, this message isn't available in translation mailing list 
history. People can't read the message I'm answering to. Here is a 
forward for archive purpose.


-------- Message transféré --------
Sujet : 	Re: DNF and Anaconda ask to delay Zanata migration in March
Date : 	Mon, 20 Jan 2020 04:37:33 +0100
De : 	Luděk Janda <[email protected]>
Pour : 	Jean-Baptiste <[email protected]>
Copie à : 	[email protected], Fedora Translation Project List 
<[email protected]>, Matej Marusak <[email protected]>, 
[email protected], Michal Konecny <[email protected]>, 
[email protected] <[email protected]>



Hi Jean-Baptiste,

I think I answered already on 15 February. My copy pasted answer from 
that day follows. Let me know if you need anything else you need to 
clarify from me.  Thanks, L

Hi all,

> On 15 Jan 2020, at 08:19, Matej Marusak <[email protected] 
> <mailto:[email protected]>> wrote:
>
>
>
> On Tue, Jan 14, 2020 at 9:45 PM Jean-Baptiste 
> <[email protected] <mailto:[email protected]>> wrote:
>
>     Le 14/01/2020 à 16:25, [email protected]
>     <mailto:[email protected]> a écrit :
>     > 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.
>
>     I feel that this assumption is wrong, or requires more details.
>

That’s just a small misunderstanding. We prefer to translate in our 
internal platform because this way we can share RHEL UI translation 
memory with other projects such as RHEL documentation, our translators 
working on docs can easily verify the appropriate UI strings translation 
when necessary. We can also leverage easier our past translations from 
other projects / other RHEL components. I do not have numbers for 
Weblate, but comparing Zanata with our internal platform - when sharing 
TM in our internal platform we are to reduce workload by ~20% (e.g. 
Cockpit in Korean, Zanata workload: 1107, Memsource workload: 802). We 
also have access to our MT engines (DeepL) that speed up delivery. Etc.

>     Anyway, it looks like Ludek Janda was able to import a list of files
>     easily: https://translate.stg.fedoraproject.org/changes/?user=ljanda
>
> Hey all,
> I would like to mention our experience with this migration. (not the 
> migration itself, that is a long story as we did not like the "common" 
> weblate workflow)
> I migrated 3 Cockpit projects from Zanata to Weblate last week not 
> realizing that there is a translation phase going on.
> Yesterday Ludek pushed updates into Zanata. So I talked to him and 
> learned that they don't use Zanata as translation platform - they just 
> pull source file from it and push translated files there.
> Although I agreed that they can finish this phase in Zanata and then I 
> would do a manual sync into Weblate, Ludek tried Weblate and said it 
> was easy to push there, so he did exactly that.
>
> So yes, he was able to do that, but it is important not to break their 
> workflow in the middle of a translation phase. But after he tried 
> Weblate yesterday, maybe he would be willing to do this also for other 
> projects?

Yeah, it was surprisingly easy, thanks, Matej, for giving me that 
opportunity. Challenging part seems to be the GA check. I will need to 
align our internal QA tools to highlight the same errors as in Weblate.

Because Cockpit and Composer already moved to weblate, we can definitely 
finish our translations there.

But in general I would really prefer to have RHEL 8.2 translation cycle 
finished first (18 February) and migrate after that.

The list of affected components (with some translation work in 8.2)

  * anaconda
  * cockpit
  * composer
  * dnf
  * dnf-plugins-core
  * libdnf
  * NetworkManager
  * policycoreutils
  * pykickstart
  * setroubleshoot-plugins
  * sssd
  * subscription-manager
  * syspurpose


Thanks, Ludek


> On 17.01.2020, at 19:23, Jean-Baptiste <[email protected] 
> <mailto:[email protected]>> wrote:
>
> Ludek, as RHEL Localization Manager and the one asking to DNF and 
> Anaconda to delay migration, could you please answer the different emails?
>
>
> I see no reasons to delay, and ask you the help us in this migration 
> by being an enabler: telling all Red Hat teams to fully support this 
> community effort.
>
>
> Added in CC, Mairin as FCAIC.
>
>
> Le 15/01/2020 à 08:19, Matej Marusak a écrit :
>>
>>
>> On Tue, Jan 14, 2020 at 9:45 PM Jean-Baptiste 
>> <[email protected] <mailto:[email protected]> 
>> <mailto:[email protected]>> wrote:
>>
>>    Le 14/01/2020 à 16:25, [email protected] 
>> <mailto:[email protected]>
>>    <mailto:[email protected]> a écrit :
>>    > 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.
>>
>>    I feel that this assumption is wrong, or requires more details.
>>
>>    Anyway, it looks like Ludek Janda was able to import a list of files
>>    easily: https://translate.stg.fedoraproject.org/changes/?user=ljanda
>>
>> Hey all,
>> I would like to mention our experience with this migration. (not the 
>> migration itself, that is a long story as we did not like the 
>> "common" weblate workflow)
>> I migrated 3 Cockpit projects from Zanata to Weblate last week not 
>> realizing that there is a translation phase going on.
>> Yesterday Ludek pushed updates into Zanata. So I talked to him and 
>> learned that they don't use Zanata as translation platform - they 
>> just pull source file from it and push translated files there.
>> Although I agreed that they can finish this phase in Zanata and then 
>> I would do a manual sync into Weblate, Ludek tried Weblate and said 
>> it was easy to push there, so he did exactly that.
>>
>> So yes, he was able to do that, but it is important not to break 
>> their workflow in the middle of a translation phase. But after he 
>> tried Weblate yesterday, maybe he would be willing to do this also 
>> for other projects?
>>
>> MM
>
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]