On Tue, Jun 14, 2011 at 8:09 AM, Greg Stein <gstein@gmail.com> wrote:
You describe how all the committers and people on the steering
committee know these details. Well, of course. But what about all the
people at Apache who are trying to learn about the work you guys have
done here? Trying to learn the details of your Foundation, its
organization, and its (current) backing association? Trying to learn
who handles your donations, and how those proceeds are disbursed?
If you had come up with a plan of merging the foundations, all these details
would have been worked through. I don't think it matters now given the fork.
BRM, Jim, and I are trying to say that that information is opaque. It
takes direct involvement from Florian to achieve understanding.
You should have gotten your question answered before the proposal was
submitted for a vote.
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?
-Keith
--
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.