Re: [native-lang] Position of Native-Lang and other non-coding parts of the communty [was: New template project]

Thanks for the explanation, jonathon, and nice to meet you here. :)

On 04/12/2006, at 10:49 AM, [email protected] wrote:

>
>> I've been surprised not to see frequent mails on this or the  
>> dev@l10n list, requesting translations of modules, webpages,  
>> documentation, wiki
>
> OOo suffers from having _too_ many mailing lists. The last time I  
> counted, there were over a hundred mailing lists.  As a result,  
> requests for the things you mention can be scattered over all of them.

Yes, I can see that. This single project (from the i18n POV, and one  
of only 25 in my case) so far requires me to be on 10 mailing lists.  
And obviously I'm still missing out on needed info. :S

But still, it makes sense that requests for translation would come to  
this list, or to the dev@l10n list. If the requesters want to send  
individual invitations to all the NLPs, that's their choice. Either  
way, we would still get the invitations. And we aren't receiving them.

Does this mean people don't ask to have things translated?
>
>> little or no discussion of l10n bugs and the continual effort to  
>> fix them.
>
> That is due to one of several things:
> * They are discussed and (maybe) fixed on a specific list of the  
> NLP that is affected by the specific bug;

I reported several bugs from the testing builds, and none of them  
affected only our NLP. I'm not saying such bugs don't occur, just  
that most bugs will affect the product overall, and at least one  
architecture.

> * They are discussed on one of the specific developer lists;

If l10n bugs are being discussed on dev lists other than dev@l10n,  
then the developers are missing out on the expertise and specialized  
information they can get from a l10n list.

I suppose I'm much more accustomed to seeing such bugs followed  
through on l10n lists, to make sure they are solved, and discuss and  
implement ways of solving them. Input and display problems affect  
different languages differently, and we can help the developer with  
that information.

> * They are discussed in issuezilla;

Possible. But I've only seen tags (progress tags, but just tags) on  
the ones I've submitted so far. No discussion.

> * They are ignored;
> * The gatekeepers for Issuezilla don't have a clue about history,  
> geography, writing systems, languages, or anthropology, and hence  
> close issues because of their ignorance in those subjects;

Yes. :S
>
>>  but we don't seem to be talking to each other very much.
>
> Historically, every time a slightly different aspect of project  
> management has come up, a new list has been created for it. Which  
> means that the only communication that happens, is between people  
> who are subscribed to the same list.  If people aren't subscribed  
> to a list, they have lost the ability to even marginally track what  
> is going elsewhere in the project.

This is a pity. Surely their is an overall hierarchy of information,  
so child lists could have the responsibility of reporting back to  
overall lists. Otherwise it's just fragmentation.

from Clytie (vi-VN, Vietnamese free-software translation team / nhóm  
Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN