search

OpenHFT / Chronicle-Values

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

Licensing mismatch between source files and project license #31

Closed moore-ryan closed 3 years ago

moore-ryan commented 3 years ago

The root project license is defined as Apache 2.0 in LICENSE.adoc, but most source files still define the license as LGPL 3 in their headers (see Array.java for example). I see that there was a change done ~5 years ago to change the project license to Apache 2.0 (9805605d). Other OpenHFT projects also converted the headers to reference Apache 2.0 around the same time (see https://github.com/OpenHFT/Chronicle-Map/commit/1e1a086ea98add2695fe6233ae9acd43edb9b965) but this does not appear to have been done for Chronicle-Values.

Since LGPL 3 is not compatible with Apache 2.0 (at least so far as I understand), is the fact that the source headers still reference LGPL 3.0 a mistake?

moore-ryan commented 3 years ago

We're interested in using this (plus Chronicle-Map - these libraries fit our use-case very well) but unfortunately due to the licensing mismatch we're having some trouble getting Chronicle-Values cleared for use.

moore-ryan commented 3 years ago

I found https://github.com/OpenHFT/Chronicle-Values/issues/13 which seems to have raised this same concern - however, no action seems to have been taken regarding the LICENSE.adoc file.

moore-ryan commented 3 years ago

Thank you for the response. I see that https://github.com/OpenHFT/Chronicle-Values/blob/ea/pom.xml still contains a reference to the LGPL - is this also supposed to be Apache 2.0?