Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53866899C for ; Sat, 3 Sep 2011 15:13:52 +0000 (UTC) Received: (qmail 10494 invoked by uid 500); 3 Sep 2011 15:13:51 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 10413 invoked by uid 500); 3 Sep 2011 15:13:50 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 10405 invoked by uid 99); 3 Sep 2011 15:13:50 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Sep 2011 15:13:50 +0000 Received: from localhost (HELO mail-ew0-f47.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Sep 2011 15:13:50 +0000 Received: by ewy5 with SMTP id 5so1803953ewy.6 for ; Sat, 03 Sep 2011 08:13:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.2.148 with SMTP id 20mr637693eef.125.1315062828543; Sat, 03 Sep 2011 08:13:48 -0700 (PDT) Received: by 10.14.188.2 with HTTP; Sat, 3 Sep 2011 08:13:48 -0700 (PDT) In-Reply-To: <4E61A571.8000607@gmx.org> References: <4E61A571.8000607@gmx.org> Date: Sat, 3 Sep 2011 11:13:48 -0400 Message-ID: Subject: Re: Should w merge discuss@ooo into ooo-users.i.a.o ? From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Sep 2, 2011 at 11:56 PM, Peter Junge wrote: > On 03.09.2011 11:00, Rob Weir wrote: >> >> I've been going through the archives of the existing >> users@openoffice.org and discuss@openoffice.org. =C2=A0I cannot tell the= m >> apart. =C2=A0They cover the kinds of questions and topics. =C2=A0Maybe a= t some >> point in the past the project had distinct visions for each list. =C2=A0= But >> this differences are blurred beyond detection now, at least to me. > > Originally discuss@ooo was intended to be the mailing list for the commun= ity > to discuss about the community, hence both focusing on a different topic = and > addressing a different audience. Over the years discuss@ooo indeed became > something like users2@ooo. > OK. That is good to know. > >> >> Since we've recently set up the ooo-users@i.a.o, I think it makes >> sense to ask users from both users@ooo and discuss@ooo to move to >> ooo-users. =C2=A0In doing so we avoid unnecessarily fragmenting communit= y >> discussions. > > That would make sense, at least for those who are used to discuss support > topics at discuss@ooo. The few others should be happy with ooo-dev. > So we should probably mention both lists in the notification to discuss@oo.= o. We'll probably be merging other lists in a similar fashion. users@ooo -> ooo-users dev@ooo -> ooo-dev discuss@ooo -> ooo-users Also, within the projects, the dev-related projects (performance, security, api, uno, xml, etc.) should go to ooo-dev as well. > Peter > >