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 rgardler@opendirective.com
 designates 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E14E6F1.8020700@oracle.com>
References: <BANLkTi=HV9uyQzvADD0KSLFcoPesdjfu1w@mail.gmail.com>
	<1309381916.82460.YahooMailClassic@web113503.mail.gq1.yahoo.com>
	<BANLkTikDx3yVjKZJcr57o95+H=bevXn2jA@mail.gmail.com>
	<00c701cc36ec$5dab9750$1902c5f0$@acm.org>
	<BANLkTik1v+arZ8We2Z=WKaQCjQGvjWn9yw@mail.gmail.com>
	<010001cc3741$51c88740$f55995c0$@acm.org>
	<BANLkTikJJO7YPoa0t7kNMmMX-J8GKrx+ZQ@mail.gmail.com>
	<00d001cc380f$98fec4c0$cafc4e40$@acm.org>
	<1309664343.19050.3.camel@rigel>
	<1309666612.2224.4397.camel@linux-krcc.site>
	<4E14E6F1.8020700@oracle.com>
Date: Thu, 7 Jul 2011 12:09:37 +0100
Message-ID: 
 <CAKQbXgAVyt2pDNYvUcgASXJ_Zs__bopMCaquayzRZUQpHOrhNA@mail.gmail.com>
Subject: Re: OOO and LibreOffice.
From: Ross Gardler <rgardler@opendirective.com>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 6 July 2011 23:51, Andrew Rist <andrew.rist@oracle.com> wrote:
>
> To date the LibreOffice crew has taken the effort to merge in changes fro=
m
> the OOo code line, for each release.
> The most obvious and best way to collaborate in the future is to write go=
od
> code, and make it worth their while to integrate it into LO.
> The more compelling the development effort at Apache, the more likely it =
is
> reused by LO.
> This also leads to the situation where they have an interest in pushing
> changes into the AOOo code line, to simplify their future merges.

I agree 100% with this.

My question, as someone who does not know the OOo code, is are there
any obvious places in the code where this is likely to happen?

A strong Apache project has the broadest possible community of users.
Some of these users become contributors and some of those become
committers.

I wonder if there are any units of code that can be separately
packaged in order to allow them to be included in downstream projects
without "merging cnhanges" into a separate code tree?

I'm a Java weenie, so I think in terms of JARs that can be reused
easily. Is there any scope in the OOo project for similar library
reuse? If so where is the low hanging fruit?

Ross

>
> Andrew
>
> On 7/2/2011 9:16 PM, Graham Lauder wrote:
>>
>> On Sat, 2011-07-02 at 23:39 -0400, Ted Rolle, Jr. wrote:
>>>
>>> Perhaps I'm jaded, but when you have data in two places, you can be sur=
e
>>> of one thing: =A0they're both wrong.
>>
>> Conversely, they are both right for their respective supporters and the
>> reasons that each cite are also right, for each respective audience
>>
>>> I fear that the *Office camps will be in some sort of competition.
>>> Competition means that there is a winner, and a loser.
>>
>> Not always true, if each iteration serves a unique market. =A0They can
>> still be in competition for bragging rights but at the same time only
>> competing for a common set of the market that is smaller than their main
>> market, in this case I believe it will be Consumer on one hand (LO) and
>> Enterprise on the other (OOo), IMO, MSO will be the big loser.
>>
>>> The good thing is that one will survive and become the de-facto
>>> standard.
>>>
>>> Prove me wrong!
>>
>> I'm hoping we will, either way we live in interesting times
>


--=20
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com