-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
CC-0 for cookiecutters #24
Comments
@SylvainCorlay Do we have documentation for that? |
Code snippets in documentation and examples are usually cc-0 so that people can use them to create software with other licenses. I am posting this from my phone so I cannot look it up easily but there have been discussions in other jupyter subprojects. |
I'm ok with that. I just want us to confirm this and docuement it for future reference. Will make changes following the Tuesday meeting. |
@fm75 would you be interested in making this change? |
I'm happy with any of my contributions to this cookiecutter to be considered public domain (e.g., CC-0). In other words, from my standpoint (i.e., my contributions here), I'm happy to have people use the output of the cookiecutter in whatever way they want. |
I support to the re-licensing to CC-0. |
I support the re-licensing to public domain/CC-0 too. |
In our JupyterLab dev meeting today, @vidartf pointed out that the cookiecutter generates an extension where the copyright is assigned to the person that ran the cookiecutter. The legal assumption here is that, as the copyright holder, presumably the person that ran the cookiecutter could then relicense their project however they wished. That's an interesting approach to this issue. I'm really curious if other projects (or lawyers) have thought of this approach, and if it is legally sound. |
If it is sound, we should probably add a note to the top-level readme, indicating to contributors the legal theory here... |
I'm for making all the code in this repo CC-0, since it should remove any doubt about what the licenses cover or not, and it will also make the license in the output make sense (CC-0 can, AFAIU, be re-licensed like that without issue). #notalawyer |
BTW, here's the list of committers according to GH: https://github.com/jupyterlab/extension-cookiecutter-ts/graphs/contributors |
A license file was just added (BSD 3-clause).
I think that for most cookiecutters in the org, we opted for CC-0 #23
The text was updated successfully, but these errors were encountered: