On Sat, Jun 4, 2011 at 12:00 AM, plino <pedlino@gmail.com> wrote:
It seems that the logic here is: code for OpenOffice and you are contributing
to both projects, code for LibreOffice and you only contribute to one :)
http://www.robweir.com/blog/2011/06/apache-openoffice-how-to-get-involved.html
I would say, If you are adding to ooo, you are not only contributing
to both, but also to ibm\s fork and any other fork.
but seriously, if you are the original author you can in theory apply
your patch to both, or publish your code standalone so it can be used
by everyone.
Also, seeing what Apple, and Microsoft do to public domain code (DRM
and lockdown) makes me want to not allow them to profit from my work,
at least if I am doing it on my free time.
Sure If i am being paid to work on something by a university or
research grant it might make sense to be public domain or Apache
licensed.
Of course, this discussion has been done a million times and everyone
has their preference, I am not going to convince anyone here.
mike
--
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
Re: [tdf-discuss] Re: Oracle contributes OOo Code to Apache Software Foundation'sIncubator · Varun Mittal
Re: [tdf-discuss] Re: Oracle contributes OOo Code to Apache Software Foundation'sIncubator · Mike Dupont
[tdf-discuss] Re: Oracle contributes OOo Code to Apache Software Foundation's Incubator · plino
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.