-
Notifications
You must be signed in to change notification settings - Fork 1
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
licence #4
Comments
I'd be happy to switch, but I think you'll find CRAN recognizes the use of CC0, available.packages(fields = "LICENSE") %>%
as_data_frame() %>%
select(Package, License, Repository) %>%
filter(License == "CC0") |
You are absolutely right of course, what I meant, and I should write a bit less terse, is that I thought the creative Commons licenses are not meant for code. Choosalicence.com gives cc as a option for if you don't have software. This is a minor point though |
https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software CC0 is GPL compatible according to FSF. Technically CC0 isn't a license but rather a public domain definition, and one which has paid more attention to international legal language than the very terse MIT. ( Given that R packages can distribute data, vignettes etc as well as source code, it's not always obvious what the source code license of the package covers, though that's no issue here). On the other hand, OSI rejected the current CC0 license after lengthy debate due to patent questions, so perhaps we should switch to something more conventional. Being at Berkeley I'm partial to BSD-2 ;-) |
All right =-) |
I think you can't actually use the cc0 licence , probably a MIT licence would be better.
The text was updated successfully, but these errors were encountered: