Thanks for reply, see inline.
On 2018/08/05 14:22, Sundeep Anand wrote:
Transtats talks to various services like translation platforms, build system, git
repositories, release schedules etc. to have an answer for - how much product release
(as-in fedora 29) is translation complete? If not why - which languages? which
packages? which strings?
[Products] tab shows just Release Schedule, nothing for
packages or strings.
Just for the statistics, Zanata should show most accurate ones (afaik)
and so Damnedlies...
A question comes up in my mind, WE ourselves have no full list of
packages for certain release, because some come up newly while others
become obsolete. Where can you reach the full list of package, and how
to know the update for release?
Transtats jobs as-one is a tool to track string change, verify
translations, inspect built SRPM for errors etc. And if we just schedule these jobs,
automation could be attained.
[Jobs] syncs with platforms, build systems, source repositories and
Does this mean, something like, a job pulls certain set of translation
from zanata and damnedlies, build, and then push to source repos? Do we
schedule this job, why? with what kind of permission? Does this make
maintainer really happy?
As this part is heavy under-development - I could not say much here
now! Basically, transtats contributes to g11n success.
It seems discussed in i18n fad, anyone there from l10n?
There is very interesting part I can see in your slide, under "Fedora
Readiness" -> 2 Engagements. This is major problem for l10n and I've
been looking for a solution for loooooong. So thank you!!
It is good feature to detect string breakage, but please be careful cz
this can kill translator if it is used wrongly. The detection must send
a warning to a maintainer, not us. A maintainer is responsible to
manually notify us by following the procedure . The goal is to
minimize the breakage, not making auto-process for maintainer easily to
break and translator to fix. I like to see a feature to send a warning
to a maintainer as well counting the number of breakage across releases.
From there, we can talk to a maintainer for improvement.