Rémi,
I believe (am pretty sure) that in order to move source code to Eclipse
and to change the license of that code to EPL, all the copyright holders
(all people who ever contributed anything to the source) must agree to
the license change. Without that agreement, you can't change the
license regardless of how much you've added to the code. No amount of
change will eliminate the contributions of the original copyright holders.
Regards,
Ed
On 06.07.2017 10:24, Rémi Druilhe wrote:
Hello incubation mailing list,
We are in the process of providing a new set of modules from our
internal project to the Eclipse IP review for putting them public.
In particular, we use an old version of a GPL library, i.e.,
nrjavaserial. For our own purpose and to integrate it in our project,
we retrieved the source code of this 3rd party library and started to
modify it. At some point, we asked ourself if the newly provided
library is still under GPL because a major part of the code as been
re-writed (even if we don't know the delta between the old one and the
new one).
My question is: is this new library still under GPL despite major
modifications or can we say that this is a new library that can be
pushed under Eclipse license ? At which point a modified library can
be considered as new and independent from the initial library?
I think I already know the answer but I wanted to ask anyway. Just to
be sure.
Thanks,
Best regards.
--
Rémi DRUILHE
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
