Repeat.
On 06/06/2011 06:05 PM, NoOp wrote:
On 06/04/2011 05:10 PM, Jim Jagielski wrote:
...
Whether OOo lives or dies in Apache, Oracle has made it abundantly
clear that this is it... This is one promise I fully expect Oracle
will keep :/
Interesting...
Could you clarify that statement?
1. @ASF: What happens to OOo if ASF votes *not* to accept the OOo
project into the incubator? And it that is the case, what happens to the
OOo software that has been granted to the ASF by Oracle?
...
Was it your intention to pop into this list with:
Hello!
I have also just subscribed to both discuss@ and steering-discuss@
in hopes that if there are questions here regarding OOo, LOo, TDF
and the ASF, I can respond. I'm also here to also ask that if
you feel more comfortable emailing me directly, that is fine
as well.
and no longer respond to questions?
The questions are, IMO, valid and are important - both for OOo and TDF/LO.
--
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
[tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice · NoOp
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice · AndrĂ© Schnabel
Re: [tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice · Greg Stein
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.