(2014年07月11日 13:41), Marcelo Barbosa wrote:
We may collect the Transifex all Coordinators, Reviewers and
Translators through the API, for example:
$ curl -i -L --user username:password -X GET
Think this activity will diminish the impact of migration.
Today we have the teams names entry Zanata different of wiki page
) and too Transifex, for
example, in the case of my team in Zanata this: "pt-br" and in our wiki
this "pt_br" and Transifex "pt_BR", I believe our default is wiki, in
Agree, our default is wiki.
The steps for
necessary creating the group "Fedora", from what I understand in of
Zanata a group should have the "Fedora", in languages would be the teams
and designs belong to a group, I believe that the relationship is this,
if I'm wrong please correct me.
I am not too sure if the group in zanata works as it has been working at
transifex. Here we need an input from zanata team, Luke, Carlos?
afaik, currently zanata has only one set of language teams.
Thus translator belonging to xx-XX can translate any file for xx-XX of
any project registered. Please correct me if I am misunderstanding.
* Zanata/Language Team/xx-XX
We may need separate set of language teams to control access, since
there are other projects which is not part of Fedora.
This restricts translator who is not belonging to particular umbrella
(group, org, whatever called) from translating file(s) of that umbrella.
* Zanata/Fedora/Language Team/xx-XX
* Zanata/Project_Name/Language Team/xx-XX
Transifex has had this feature. Thus there is no need to worry that
non-member of xx-XX of the language team under that umbrella modifies a
* Tx/Fedora/Language Team/xx-XX
* Tx/Transifex/Language Team/xx-XX
* Tx/Project_Name/Language Team/xx-XX
I've requested this feature sometime ago, but unable to locate the
bug... This is the one listed under 'Concerns'.
Btw, unless Infrastructure team needs to track this discussion for some
maintenance reason, can we discuss at trans list only as many of
translators have not subscribed infrastructure list?
I hope the new version of Zanata (3.4.2) is faster, because for
the test platform is a little slow.
On Thu, Jul 10, 2014 at 11:39 PM, Noriko Mizumoto
<noriko(a)fedoraproject.org <mailto:email@example.com>> wrote:
I've read your thread posted in Infra.
Indeed, it is sad to hear but understand your position.
It was just like yesterday, we moved from elvis to transifex. Since
then, you have been supporting us translators 24/7. I thank you so
much from my heart, can't say enough.
I support the move to zanata, but I don't think that our
relationship is fading out.
Robyn, thanks for copying trans at lists.
I believe that this (trans list) is the place to discuss and decide
the way we go as translators.
(2014年07月10日 22:01), Robyn Bergeron wrote:
----- Original Message -----
From: "Kevin Fenzi" <kevin(a)scrye.com
Sent: Friday, July 4, 2014 9:53:48 AM
Subject: Re: Transifex has become proprietary
On Fri, 4 Jul 2014 10:11:45 +0200
Pierre-Yves Chibon <pingou(a)pingoured.fr
On Thu, Jul 03, 2014 at 10:25:41AM -0400, Rahul Sundaram
On Thu, Jul 3, 2014 at 10:20 AM, Pierre-Yves
What are they?
I haven't spent a lot of time looking up
alternatives but I am
aware of the following:
developed by Red Hat
Translatewiki which is apparently what
MediaGoblin is considering
For the record, I support the move away from Transifex
and will relay
the sad news to the projects where I have before advice
The question is of course moving to what? That's
something I cannot
advice on atm.
Yeah. There's also some more mentioned in the above
Would someone care to look at them all and provide some
each and how well they might work for our needs?
Copying the trans list since they probably have some good input
about their needs :) (And nothing on this topic in their
archives, not sure how much overlap between these two lists.)
For the translations team's reference -
is the original mail Rahul posted on the subject.
infrastructure mailing list
trans mailing list
trans mailing list