On Thu, Jun 02, 2016 at 08:25:18AM -0400, Máirín Duffy wrote:
Hi!
So we have three hubs we're trying to target to be nicely designed
and ready-to-go for the Flock prototype:
- Design Team
- CommOps Team
- Translation Team
Just a quick note that I've been working on issues #167 + #165 which
are in support of the Translation Team hub. I've been doing some
research about translation workflow and Zanata. I met with Yu Shao
who is the development lead for Zanata itself. If you haven't seen
the Zanata UI you should check it out. You can log in using your FAS
account:
https://fedora.zanata.org/
It has a really cool interface where you drill down into a project
and you can view strings in need of translation and type in your
translated strings right on the site. No local installation of
clients / tools or building stuff locally or anything - you can just
get right to translating in the UI.
I have also reached out to Noriko Mizumoto from Red Hat and Fedora's
translation team to learn more about translator workflow and how
that team works right now.
Based on what I learn I'm going to design + mockup some widget ideas
for the Translation Team hub. They will probably involve some kind
of integration with Zanata. Some initial ideas:
- Widget that displays % translated statistics for various critical
pieces of Fedora. (How do we define critical?) Goal of the widget
would to be to identify those parts of Fedora in most critical need
of translation and try to encourage translators to pop over to those
items in Zanata and submit some new translations.
I remember discussion around fedmsg support for Zanata, but I don't remember how
things are nowadays. If we do not have fedmsg in zanata, then we will end up
caching the % of translation and various stats without a way to clear that
cache, ending up in a situation where we're showing invalid stats.
Pierre