[native-lang] Information flow (was: Re: [native-lang] New template project

On 04/12/2006, at 10:11 PM, Charles Schulz wrote (in part):

>
> So whatever you/we do, we have to include people from the  
> documentation,
> people from Sun/Novell, engineers, UI testers, marketing/art  
> people, the
> NLC community members, etc. In short, lots of people :-) .

To follow on from what I was saying about a hierarchy of information,  
it doesn't mean each sub-project has to send all information to other  
projects.

It simply means that you send an initial description of what you are  
doing, to the main lists in the information hierarchy (dev@l10n/ 
dev@nlp, dev@doc etc., one list to represent the information target  
root in each main area), including a link to the information source  
root (e.g. wiki page).

Following that, you only need to communicate with other lists when  
you're looking at changes which will affect them directly. That may  
mean keeping dev@doc in the loop all the way with templates, or  
requesting a representative from dev@doc follow the templates list,  
but it would only mean writing to dev@nlp when you were talking about  
internationalization: translation and implementing your work in  
language communities.

With a lot of lists, this could be complex, but it would be much  
simpler if we had an overall list of _all_ mailing lists, like a site  
map, grouped in their information categories. The top list in each  
group is the information target root for other lists' mails about new  
work.

The information domain of each list could be included as a tooltip to  
each list link on the overall page.

I'd be willing to work on this, to try and improve the information  
flow here at OOo.

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