On Fri, Oct 14, 2016 at 01:35:18PM +0200, Jean-Baptiste wrote:
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.
Hi Parag, Jean-Baptiste,
Yes, we need to understand the criteria.
If the criteria is not 'everyone that is in one of the previous groups',
we may not need to mass-import those people and we can proceed in a
"normal" way.
> 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.
cvsl10n is not a good name, imho, since we don't use CVS anymore.
About the two groups, yes, we could go that way but I think it's not
necessary, since - as you mentioned - we are not associating privileges
to this group, is more a way to know the people that are interested in
the topic (and let anyone in the project know).
> Again, Why can't any fedora user can have freedom to add
l10n or i18n
> string in any new/existing fas group name?
Not sure what you mean here
> 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.
Actually FAS han API that - given a group name - gives you all people in
that group.
Also, I was speaking this morning with pingou and he agreed that if we
are not able to find some data that are needed for this reorganization,
he (or other fedora-infra people) can run SQL queries against the FAS DB
and at that point, we can know whatever we want.
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;
coordinators could be sponsors of the FAS group, so they can perform
such actions.
* we should consider to delegate the self-introduction to the local
team
only if there is a dedicated active mailing-list.
I think it would make sense to have all people presenting themselves in
the G11N list, since the local ML are localized (aside the fact that
only includes the translators for that specific locale), and I think a
presentation in English should be present for every person.
As a bonus, create something automated when approving a new user in
Zanata
team would also be a great progress.
I see this as complex, if you mean that G11N FAS members would be
automatically approved in Zanata, since Zanata has different teams based
on the language, while the G11N FAS group would be only one.
If you mean the other way around, it would be possible, but I see very
badly any kind of self-approval for FAS groups (you know, to avoid the
possible SPAM problem).
Best,
Fale
--
Fabio Alessandro Locati
Red Hat - Senior Consultant
PGP Fingerprint: E815 3C49 2A8D FD8B 1CBD BC85 FDB3 DF20 B2DC 9C1B
