Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of apache@robweir.com designates
 67.222.54.6 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E4A9E8D.4070302@gmx-topmail.de>
References: 
 <CAP-ksohk1-5NgLH9-nA+4eeaAsUc4KNUh=pzz8do2nCptzG0Bg@mail.gmail.com>
	<4E4A785B.1050801@gmx-topmail.de>
	<CAP-ksojKEjVGDMQh=aoUVV+EtemHzaJOX6gaEGLESjjk6d6OBQ@mail.gmail.com>
	<4E4A9E8D.4070302@gmx-topmail.de>
Date: Tue, 16 Aug 2011 13:04:33 -0400
Message-ID: 
 <CAP-ksognRNFT8YyEw5+sEFun5ogDw2rduog8dUez3c9P-BUF_w@mail.gmail.com>
Subject: Re: [Repo][Proposal] OOO340 SVN Dump file import
From: Rob Weir <apache@robweir.com>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 16, 2011 at 12:45 PM, Ingrid von der Mehden
<IngridvdM@gmx-topmail.de> wrote:
> Am 16.08.2011 16:21, schrieb Rob Weir:
>>
>> On Tue, Aug 16, 2011 at 10:02 AM, Ingrid von der Mehden
>> <IngridvdM@gmx-topmail.de> =C2=A0wrote:
>>>
>>> Am 15.08.2011 18:46, schrieb Rob Weir:
>>> [...]
>>>>
>>>> ooo/trunk/core --- all the OOO340 stuff
>>>> ooo/trunk/l10n -- all the language stuff
>>>>
>>>
>>> Actually I would suggest to name the directory 'main' instead of 'core'=
.
>>> The term 'core' is used already in several modules within the OOo sourc=
e
>>> code, where it does imply that this is something without user interface
>>> (more the model part in MVC pattern). So using the term 'core' for the
>>> whole
>>> office (including user interface) is misleading and could create
>>> confusion.
>>>
>>
>> Note what we already have in SVN:
>>
>> https://svn.apache.org/repos/asf/incubator/ooo/
>>
>> We're mixing site files, and source in the same repository.
>>
>> I wonder if we want a "src" directory that is a sibling of "site".
>> And then "main" and "extras" under that?
>>
>
> I just searched through the different Apache projects and the scheme as w=
e
> have it is quite common:
>
> 'Apache Project'/site
> 'Apache Project'/trunk
> 'Apache Project'/branches
> 'Apache Project'/tags
>
> Those directories can be found very often. I think it is not too bad to s=
tay
> with the common scheme. This makes it easier to switch between projects f=
or
> all Apache committers.
>
> ------
>
> If we instead choose to have a src directory next to site, I would vote t=
o
> put trunk, branches and tags into it. All the different code lines are al=
l
> src, they belong together. So we would have:
>
> ooo/site
> ooo/src/trunk/main
> ooo/src/trunk/extras
> ooo/src/branches
> ooo/src/tags
>
> This will lead to an additional directory in the path. But the logical
> grouping is cleaner. A pitfall might be that some people might expect onl=
y
> source code in a directory called src and not things like help content or
> translation.
>
> So I still prefer:
> ooo/trunk/main --- all the OOO340 stuff
> ooo/trunk/extras/l10n -- all the language stuff
>

OK.  I'll do that for the the next run.  This will be Linux, with your
directory structure.   Should be ready in 3 hours or so.

> Kind regards,
> Ingrid
>
>>> I would also put the l10n stuff into a further directory. Those people
>>> who
>>> have no idea what l10n might be, could benefit from a simpler name
>>> 'extras'.
>>> This makes the first browsing experience in the source code less
>>> frightening.
>>>
>>> So I would suggest:
>>> ooo/trunk/main --- all the OOO340 stuff
>>> ooo/trunk/extras/l10n -- all the language stuff
>>>
>>> The full proposal was here:
>>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201108.mbox/=
%3C4E3D07B7.8080101@gmx-topmail.de%3E
>>>
>>> Kind regards,
>>> Ingrid
>>>
>>>
>>>
>>
>
>