Processes in the L10N team

[A S Alam]

Dimitris Glezos ਨੇ ਲਿਖਿਆ:
> (removed -devel-list since this is a -trans-list issue)
> 
> 
> O/H Thomas Canniot έγραψε:
>> Le dimanche 26 novembre 2006 à 01:21 +1000, Chester Cheng a écrit :
>>> Hi Igor,
>>>
>>> The .pot file hasn't been prepared by the author.
>>> It will be released soon and we can make po files then.
>> I think there is translation related problems here.
>>
>> Why hasn't it been made BEFORE FC6 ?
>> Why hasn't it be done at the same time than developing desktop-effects ?
>> Why translation is always seen as second class interest by developers ?
>> Why most translators seem to accept this second class idea ?
>> Why bugzilla bug reports must be opened to force a developer to add
>> translations ?
>>
>> Question I don't have any answer for ... yet ? 
> 
> Thomas,
> 
> I agree we need to fix our l10n process. I've spoken to some people and the
> presence of the gap is pretty much known. How can we fix it then?
> 
> Here are some first ideas:
> 
>   1. Start by documenting the need for attention to this matter, for example by
> getting some numbers of the non-english users (e.g. fedora-brazil is HUGE)
> 
>   2. List irritations the translators have stated in the past. One example is
> releases not having up-to-date translations in packages [1].
> 
>   3. Start having IRC meetings to discuss things, our progress and get people to
> hang out on the IRC channel more often.
> 
sure, that is most important to improve our communication between team
#fedora-l10n is there, you all are welcome. Let us start on channel

>   4. Think about electing a Steering committee for the team; check out the
> DocsProject voting proposal:
> 
>     http://fedoraproject.org/wiki/DocsProject/Policy/FDSCoElections
> 
>   5. Start writing guidelines for developers and slowly try to make them happen.
> A steering committee can help with this by having open communication channels.
> 
+1
>   6. Open up a wiki page holding links to common/known problems, a bug tracker
> for translation bugs (is there one?) and start pushing release-blocker bugs for
> important issues.
> 
+1
>   7. Get the team closer to the Docs project; this team does a *great* job and
> the two teams have a lot in common and could share experience, tools etc.
> 
> 
we are already working with docs team, but need more closely and more 
sharing information/data with team.

> The L10N project shouts "I need resurrection" with all it's strength. So, to
> have something to hold onto, I copied the above points here:
> 
>   http://fedoraproject.org/wiki/L10N/Tasks
> 
good idea

-- 
A S Alam
timezone: GMT+5:30
join us at #fedora-l10n (freenode)

"Either find a way or make one"