Re: L10N after Contributors and Coordinators, let's go deeper

The problem with reviewing is greater when the translation team size
is small, or the translator is alone in not really worldwide spoken
language. Therefore if the translation process is not owned by the
translators of the language, and not even controlled directly - we are
on the mercy of others. The real solution will be when we translators
are own the po files, and take responsibility, and direct pull/push
mark on updates - separated from packages. But this is an other issue.

When we are talking about structure:

Right now, I think language team leadership/council should consist
from 4 person Noriko, Piotr, Alex, and Pravin. Many times Noriko,
Pravin and Piotr took care of the l10n community with mailing lists,
and membership.

For community engineering - Alex did, and does the stuff with Zanata.
I'd like to suggest one more person who is interested with typography,
and input methods - Mike Fabian (if he accepts this listing in wiki).
I would like to suggest here few more person, that actually helps with
i18n, stats management, community care reports, meetings and such.

For administering, I think would be the best to have Pravin - and for
fallback Noriko - IMHO. For the structure, if someone has questions,
and need to know the know-how, how to use Zanata itself - I think, one
mentor is necessary either as we do for ambassadors or we can take
this role to implement the l10n team leaders.

Contributors with l10n team leaders > l10n team leaders under the lead
of an single admin with a mentor > g11n language team
leadership/council with the engineering... and we have formed a
structural team, I think.

With this we are following the same infra as we use in big, therefore
we know it that perhaps can work inside the g11n team too.

Zoltan

2016-10-04 8:21 GMT+02:00 Jean-Baptiste Holcroft <jean-baptiste@holcroft.fr>:
> Le 19/09/2016 à 18:16, Marcel Ribeiro Dantas a écrit :
>>
>> 2016-09-19 7:58 GMT-03:00 Jean-Baptiste <jean-baptiste@holcroft.fr
>> <mailto:jean-baptiste@holcroft.fr>>:
>>
>>
>> Hi Marcel, it's a good idea, but first we need to describe this
>> role on the wiki. With Zanata's behaviour, I think it is a
>> mandatory role in a team. Your contribution would be really
>> appreciated. Please write a draft about this on your wiki page.
>>
>>
>> https://fedoraproject.org/wiki/User:Mribeirodantas/Drafts/Reviewer_Role
>>
>> v0.1 :-)
>>
>> Feel free to edit/improve.
>
>
> While I know Reviewer Role is important in internal organization, I do not
> feel like define it as a global "Fedora Localization Project" role.
>
> Each team may chose have one, many, give them more or less importance and
> combine it with other roles. It is a good practice to have one, but I do not
> feel like mandatory to have your team working.
>
> I would feel better just to add some hints about "Reviewing with Zanata" in
> L10N/Guide.
>
> By the way, as far as I know, "translated" strings are still pulled by
> projects, whatever approved or not so we should present this as a non
> mandatory action so little team do not waste resources approving string by
> string.
>
>
> --
> Jean-Baptiste Holcroft
> _______________________________________________
> trans mailing list -- trans@lists.fedoraproject.org
> To unsubscribe send an email to trans-leave@lists.fedoraproject.org

--
PGP: 06853DF7
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org