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


Got a couple of questions.

(1) I heard that OpenOffice is restricted from re-using code from
LibreOffice because Oracle insists on broader licenses than LO developers
are willing to give, but the reverse is not true. So, from this aspect LO
can only get stronger while OOo stagnates. Is this accurate?

(2) According to what I've read so far, most of the work to create and
maintain OpenOffice was done by a team of developers originally working for
StarOffice, later bought by Sun, in turn bought by Oracle. Outside
volunteers working without pay contributed only a small portion of the code.

Other companies, notably Novell, are said to be stepping in for LO. Will
they dedicate comparable resources to maintaining and expanding LO as
StarOffice/Sun/Oracle did for OO? If not, will volunteers (enthusiastic
about being free of Oracle) be picking up the slack for LO, or is it too
early to tell?

--
View this message in context: 
http://nabble.documentfoundation.org/Two-questions-about-course-of-LO-tp2757230p2757230.html
Sent from the Discuss mailing list archive at Nabble.com.

-- 
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.