CVSL10N access approval
noriko at redhat.com
Thu Nov 20 23:36:33 UTC 2008
Dimitris Glezos さんは書きました:
> Seeing about 10 membership requests on cvsl10n's queue right now, a decision
> probably needs to be made soon, ensuring that people deciding to join our
> project, actually _do_ join it before their patience gets exhausted. :-)
- I have not seen the translator who made introduction matching with the
username who sent cvsl10n group application. But I might just miss out.
- While I have not heard any further push for approval from any user via
ML, personal mail nor irc channel. But he/she can be shy to do so and
choose being patient.
Did we miss out anyone? If so please shout!
> On Fri, Nov 7, 2008 at 3:20 PM, Igor Pires Soares <igorsoares at gmail.com>
>> Em Sex, 2008-11-07 às 10:21 +0530, Runa Bhattacharjee escreveu:
>>> Noriko Mizumoto wrote: The above is the model currently followed by Gnome
>>> account system and is a good way to ensure that the language
>>> maintainer's nod is taken into account before granting a new entrant commit
>>> rights. Due to the large number of language teams (>~75) in FLP, granting
>>> cvsl10n approval rights to the maintainers for each language team is not a
>>> scalable model (imho). Rather, the introduction of an additional step -
>>> "approval from the language maintainer" - would ensure that the the process
>>> does not lose its streamline.
>> I agree that the inclusion of an approval from the language maintainer is a
>> good way to go but I don't thing granting cvsl10n credentials for a new
>> member is a good idea. IMHO the members should have some experience in the
>> team before his credential approval. The idea is just add some guidance to
>> the translator, in order to avoid mistakes.
> So what do we need to get this going? A few thoughts:
> 1. Give sponsor access to all language coordinators and write a SOP for adding
> new people to a group on a wiki page.
> 2. Some folks step up to give some love to the applications for languages
> without a maintainer and those which stay on the queue for more than a few
> 3. Update the TQSG with the new instructions. Make the steps including
> self-introduction not optional.
More information about the Fedora-trans-list