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

Create LICENSE #134

Closed
wants to merge 1 commit into from
Closed

Create LICENSE #134

wants to merge 1 commit into from

Conversation

fm75
Copy link

@fm75 fm75 commented Aug 26, 2017

Fixes #133

@jzf2101
Copy link

jzf2101 commented Aug 26, 2017

Could someone confirm we can have a license on the website?

@takluyver
Copy link
Member

We can, but I think it should be a content license (like the CC family) rather than a code license like BSD.

@fm75
Copy link
Author

fm75 commented Aug 28, 2017

@jzf2101 - You are probably right about the content license. We did many PRs as part of a sprint after jupytercon. I think it would be best to let Jessica work out the details on this and the similar PRs.

@Carreau
Copy link
Member

Carreau commented Sep 7, 2017

We can, but I think it should be a content license (like the CC family) rather than a code license like BSD.

Also if the license have a date it should likely not be 2017 but the first date the website was released.

@ivanov
Copy link
Member

ivanov commented May 15, 2021

Hey there, I'm going through old issues and it seems to me that it makes sense to close this one. Seems like we reached consensus here that BSD 3-clause is not the license we'd want to use for the website assets.

Thanks everyone and happy hacking! :bowtie:

@ivanov ivanov closed this May 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add LICENSE
5 participants