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


On Wed, Jun 8, 2011 at 2:11 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:

On 2011-06-08 2:04 PM, BRM wrote:
Like all the venom towards Oracle, OOo, and ASF that has been spewed
by TDF members and contributors on this topic over the last few days?

Very little of the negative reaction has been directed at the ASF,
mostly it is directed at Oracle...

Personally, I think it is silly - LibO obviously has moved way past
where OOo was, so it is imho a non issue...

Rest in peace, OOo... long live LibO!


I sincerely wish that this were the prevailing opinion.

With the time that has passed since the realization of the fork,
with the time it will take before an OOo-ASF product becomes a
reality, OpenOffice.org is in serious trouble. The last release was based
on momentum from the time of the fork.

I concur; let's take care of improving and fixing the present bugs in
 LibreOffice-3.4 and stop worrying over things that we are unable to
change.

All of this energy in this list would be better spent on LibreOffice.

saludos,
Richard.

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