Re: [native-lang] All community discussions - wich list to use? (was: New template project)

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


I didn't have the time to reply to all of the other mails I want to 
comment (but will do so).

Just one question WRT this mail (as this solution did come to my mind too):
Charles Schulz schrieb:
> Petr, all,
>> Is there any volunteer who could start the discussion with other projects, 
>> actively cooperate with them, discuss the template needs...? I think that we 
>> really need more cooperation.
>>   
> Tomorrow I'll lauch the discussion on the dev@ooo list. I think it's the
> best choice, and nobody will be able to say that it was done behind
> close doors... :-)

I am not sure if this topic is more a developer topic (to be discussed 
on dev@OOo) instead of an all community topic, that could be discussed 
on [email protected] with a broader audience.

Of course there are more developer subscribed to dev@OOo, but my 
feelings are that discuss@OOo should be used for *any* discussion or 
decision with effect on major parts of the community.

I strongly recommend to subscribe this list to anybody interested in 
overall community topics - and to post such messages there.

For the starting point of this discussion (the new template spec) I 
would have been interested in a mail to [email protected] 
once this project had been started (if I didn't miss the mail there).

This list should be one to be used more frequently IMHO (especially in a 
earlier state of a spec). I know that huge discussions tend not to lead 
to a better result, but keeping people uninformed because someone wants 
to avoid discussions and present something as "fait accompli" is not the 
way I want our community to work.

We saw many examples how this attitude caused frustrations and time lags 
afterwards...

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.