Re: [native-lang] All community discussions - wich list to use?

Hi Bernhard, 

Am Tue, 5 Dec 2006 14:31:55 +0100 (MET)
schrieb Bernhard Dippold <[email protected]>:

> Hello Charles,
> 
> Charles Schulz schrieb:
> > Hello Bernhard,
> > 
> >> 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.
> > The discuss list is of course an interesting place. But there may
> > be too much noise. 
> 
> I know - but how could this be changed?
> 
> We need a central list for general discussions between developers and 
> non-coders. IMHO neither releases@OOo nor dev@OOo suite for this
> purpose as the work there has a different orientation.

I agree with you in this point. And I also agree, that flooding the
dev@ooo with non-coding topics isn't a good idea. 
> 
> I don't think that it would be a good idea to "mess" (in the eyes of 
> some developers) dev@OOo with larger threads like this one on
> non-coding topics. In the Germanophone community we had such
> discussions leading to conclusions on fundamental questions, but
> there was quite a number of people displeased about the "noise" -
> even if [email protected] is not a real developer list.
> 
> > dev@ooo has the quite rare advantage of being known by
> > everybody and not being crowded.
> 
> I doubt if it stays uncrowded, if more of such discussions take part
> there.
> 
> > I know that the list does not make up
> > for the quality of the discussions, but dev@ has a surprizingly high
> > amount of quality discussions (see the discussions on the specs). I
> > think we need a broad input of the community but not necessarily the
> > input of everybody who may not be familiar with OOo...

Yes,  I don't think, that the developers will stay on the dev-list, if
it's going to be overwhelmed with unrelated topics. 

> 
> Right - that's one of the negative aspects of discuss@OOo.
> 
> What do you think about a new list restricted to people being project 
> member of any of the OOo projects? Stating clearly that no mails will
> be moderated on the list, we could avoid such noise perhaps ...
> 
> I'd propose a name like [email protected] or something
> like that - not quite sure in the moment (it's just a first idea -
> not thought about it thoroughly).

Normally I would say, "Yes, this is a good idea", but do you really
think, that everyone will subscribe to this list? There were thoughts,
that there are too many mailinglists, that no-one can monitor all the
lists. This was the main concern for missing (important) informations. 
And now, we create a new list? 

Don't misinterpret me, I would say, that having such a list, open only
for project members, would be a good idea, but I doubt, that the
people, already active in any project, will monitor another list. 

> > 
> > For discussions on communication and walled gardens, I suggest we
> > keep them here, on this list?
> > 
> For walled gardens between N-L project teams this is the right list,
> but it doesn't help at all if we find a way to optimize the way of 
> communication with developers if they don't take part in this
> discussion.

I don't like the idea of a walled garden in a community project like
OOo. In my opinion, a garden is a lot nicer, if it's open and welcoming
to everyone. ;)


Sigrid