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


And finally, whether it would make any sense from the technical point of view for LibreOffice 
contributors to even try to participate in OOo at ASF depends very much on what actually ends up 
there, and in what direction it is taken by the presumed main driving force, IBM. For all we 
know, it might be that the code that is eventually dumped in ASF's SVN (!) is a subset that 
doesn't even build, and then IBM starts adding its own hitherto proprietary stuff including build 
mechanisms that makes it into a completely different beast than what we are used to. I suspect 
lots of Java is involved, and that is not necessarily that popular around here. As if 
understanding and using the "old" OOo build mechanisms which have been somewhat adapted at LO 
wasn't hard enough.

Good point, Tor. Is the source code available somewhere already?
I wouldn't join any Open Source project if I can't see the source code first :)

-- 
Jesús Corrius <jesus@softcatala.org>
Document Foundation founding member
Mobile: +34 661 11 38 26
Skype: jcorrius | Twitter: @jcorrius

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