Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add proper licence #8

Open
ismell opened this issue Jul 7, 2020 · 4 comments
Open

Add proper licence #8

ismell opened this issue Jul 7, 2020 · 4 comments

Comments

@ismell
Copy link

ismell commented Jul 7, 2020

It would be nice to have this GPL2 or BSD licensed. This way it could be included in other projects.

@rfanner
Copy link

rfanner commented Feb 24, 2021

+1 on having a proper licence.

My feeling is that MIT might be a sensible choice, as that would be consistent with the C++ code by Austin Appleby that was ported to C for this library. (https://sites.google.com/site/murmurhash/).

From the above:

"All code is released to the public domain. For business purposes, Murmurhash is
under the MIT license."

GPL2 would add restrictions beyond "public domain" to make it copyleft, which would potentially impact wider adoption.

@eeliu
Copy link

eeliu commented Apr 10, 2024

ping

@otac0n
Copy link

otac0n commented Apr 16, 2024

This issue needn't be open in my opinion. Using it only exposes you to a claimed public-domain port of an MIT licensed library. It is MIT licensed.

@rfanner
Copy link

rfanner commented Apr 16, 2024

@otac0n agree the exposure is limited.

That said, non-standard or less specific copyright text has a way of cropping up as effort whenever SBOM open source compliance checks need to be done in a commercial context.

Specific license texts like MIT are quick to review/re-review, as tools and people doing FOSS compliance have a common understanding of what these mean.

Non-specific license texts, on the other hand, frequently trigger the need to (repeat) a deeper look at the code and the provenance of the code to establish that commercial (or other) usage is indeed compliant.

It's certainly not a deal-breaker to use "public domain" code, but clearer licensing is always nice to see.

(Provided that license isn't GPLv2, as that would erode previous usage rights on later software versions published in some commercial contexts :) ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants