Re: [native-lang] Information flow

Bernhard Dippold <[email protected]>
Newsgroups gmane.comp.openoffice.nativelanguage
Message-ID <[email protected]>
Hi Clytie, all,

Clytie Siddall schrieb:
> 
> 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).

Charles has been asking for such information once and again - but not 
even the people heavily interested in inter project communication do 
find the time to spread the word about what's going on inside their 
projects.

Especially if there are no reactions...
> 
> 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.

That's right. Just a few examples:

Local marketing efforts might be an example for other parts of the world.

Materials worked out in one N-L project are sometimes much easier 
translated than rewritten or redesigned (depends on the context).
> 
> 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 main point is not to search for the appropriate list but to think of 
the appropriate project. Improving communication means more awareness - 
if we would be able to do this by any updated web pages, this would be 
great...
> 
> 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.

This is more than just collecting informations about the projects, but 
your effort is highly appreciated.

You know about the discussions on [email protected]. If you would help 
updating the projects.OOo page this might be a first step.

Best regards

Bernhard
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.