Am 12/12/2013 11:08 PM, schrieb Kay Schenk:
On Thu, Dec 12, 2013 at 12:09 AM, Jörg Schmidt<joe...@j-m-schmidt.de>wrote:

From: Andrea Pescetti [mailto:pesce...@apache.org]
Sent: Wednesday, December 11, 2013 2:10 PM
To: dev@openoffice.apache.org
Subject: Re: German community needs a second mailing list for
effective working

jan i wrote:
+1 from me, my only concern is how to make sure important
information is
not kept solely on dev-de (important may also be hints
about how to compile
etc). I see a heavy burden on the moderators to ensure that
this happens.

It depends on the focus, but from Joerg's initial
description, the new
list would help "distinguish general user questions from specific
discussions among the project members", so the structure seems very
similar to the two mailing lists in Italian (one for
users/support, one
for volunteers/coordination/discussions). Moderation is easy
in this case.

Exact.

Let me say once again absolutely clear, the new list of
"dev...@openoffice.apache.org" to record all information will be already
today on
the other de-list (users...@openoffice.apache.org) and for project work
are
important, nothing is what it are lost.

(Note: Today's "users...@openoffice.apache.org" is in fact not what the
name says,
but rather in truth it is a 'dev-and-users...@openoffice.apache.org', and
that
makes problems.)



Greetings,
Jörg


In concept, I don't have objections to this new list, but wish it could be
named something other than "dev-de" so it doesn't get confused with
dev@openoffice.apache.org.  But...I don't have any suggestions.

hm yes, that's a good point. "dev@" and "dev-de@" are very similar and the differentiation is not really good visibile.

But I've a suggestion. ;-)

What about to name the new ML like what its purpose should be (coordinate the project work):

project-de@

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to