search

OpenHFT / Chronicle-Values

http://chronicle.software
Other
104 stars 38 forks source link

Licence Inconsistency #13

Closed sirinath closed 8 years ago

sirinath commented 8 years ago

The mail license file https://github.com/OpenHFT/Chronicle-Values/blob/master/LICENSE.adoc says ASL 2.0 while all the file headers has been updated LGPL: https://github.com/OpenHFT/Chronicle-Values/commit/20cc558c5132ba75e48649684e86727722492a48

sirinath commented 8 years ago

I guess this issue is there in other projects. E.g. https://github.com/OpenHFT/Chronicle-Engine/blob/master/src/main/java/net/openhft/chronicle/engine/Chassis.java

sirinath commented 8 years ago

@peter-lawrey @leventov Just to follow up on the issue the the source headers. E.g. https://github.com/OpenHFT/Chronicle-Values/blob/master/src/main/java/net/openhft/chronicle/values/Align.java#L1

leventov commented 8 years ago

@sirinath Chronicle Values are still LGPL, they were updated by mistake when most (but not all) Chronicle projects moved to Apache 2.

Chronicle Engine is now Apache 2.

sirinath commented 8 years ago

But this file says ASL 2.0: https://github.com/OpenHFT/Chronicle-Values/blob/master/LICENSE.adoc

leventov commented 8 years ago

@sirinath thanks, this will be fixed

sirinath commented 8 years ago

Also is it possible to consider ASL 2.0?

sirinath commented 8 years ago

Also it is possible to but out which library is under which license and a promise that the licensing will not change for the parts under ASL 2.0 so users will not accidentally start suing libraries which are incompatible with licensing policies for a particular project or it does not change mid way into a project.