[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[iot-pmc] [CQ 18809] com.augustcellars.cose.cose-java-0.9.7
|
http://dev.eclipse.org/ipzilla/show_bug.cgi?id=18809
Kai Hudalla <kai.hudalla@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kai.hudalla@xxxxxxxxxxxx
--- Comment #7 from Kai Hudalla <kai.hudalla@xxxxxxxxxxxx> 2019-01-30 08:45:00 ---
(In reply to comment #4)
> So should that become code of the Eclipse Californium project (as the package
> name suggests)? Or should is still be an external dependency, but hosted inside
> the californium repository?
>
> I think the he first case, you would need to the change the license as well. In
> the latter case, it should live in a different package name (the original one).
>
I do not see why we shouldn't be able to include code from other projects in
the Californium code base under its original license. IMHO the only thing to
make sure is that the license is compatible with the EPL 2.0. We need to comply
with the terms of the license when distributing Californium, of course, but
that should be no different from all of the other (external) dependencies we
are using.
I agree that it would be even easier, if we could get written consent from the
original authors to re-distribute the code under EPL 2.0 but that is not a
requirement FMPOV.
--
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.
