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

DF programmers should join the Apache OO committee merely to be aware
of activities in this product. LO should remain separate as a full GPL
product. Presumably, if DF members become aware of feature X becoming
imminent in apache OO, they can make a proposal for a similar feature
to be copied/improved in LO. The analogy is opera introducing tabbed
web pages in a browser and firefox later introducing the same

More separately developed ODF compliant products in the market is a
good result, just like there are numerous gnu/linux distributions for
users to choose. The proliferation of many ODF products gives powerful
confidence to users that if apache OO (any other ODF compliant
product( disappears, the user can switch to using LO. It should be
remembered that this cannot occur with m$o and this is the single most
dominant benefit of numerous ODF programs to the user. It is the
"killer reason" to use LO.

In summary, please do not merge apache OO (or any non-(L)GPL) code with LO.

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.