Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On Sat, Jan 22, 2011 at 16:47, Tom Davies <> wrote:

I think Oracle have decided they are competing with LibreOffice but so far we
seem to be co-operating with them.  It would be wise for us to
1.  Beat them to the finish line.
2.  Keep aware of what they are doing, odd stats can help sometimes
3.  Keep going the way we have been, rapid growth and development in
infra-structure and support along with excellent coding development
4.  Keep co-operating as long as they let us.

After initial release we wil, of course, keep developing in all areas so rushing
final release and getting it out there wouldn't hurt us.  We don't have to worry
about corporate clients right now but they do.  So a 2nd release in another
couple of months wouldn't hurt us but it's almost unthinkable for them.
Regards from
Tom :)

Are you suggesting that upstream (OOo) bugs are fixed independently in
LibreOffice? Or are you referring to LibreOffice specific bugs? For
that matter, is LibreOffice still pulling from OOo upstream? If so,
are bugs fixed in LibreOffice being submitted as patches to the OOo
bugtracker, or is it up to Oracle to come asking for them? I think
that it would be wise of LibreOffice to file the patches, and I am
willing to take that responsibility if needed.

Dotan Cohen

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.