incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: OpenOffice: were are we now?
Date Mon, 06 Jun 2011 00:37:00 GMT
Simon Phipps <> wrote on 06/05/2011 07:49:41 PM:

> From: Simon Phipps <>
> To:
> Date: 06/05/2011 07:50 PM
> Subject: Re: OpenOffice: were are we now?
> On Mon, Jun 6, 2011 at 12:38 AM, Richard S. Hall 
> >
> > I don't think the proposal here is for OOo to enter incubation and 
then try
> > to copy everything that TDF/LO does. I assume the proposers have a 
> > for where they want to go, even though they may be starting from the 
> > place.
> >
> I'm not clear how safe that assumption is - that's what I have been 
> to see explained for quite a while actually. Rob has been strong on
> long-term abstract vision (clearly more omniscient than me), but any 
> specifics of what (& how) is going to happen in the immediate future in
> terms of maintaining the important consumer end-user presence
> delivers, things get pretty fuzzy and hand-wavey.

Perhaps you missed it in the thread on end-users. Here is a link:

IMHO, the growth in end user adoption will happen in the enterprise.  That 
will require support mechanisms that are far beyond what LO or Apache can 
give. But it will be provided by a mix of consultancies based on free or 
libre versions of the code, as well as by commercial;, mixed-source 
versions built upon the Apache code. 

In parallel to that, we'll continue doing the same thing that OOo did for 
the last 10 years, provide documentation, tutorials, FAQ's, user forums, 
etc., on  The intent is to keep that as the 
end-user portal.

I'd be interesting in hearing if the TDF has something stronger to offer. 
Were you planning on providing 24x7 phone support?  Visiting customers to 
do migrations?  Provide 14 day guaranteed patch support?  Provide onsite 
training?  Of course not.  Supporting the full range of end users requires 
an entire ecosystem of partners.  I believe that the Apache 2.0 license 
facilitates growing that kind of ecosystem.  We've seen this happen with 
many other Apache projects.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message