Le 14/10/2016 à 13:15, Parag Nemade a écrit :
AFAIK, new or regular g11n user don't need any group to work for
g11n
group. If you are asking for a general group to represent g11n people
then we need some criteria or list of people who will be part of that
group.
I agree.
I am thinking to have 2 groups for whole g11n people, one general
g11n
people maybe called as "g11n" and other is needed for translation work
"cvsl10n". Here cvsl10n group will be subset of g11n fas group. The
reason I am just thinking 2 groups is not sure if for Zanata l10n
people need different group to represent them where not necessarily
all g11n people want to participate for cvsl10n activities.
Again, Why can't any fedora user can have freedom to add l10n or i18n
string in any new/existing fas group name?
Regards,
Parag
Fale, please have a look to g11n mailing list about those groups, most
of them can be merge, but gitman-pages-l10n is a related to a project
lead by Akoh and is not related to L10N membership.
I asked about FAS behavior and features :
https://github.com/fedora-infra/fas/issues/204
The actual problem is : it's hard to know which team each user is member
of or requesting for.
Depending on what FAS can do, we may have one global group or one group
per language.
I have difficulties to write the good questions to produce two possible
solution to L10N community.
Anyway, the current process is not efficient, newcomers have pain to
join our teams. I have some examples from event and distant requests.
I'm convinced:
* we should consider to make the coordinator accountable of the user
addition to L10N group. I did it a few days ago for jaaf64 and it was
very easy and quick;
* we should consider to delegate the self-introduction to the local team
only if there is a dedicated active mailing-list.
As a bonus, create something automated when approving a new user in
Zanata team would also be a great progress.
--
Jean-Baptiste Holcroft