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


On Mon, Jun 6, 2011 at 9:20 PM, Andy Brown <andy@the-martin-byrd.net> wrote:

I seem to be really missing something in all this talk about the transfer of
OOo.

1: What would TDF do with the code?  At this point in time LibO is way ahead
of OOo in features and code clean up, from the patches flying in the dev
list.

2: What would TDF do with the OpenOffice.org name and trademarks?

3: Would they rename LibreOffice to OpenOffice.org? If so why, since
LibreOffice has spread like it has?

4:  Why is TDF trying so hard to block the proposal with ASF?  I guess
answers to the above will answer this one.

Thanks
Andy


I think it is less about the code itself and more about avoiding
fragmentation and duplicated effort.  TDF would become of the official
home of OpenOffice.org.  Instead, what we are looking at one group
having the name and official control of the code base, and the other
having the vast majority of the community, developers, and
infrastructure.  That will confuse people who have grown use to the
OpenOffice.org name.

-Todd

-Todd

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