On Mon, Aug 10, 2020 at 11:34 AM <jean-baptiste@holcroft.fr> wrote:
thanks for your answer, but i don't want to be linked to transtats.

This tool requires much more technical knowledge to contribute than what I can do.

I guess, it's just about consuming a couple of APIs for you! Obviously I'll do the 'extend' part in Transtats. Moreover, if that helps we can do a demo as well.

in addition, it requires per project configuration, which makes it covering 80 project while we have thousands times more srpm in Fedora.

"Sync Package Build System" job works for any package which is built in fedora irrespective of its presence in Transtats! 
Just that currently the job is limited to `PO` files[1].

Idea behind developing "Transtats Jobs Framework" is to have a centralized processor through which we can solve multiple sets of problems in a flexible way.
Because, it has information about Fedora Release (and its Schedule), Package Source Repo, Package Translation Platform, and Package Build System; and interestingly we can expand them[2].

Multiple sets of problems can be captured and executed in the form of Job Templates. And jobs are YAML based, hence flexible - we can edit them. 
Hence, jobs can be unique though they originate from the same template.

I agree, the development pace of Transtats is slow, however, it can deliver better results if tweaked in the required way!

thanks Jean-Baptiste!


[1] https://github.com/transtats/transtats/issues/149
[2] https://speakerdeck.com/sundeep/use-cases-for-transtats-in-the-fedora-community?slide=13



--
Jean-Baptiste
_______________________________________________
i18n mailing list -- i18n@lists.fedoraproject.org
To unsubscribe send an email to i18n-leave@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/i18n@lists.fedoraproject.org