Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <4E609CDB.1050407@wtnet.de>
References: 
 <CAG6wa6GrNMkTVaoAhQyJV=4f0tJQEuZP3nKS8y8E0j4O858n=Q@mail.gmail.com>
	<671317C7-8EA2-4212-A95F-8DCB45120D28@free.fr>
	<CAG6wa6GtrTcrcfrz2-4CKWGuY4pG4CXkJ3vZ1DktRSH3N00nEA@mail.gmail.com>
	<4E609CDB.1050407@wtnet.de>
Date: Fri, 2 Sep 2011 08:01:05 -0400
Message-ID: 
 <CAP-ksoiMnJ6VmzR0p=qskSZzKoK_c4ayBvMh_=v9ph1MrKy19g@mail.gmail.com>
Subject: Re: Set up of ooo-ja-general@incubator.apache.org
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 2, 2011 at 5:07 AM, Marcus (OOo) <marcus.mail@wtnet.de> wrote:
> Am 09/02/2011 10:10 AM, schrieb Kazunari Hirano:
>>
>> Hi eric,
>>
>> On Fri, Sep 2, 2011 at 4:58 PM, eric b<eric.bachard@free.fr> =C2=A0wrote=
:
>>>
>>> Hi,
>>>
>>>
>>> -1 from me, for the following reasons :
>>>
>>> - we should define something general, for all the locales in the same
>>> time,
>>> but not one and another one .. and so on.
>
> I also would like to see some agreements what and how to do it.
> To prevent to process single puzzle pieces again and again.
>
>>> - no precipitation is better : not everybody understood how to create a=
nd
>>> even propose a new project, re replace the existing NLC one.
>>> - how does this work ? K. Hirano asks, and will manage everything alone=
 ?
>>
>> No. =C2=A0I can not do it alone. =C2=A0We will discuss how to manage thi=
ngs on
>> the list with Japanese users and contributors.
>> I don't propose creation of a native language project.
>
> It should be known that there are already some people that will manage th=
e
> list; like for the ooo-users@ list.
>
>> I am proposing creation of a list where Japanese AOOo users and AOOo
>> developers and AOOo contributors can understand Apache OpenOffice.org
>> project and discuss how to make AOOo the product and community better
>> "in Japanese" to involve Japanese users and contributors who don't
>> read English.
>
> Furthermore we should talk about a common structure how to name the lists
> befor we have different names for different NLC groups. To prevent
> uncontrolled growth regarding names.
>
> To stick with a known naming I would prefer ooo-users-ja@. Or maybe
> ooo-discuss-ja@ when you already know that many discussions will come abo=
ut
> the Japanese way of AOO.
>
> Please don't get me wrong but "general" looks like that the content is no=
t
> yet known what will be posted in the list. ;-)
>

Actually, the convention at Apache is to have "general" lists for
projects.  Remember, all lists are used for discussions. The name of
the list expresses either 1) Who is doing the discussing (dev, users,
etc.), or 2) The topic of the discussion (private, support, etc.)
There is no need to put the name "discuss" in the list name.
"General" would be for discussions that are not specific to any other
project list.  So discussions of general interest.

I know this is different than how OOo did it.

> Marcus
>