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

On Tue, Jun 14, 2011 at 2:40 PM, Greg Stein <> wrote:

We got our answer (before the vote) because Florian explained it. Our
point is that other people visiting the site will not have Florian's
attention. This has nothing to do with Apache, except by way of
example and that Florian was engaged. Others will not be so lucky.

It isn't very frequently that people with the OpenOffice trademark come

I don't think the questions that I posed had anything to do with
"merging", but simply the kinds of curiosity that TDF supporters may
have (or those who may be interested in *becoming* supporters).

They are irrelevant to you now that you aren't merging, and they would only
have been relevant to you if you had merged, and they aren't relevant to
typical people in the community so you can imagine why it is low priority.

Our goal is not to "beat" you. This is not a competition. That is not
how Apache operates.

Your goal is not to beat LO, but by choosing a fork you make cooperation
difficult via license incompatibilities and social engineering. So if you
aren't cooperating or competing then what word would you recommend?

We want to cooperate.

Forking makes cooperation more expensive. Your intentions are less important
than your consequences.


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.