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


Johannes,
Perhaps this is not the place to insert myself, and if not, I will desist.
I think your question is a good one.  I think LO is a side-effect of this
desire for something seminally different.  Most people were mostly satisfied
with what OO.o could do.  The fear of being roped into a single Oracle
vision and a longing for what might be accomplished by a community driven by
community rather than subtle coercion are the drivers of the schism that
started TDF. (IMO)
A few years ago, There was a similar conversation which led to the formation
of the centralized polylingual support web site for OO.o.
I was one of the original team that drove that move.  The outcome, though
solving the issue of our site being controlled by a single individual, was
not what we had hoped.   We could not push past the work-a-day aspects of
getting the site up, similar to some responses here.
Where I went, and where you are going here, is into deeper strategy and
positioning of the organization. The deeper strategy gives the organization
legs. Without it, we have 1 software suite and we can never hope to have an
impact upon the world beyond stealing market-share from other similar
products.

Wolf Halton

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***

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.