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




On 01/04/2011 10:37, Charles-H. Schulz wrote:
Hello,

@Mark: you write that you were able to see the source code of OpenOffice
before Oracle bought Sun, but OpenOffice was Open Source anyway, so
anybody could see the code. Did I get your point right?

You did get it right Charles - and yes it was fully open-source so I
had downloaded the whole lot. Sun just guided me to "relevant bits" so
I could look them over. I've not done that with the new codebase
because the old one put me off it so much, but am delighted to hear it
is being cleaned up.

Added to this, let me say my impression is that the more technically
capable resources (ie. people) are working with LibreOffice rather
than OpenOffice and worries others might have of Oracle "flinging
resources" at Ooo to make it outstrip LibO are almost certainly unfounded.

Yes, I am biased, but I have no doubt at all that the fork to LibO was
right, reasonable, appropriate, timely and inevitable. It is, granted
in my personal opinion only, the best thing that could possibly have
happened to Ooo to ensure its future.


-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.