On 2018/08/05 21:11, Sundeep Anand wrote:
Thank you so much, discussing this :)
Many of transtats parts are under-development. I can explain, but I need some time making
> Hi Sundeep
> Thanks for reply, see inline.
> On 2018/08/05 14:22, Sundeep Anand wrote:
> [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...
Let me reinstate that zanata/damnelies can show most accurate statistics.
For translators, it seems best to refer the original stats unless any
Here, I am worry, it may results that translator may need to go back and
forth between zanata, damnelies, transtats etc.
> 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?
We have master list. And can create subset. This subset will be linked to each release.
For packages it is under development. Similar idea has been implemented for languages.
Oh, that sounds cool, could you please kindly share where we can refer
that master list, please?
I am most happy to update our wiki page.
> [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 of now, transtats just do read operations. Jobs pull stats / language resources to
generate meaningful stats / reports. No build or push to the source repository. With
fedora deployment, FAS authentication would be available - and then permissions may come
into picture. (we have some time deciding on that). I hope to discuss this at flock
I am sorry, due to my own business I no longer am able to attend this time.
Could you mind to explain a little more detail about a "job"?
I can't believe that this job makes a maintainer happy atm, but might
create an unnecessary trouble.
> 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.
Obviously, this is for maintainer. Actually, this ease some QE work.
Great to hear!! also I would like to know how it can ease QE work :-)
feel free to bug me,
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines