2011/6/4 Jesús Corrius <email@example.com>:
As if understanding and using the "old" OOo build mechanisms which have been
somewhat adapted at LO wasn't hard enough.
As a user (with just a tiny contribution) I really wish that OO.o
would just die already.
It is not "just" that the current community are much more friendly and
open to contributions
now, it is also the codebase that is starting to become more sane and
organized / accessible.
In a while, it may even build without requiring your own Cray
supercomputer and two PhDs.
Why would people want to go back to the java-dominated "obscure build
system land" that
has cost so much to the project already?
With TDF I think LibreOffice can make the equivalent of Netscape ->
For me the sane thing for ASF is to either donate the OO.o
name/trademarks in turn to
TDF, so that maybe we can have the equivalent of gcc -> egcs -> gcc
the existing marketing efforts for OO.org don't go to waste, or just
drop the whole thing
and let it die in peace.
I hope even IBM can see the light and start contributing to
LibreOffice instead of
trying to maintain the ugly beast that was OO.o on its own, or trying
to divide the
community (and thus generating bad publicity for both IBM and Oracle in the end,
Go Libre Office! We users love you! :) :)
Unsubscribe instructions: E-mail to firstname.lastname@example.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
Impressum (Legal Info)
: 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