-
Notifications
You must be signed in to change notification settings - Fork 59
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
Re-license under GPL #5
Comments
@ergonlogic would the MIT or BSD be acceptable as well? (I've not really paid too much attention to the process of licensing of my own creations). Somehow (uneducated, first glance) GPL makes me feel a bit restricted. But I'm open to discussion. |
Certainly. The principal difference is whether you want derivatives to remain free also. |
I'd welcome a GPLv3+ licence. The process of licensing it as such is quite easy. |
An MIT license would be nice |
bump |
@airtonix The GPL doesn't restrict what you can do, just what others can do. The GPL is a great license, but so is MIT. I'm not a lawyer, but as I understand it, GPL enforces a "share-alike" type rule, while the MIT license doesn't. Don't take this as legal advice, though. |
Github authored an excellent human-friendly resource https://choosealicense.com/ for these kinds of decisions. 🙇♂️ |
CC licenses are not considered appropriate for software, according to: http://wiki.creativecommons.org/FAQ#Can_I_apply_a_Creative_Commons_license_to_software.3F. Unless you meant the license to only apply to the README...
They recommend a license from the FSF, which is basically some flavour of GPL.
As it stands, there are no software licenses that are technically compatible with CC.
The text was updated successfully, but these errors were encountered: