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

Permissive Relicensing #44

Open
JeremyRubin opened this issue Aug 20, 2018 · 2 comments
Open

Permissive Relicensing #44

JeremyRubin opened this issue Aug 20, 2018 · 2 comments

Comments

@JeremyRubin
Copy link

Suggesting that you might relicense this project under MIT or BSD or Public Domain.

Many cryptographic libraries are licensed as such (e.g., secp256k1, libsnark, nacl, etc).

This makes it easier to include them in a diverse set of projects, and is more likely to get attention from outside contributors.

GPL is a fine license and has many benefits, so I understand the desire to use it, but for crypto libraries something more permissive is probably appropriate.

@palladionIT
Copy link

Any update/comment on this? I am working on a project where this might become very relevant. Thanks!

@omershlo
Copy link
Contributor

We can try to help! lets discuss it in DM, please reach out to me via email : omer@zengo.com or telegram: omershlo

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

3 participants