-
Notifications
You must be signed in to change notification settings - Fork 43
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
Dual licensing #49
Comments
Just checking to see if there's been any progress on this front. |
The team seems happy to accommodate Fedora, but we're still discussing which exact combination of licenses to use. |
Hi Bas, were you able to reach a conclusion on this? |
I added a branch 'license' to tackle the issue; please check and comment. |
I am not sure how to handle the NIST files: ref/PQCgenKAT_sign.c |
It shouldn't be a problem to leave those as is, and make a comment in the README or LICENSE file that those files retain their original license. Downstream projects like OQS won't actually make use of those files in compiled libraries, so the resulting binaries will still be cleanly licensed. |
In liboqs we've gotten some feedback (open-quantum-safe/liboqs#1437) that the CC0 license is a barrier to adoption by some distributions. Would SPHINCS+ be willing to consider dual licensing to add another license? See also open-quantum-safe/liboqs#1388 (comment) for comments from the Fedora team.
The text was updated successfully, but these errors were encountered: