Re: Weblate transition & integration for upstream projects

Le 2019-11-05 12:15, Daniel P. Berrangé a écrit :
> I'm the maintainer for various upstream projects [1] which are 
> currently
> using Fedora's Zanata for translation services and I saw the recent
> change proposal for Fedora to shift to Weblate in the next release
> cycle.


Thank you for coming here and engaging this discussion!

> First I'm wondering what sort of time frame is being targetted for move
> of the upstream projects which are independant of Fedora's release 
> cycle ?

Wish: by February, all projects are using the new translation platform.
Reality: there is no hard timeframe, but the translators won't go on 
multiple translation platform, and because most important packages will 
have migrate, it may lower a lot the number of contributions to non 
migrated projects.

> Next, and more importantly, I'm trying to understand how we will 
> integrate
> with Weblate....
> 
> The .pot file is never stored as it is an huge auto-generated file 
> which
> would be out of date as soon as it was committed. We would always 
> rebuild
> this from master source files whenever it is needed so it is fully 
> updated.

Suboptimal is the pot file format, but also is the best we have.
Next generation may be the "Fluent" file format from Mozilla, wait and 
see.

> We also recently stopped storing full .po files [2], again because they 
> are
> huge files with a large amount of redundant information in them. 
> Instead
> we store what we call ".mini.po" files. This is the same file format as
> a normal ".po" file, but with
> 
> [...]
> 
> Thus I'm trying to understand how we'll go about integrating with 
> Weblate.

It's an interesting thing you did!

I see a few solutions:
* you create a repository dedicated to pot and po files,
* you interact with Weblate using the command line interface or one of 
the APIs.

> Finally in Weblate after authenticating with FAS, I still don't have 
> the
> ability to create new projects. Is this intentionally restricted ? I 
> was
> hoping to do some testing with Weblate & one of the virt apps like
> virt-viewer to try to understand its operation better before any formal
> transition period.

Yes, project creation is locked on purpose and won't be open.
Correct configuration isn't so easy and it requires some interaction 
with localization team.
The way it worked with Zanata was way too loose, nobody was informed 
when a new project came or when a project created a new document/branch.


I would love to collaborate with you to find a correct workflow using 
either method of your choice (and your help with DNF and anaconda team 
would be much appreciated), but first: _we need approval from Brian 
Exelbierd or Ben Cotton to continue deployment_. Red Hat and Weblate 
should finish the paperwork (billing + terms of use). Brian is the one 
responsible for this action.


Note for readers: I will always suggest to keep it simple and include 
pot/po files in repository for little projects. Don't invest time in 
automation as it will add maintenance work and lower the proximity 
between upstream source code and the translation platform.

Jean-Baptiste
_______________________________________________
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]