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

CC0 license #9

Merged
merged 2 commits into from
Oct 9, 2015
Merged

CC0 license #9

merged 2 commits into from
Oct 9, 2015

Conversation

jasongrout
Copy link
Member

As mentioned in #8 by @njsmith, it would be great to license the governance documents as CC0.

We'll need explicit assent from me, @ellisonbg, @Carreau, and @minrk. The one other author in the repo just fixed a link. @fperez, it probably wouldn't hurt to have your assent too, since you likely had lots of input, even if you aren't credited in the repo. Are there any others we need to get permission from?

Edit: CC0 is basically public domain, but explicitly waives rights for jurisdictions that don't have the concept of public domain. Basically, it tries to be as public domain as possible in all jurisdictions. See https://creativecommons.org/publicdomain/zero/1.0/

  • Matthias
  • Brian
  • Fernando
  • Jason
  • Jess
  • Damian
  • Jon
  • Min
  • Kyle
  • Thomas

The projectlicense.md file is to be used on project repos.  It is *not* the license for this repo.
@jasongrout
Copy link
Member Author

+1 for this PR, and I give my consent for a CC0 license.

@Carreau
Copy link
Member

Carreau commented Oct 8, 2015

I'm ok on relicensing to CC0.

@jasongrout
Copy link
Member Author

It seems that there is a general consensus. @jupyter/steeringcouncil: Please vote on merging this PR. We need at least 8 votes, and 2/3 majority for merging.

@jdfreder
Copy link

jdfreder commented Oct 8, 2015

Had to read about CC0 because I had never heard about it, but now I'm +1

@jasongrout
Copy link
Member Author

@jdfreder, I added a note about what CC0 is in the pr description above.

@ellisonbg
Copy link
Contributor

+1

On Thu, Oct 8, 2015 at 12:14 PM, Jonathan Frederic <notifications@github.com

wrote:

Had to read about CC0 because I had never heard about it, but now I'm +1


Reply to this email directly or view it on GitHub
#9 (comment).

Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger@calpoly.edu and ellisonbg@gmail.com

@jhamrick
Copy link
Member

jhamrick commented Oct 8, 2015

👍

@Carreau
Copy link
Member

Carreau commented Oct 8, 2015

Updated with checkbox list, to get a quick count.

@rgbkrk
Copy link
Member

rgbkrk commented Oct 8, 2015

👍 CC0

@damianavila
Copy link
Member

👍

@fperez
Copy link
Member

fperez commented Oct 8, 2015

Yes, I'm not credited in but I did have a lot of input :)

I'm +1 on CC-0 on these, I hope they get spread as far and wide as possible!

@minrk
Copy link
Member

minrk commented Oct 9, 2015

👍

jasongrout added a commit that referenced this pull request Oct 9, 2015
@jasongrout jasongrout merged commit 07643c6 into jupyter:master Oct 9, 2015
njsmith added a commit to njsmith/numpy that referenced this pull request Oct 9, 2015
We want to allow other projects to steal from us, like we stole from
Jupyter/IPython :-). This relicensing / public domain dedication is
possible because all text here is either by me (and thus copyright me)
or else taken from the Jupyter/IPython document, and their document is
also under CC-0 as per jupyter/governance#9
jaimefrio pushed a commit to jaimefrio/numpy that referenced this pull request Mar 22, 2016
We want to allow other projects to steal from us, like we stole from
Jupyter/IPython :-). This relicensing / public domain dedication is
possible because all text here is either by me (and thus copyright me)
or else taken from the Jupyter/IPython document, and their document is
also under CC-0 as per jupyter/governance#9
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.

None yet

9 participants