incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From drew <d...@baseanswers.com>
Subject Re: Next steps for Symphony and AOO
Date Tue, 12 Jun 2012 21:03:55 GMT
On Mon, 2012-06-11 at 21:08 -0400, Rob Weir wrote:
> As we wait [0] for the Symphony [1] code to be loaded into Subversion
> I think it would be good to start a discussion on "next steps" of how
> we can make best use of this contribution.
> 
> Hopefully you've had time to review the list of features on the wiki
> [2], install one of the binaries [3] , or maybe even download the
> source [4] and try to build it [5].
> 
> As will see by your examination, the Symphony code base has co-evolved
> with OpenOffice.org for several years now, and continued to co-evolve
> with Apache OpenOffice even recently.  Symphony has many features and
> bug fixes that AOO lacks.  And there are areas where Symphony is
> missing enhancements or bug fixes that are in OpenOffice.
> 
> Our challenge is to find the best way to bring these two code bases
> together, to make the best product.
> 
> I think there are two main approaches to this problem:
> 
> I.  Merge code, from Symphony, feature by feature, into AOO, in a
> prioritized order.  This is the "slow" approach, since it would take
> (by the estimates I've seen) a couple of years to bring all of the
> Symphony enhancements and bug fixes over to AOO.
> 

Hi Rob, others

May I break out one piece of that work and ask about that.

Is there a reasonably trusted estimate on the effort to move the Windows
accessibility enhancements from the Symphony code line to the current
3.4 line?

Thanks much for your time,

//drew

<snip>


Mime
View raw message