-
Notifications
You must be signed in to change notification settings - Fork 86
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
Change license #52
Comments
do we need to triple license it? i think |
MPL-2 is my favorite, and it doesn't hurt to just have them all ORed. That works as anyone can pick the one that fits them best. |
ACK, from my point of view, the more options the better. :) |
I went ahead, and fixed last project that was still at |
This is great, but you should make a LICENSE file explicitly so people looking at the project can see it. Or at least add it to the README. |
A LICENCE file is best. Github parses the file to give a quick overview of rights and obligations, as well as tagging the entire repo with the licence. |
I'm planing to migrate to:
everywhere. Just to give people more choice. I did in digest crates already, before releasing.
@Dylan-DPC @rffrancon . Ack? :)
The text was updated successfully, but these errors were encountered: