Dear coordinators,
We have two clear L10N roles :
* Contributor
* Team coordinator
I now suggest to clarify one last one, the role of the people having special helping the global coordination. This role is actually held by a few people : mainly by Noriko Mizumoto, but maybe also Alex Aeng and Piotr Drąg?.
Why would I want to give them an "official title" ? I want to have more description on the wiki about people to reach to answer/solve wider problems/questions.
Typical use cases : * I want to take coordinator role of a team but the previous coordinator do not answer anymore * I want to change content on Zanata (like groups, welcome page) * I need administrator help on trans@ mailing list * I need administrator help on FAS groups * I want to add a new language
Those people are administrator of our tools, to help as superpower people when coordinators are stuck.
This role is not in competition with the group decision management we have : every coordinator has the possibility to assists G11N meetings and L10N meetings, to share ideas, lead projects, organize events, improve process, make communications.
I aim to keep the inverted pyramid logic and suggest ***L10N Pillars***. Pillars < Coordinators < Translators.
Please give your feedback about this proposal before September 25th. Btw, if this role is agreed, I will ask design team to make a little image for each roles on the wiki.
Thanks for your help,
Hi Jean-Baptiste,
If you're asking the design team to make little images for the roles on G11N/L10N, I think reviewers deserve a little image too :D.
Best regards,
Marcel Ribeiro Dantas Gerente de Projeto Laboratório de Inovação Tecnológica em Saúde s: mribeirodantas.fedorapeople.org e: mribeirodantas@lais.huol.ufrn.br "An idea is only knowledge when shared." http://linkedin.com/in/mribeirodantas
2016-09-11 17:25 GMT-03:00 Jean-Baptiste Holcroft <jean-baptiste@holcroft.fr
:
Dear coordinators,
We have two clear L10N roles :
Contributor
Team coordinator
I now suggest to clarify one last one, the role of the people having special helping the global coordination. This role is actually held by a few people : mainly by Noriko Mizumoto, but maybe also Alex Aeng and Piotr Drąg?.
Why would I want to give them an "official title" ? I want to have more description on the wiki about people to reach to answer/solve wider problems/questions.
Typical use cases :
- I want to take coordinator role of a team but the previous coordinator
do not answer anymore
- I want to change content on Zanata (like groups, welcome page)
- I need administrator help on trans@ mailing list
- I need administrator help on FAS groups
- I want to add a new language
Those people are administrator of our tools, to help as superpower people when coordinators are stuck.
This role is not in competition with the group decision management we have : every coordinator has the possibility to assists G11N meetings and L10N meetings, to share ideas, lead projects, organize events, improve process, make communications.
I aim to keep the inverted pyramid logic and suggest ***L10N Pillars***. Pillars < Coordinators < Translators.
Please give your feedback about this proposal before September 25th. Btw, if this role is agreed, I will ask design team to make a little image for each roles on the wiki.
Thanks for your help,
-- Jean-Baptiste Holcroft -- trans mailing list trans@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org
Le 11/09/2016 à 22:34, Marcel Ribeiro Dantas a écrit :
Hi Jean-Baptiste,
If you're asking the design team to make little images for the roles on G11N/L10N, I think reviewers deserve a little image too :D.
Best regards,
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.
2016-09-19 7:58 GMT-03:00 Jean-Baptiste 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.
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.
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
Dear Coordinator, please remember to have a look at this proposal about L10N Pillars and to respond it before sunday (september 25th) : https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/...
2016-09-11 17:25 GMT-03:00 Jean-Baptiste Holcroft jean-baptiste@holcroft.fr:
Dear coordinators,
We have two clear L10N roles :
Contributor
Team coordinator
I now suggest to clarify one last one, the role of the people having special helping the global coordination. This role is actually held by a few people : mainly by Noriko Mizumoto, but maybe also Alex Aeng and Piotr Drąg?.
Why would I want to give them an "official title" ? I want to have more description on the wiki about people to reach to answer/solve wider problems/questions.
Typical use cases :
- I want to take coordinator role of a team but the previous coordinator do
not answer anymore
- I want to change content on Zanata (like groups, welcome page)
- I need administrator help on trans@ mailing list
- I need administrator help on FAS groups
- I want to add a new language
Those people are administrator of our tools, to help as superpower people when coordinators are stuck.
This role is not in competition with the group decision management we have : every coordinator has the possibility to assists G11N meetings and L10N meetings, to share ideas, lead projects, organize events, improve process, make communications.
I aim to keep the inverted pyramid logic and suggest ***L10N Pillars***. Pillars < Coordinators < Translators.
Please give your feedback about this proposal before September 25th. Btw, if this role is agreed, I will ask design team to make a little image for each roles on the wiki.
It looks like a pillar is an admin. Why not admin ?
You still have the role developers for higher level needs.
k.r.
Domingo Becker (es)
2016-09-19 17:38 GMT+02:00 Domingo Becker domingobecker@gmail.com:
It looks like a pillar is an admin. Why not admin ?
You still have the role developers for higher level needs.
I agree with Domingo. The simpler name is preferable, and admin seems to fit the role perfectly.
Best regards,
Le 19/09/2016 à 18:49, Piotr Drąg a écrit :
2016-09-19 17:38 GMT+02:00 Domingo Becker domingobecker@gmail.com:
It looks like a pillar is an admin. Why not admin ?
You still have the role developers for higher level needs.
I agree with Domingo. The simpler name is preferable, and admin seems to fit the role perfectly.
Best regards,
Ok, we have an agreement for the content but not on the name.
I'm afraid I do not like "admin" : * it may sounds "bureaucratic" or "technical", * it doesn't bring any allusion to the great work needed to support community activities, * for a language focused team, shoudn't we be "a little" more innovative in the word we use, aren't we people who love the words?
If someone ask me : "Hey, who is Noriko/Piotr/yourNameHere ? This name is everywhere!". I want to answer something that is actually meaningful to represent the involvement of the contributor. Answering "Admin" is just gonna be understand has: the-guy-in-the-basement.
Pillars was in continuation of the inverted pyramid, we probably can add more poetry if you wish.
What about "Master Librarian" (The main person keeping an eye on all books in the library, wise person, master of all knowledge) ?
On 29 September 2016 at 06:42, Jean-Baptiste jean-baptiste@holcroft.fr wrote:
Le 19/09/2016 à 18:49, Piotr Drąg a écrit :
2016-09-19 17:38 GMT+02:00 Domingo Becker domingobecker@gmail.com:
It looks like a pillar is an admin. Why not admin ?
You still have the role developers for higher level needs.
I agree with Domingo. The simpler name is preferable, and admin seems to fit the role perfectly.
Best regards,
Ok, we have an agreement for the content but not on the name.
I'm afraid I do not like "admin" :
- it may sounds "bureaucratic" or "technical",
- it doesn't bring any allusion to the great work needed to support
community activities,
- for a language focused team, shoudn't we be "a little" more innovative
in the word we use, aren't we people who love the words?
If someone ask me : "Hey, who is Noriko/Piotr/yourNameHere ? This name is everywhere!". I want to answer something that is actually meaningful to represent the involvement of the contributor. Answering "Admin" is just gonna be understand has: the-guy-in-the-basement.
Pillars was in continuation of the inverted pyramid, we probably can add more poetry if you wish.
-- Jean-Baptiste Holcroft
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org
Here is my proposal, please have a look and correct it : https://fedoraproject.org/wiki/L10N_Administrator Not a lot of enthusiasm about a more interesting name, so "administrator" will do the job. I understand Piotr and Noriko have this role, if this is not complete, do not hesitate to add some.