[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Retaining History for incoming EE4J Projects



On Sun, Jan 14, 2018 at 9:35 PM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:
On 2018-01-14 10:19 AM, Mrinal Kanti wrote:
When the older versions are removed, we may also lose track of the initial contributors. Given the fact that earlier versions were released under GPLv2 (with CE) and newer versions can also be used under EPL, doesn't that require consent from ALL initial contributors?

Contributors signed the Sun (later Oracle) Contributor Agreement which provides Sun/Oracle with joint ownership of the contributions. All necessary consents and licensing issues have been taken care of.

Yes, joint ownership doesn't diminish the importance of consent from those initial contributors. Thanks for your assurance that it has been taken care of.


I assume that Oracle would have cleared all license related issues but want to know if it would suffice for indemnification should the need ever arise in future.

What indemnification? No open source license past, present or future provides an indemnification.

I was contemplating on the scenario where indemnification may be sought by the Eclipse foundation if any of the initial contributors (whose consent may have been missed) ever challenge the transition/inclusion of the EPL license.


Do we have any provision for tracking initial contributor consent publicly, just to be on the safe side?

No, as none is required.

--
Mike Milinkovich
mike.milinkovich@eclipse-foundation.org
(m) +1.613.220.3223



-Mrinal.
Â
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community