Skip to content
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

COPYING.md to LICENSE #2768

Closed
jzf2101 opened this issue Aug 16, 2017 · 4 comments
Closed

COPYING.md to LICENSE #2768

jzf2101 opened this issue Aug 16, 2017 · 4 comments

Comments

@jzf2101
Copy link
Contributor

jzf2101 commented Aug 16, 2017

We should change the name of our license file to be consistent across repos at Project Jupyter

@rolweber
Copy link
Contributor

Would that imply some re-formatting of the content? It's currently in markdown format, and probably won't be rendered as such by GitHub anymore if the file suffix changes.

Also, there's more in the file than just the license.

@danielskatz
Copy link

I was checking to see the license for this project, and was surprised not to find a license file in the repo, which led me to this issue. It would be good if there was a LICENSE.txt file that was just a text version of the license, which doesn't mean there also can't be a COPYING.md file that has some of what is now in the file (except the license) and points to LINCENSE.txt

@sammyrTX
Copy link

Hi! Would it be okay to just copy the contents of the jupyter/LICENSE file into a jupyter/notebook/LICENSE.txt file and then updating the existing notebook/COPYING.md file to reference the new file (as suggested by @danielskatz)? Or are there any additional requirements for this issue? Thanks!

@jtpio
Copy link
Member

jtpio commented Jun 20, 2023

Closing as the current LICENSE is aligned with the other Jupyter projects: https://github.com/jupyter/notebook/blob/main/LICENSE

@jtpio jtpio closed this as completed Jun 20, 2023
@jtpio jtpio added this to the Reference milestone Jun 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants