Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of andy@the-martin-byrd.net
 designates 204.16.46.6 as permitted sender)
Message-ID: <4E498786.6070400@the-martin-byrd.net>
Date: Mon, 15 Aug 2011 13:54:30 -0700
From: Andy Brown <andy@the-martin-byrd.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: [Repo][Proposal] OOO340 SVN Dump file import
References: <1313435596.4441.YahooMailClassic@web113504.mail.gq1.yahoo.com>
 <4E498131.8020803@gmx-topmail.de>
 <58cd7b787da3942f6e5e382312d485d8@tutopia.com>
In-Reply-To: <58cd7b787da3942f6e5e382312d485d8@tutopia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Pedro Giffuni wrote:
> On Mon, 15 Aug 2011 22:27:29 +0200, Ingrid von der Mehden
> <IngridvdM@gmx-topmail.de> wrote:
>> Am 15.08.2011 21:13, schrieb Pedro F. Giffuni:
>>> --- On Mon, 8/15/11, Rob Weir<apache@robweir.com> wrote:
>> [..]
>>>> ooo/trunk/core --- all the OOO340 stuff
>>>> ooo/trunk/l10n -- all the language stuff
>>>
>>> Please do the directory rearrangement in SVN. I have no
>>> objection to moving stuff but if it's possible to match
>>> the old history later on, having these changes out of SVN
>>> won't help.
>>>
>>
>> On 'old' OOo there are currently already two separate hg
>> repositories. No directory move within either of them was proposed.
>> Only a target directory for each repository needs to be selected. I
>> don't see how this should affect any history mapping later.
>>
>
> Ah .. It's OK then. (sorry as I'm mostly new to the codebase)
>
> Is there some development plan after the intial repo is done or
> can committers start making massive changes (merging branches,
> adding ports, etc ..) right away?
>
> Cheers,
>
> Pedro.

The first thing that has to be done is to see if we do a build to make 
sure that we received all the files.  The next step then is to see what 
can be changed to AL2 license and which files will have to be replaced 
with AL2 licensed files.  In the second step builds will have to be done 
to make sure that nothing is broken in the process.

At least that is my understanding.

Andy
(non-coder)