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 CC0-LICENSE #528

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
@jamesray1
Collaborator

jamesray1 commented Jan 18, 2018

Creating a CC0 license allows for the content of this wiki to be placed in the public domain. This will help to allow for the dissemination of information about Ethereum, the Ethereum ecosystem and Web 3 to the public, in a completely permissive manner. I have updated the home page and created a CC0 license page, adding a contributor license agreement to help enable future changes to be under a CC0 license and referring to this PR to acknowledge those who have and have not agreed to a CC0 license, where those who have not agreed to a CC0 license have all rights reserved for their contributions.

@pirapira

This needs permissions from the copyright holders.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Feb 13, 2018

Dear contributors, please agree to using a CC0 public domain license. Pinging those who have contributed above 10 commits (possibly not including everyone that committed to the Wiki, which can't seem to be tracked as easily). (I agree.) @frozeman, @vbuterin, @chriseth, @debris, @pedrosoftz, @LianaHus, @stephantual, @xcthulhu, @shin1hi, @ryoumh, @ghasshee, @heikoheiko, @ethers, @CJentzsch, @LefterisJP, @janx, @Worker-GER, @subtly, @obscuren, @gavofyork, @TOMOAKI12345, @zelig, @tgerring, @btceth, @yann300, @Gustav-Simonsson, @EtherKorea, @jorisbontje, @nagydani, @aeronbuchanan, @arkpar, @qualiabyte, @kurihei, @maurycyp, @ethernomad, @thehighfiveghost.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Feb 13, 2018

Also pinging those who made 10 or less commits but made many additions in lines of code (which is actually a better way to sort): @ruchevits, @zaq1tomo, @jesuscript, @cubedro, @AdrienLedoux, @chfast, @utamaro, @ramvi, @phonikg, @benadrasni, @step21.

@debris

This comment has been minimized.

Contributor

debris commented Feb 14, 2018

I agree.

@ramvi

This comment has been minimized.

Contributor

ramvi commented Feb 14, 2018

I very much approve of this! (kind of thought it was under creative commons already)

@EtherKorea

This comment has been minimized.

EtherKorea commented Feb 14, 2018

@ruchevits

This comment has been minimized.

Member

ruchevits commented Feb 14, 2018

@LefterisJP

This comment has been minimized.

Contributor

LefterisJP commented Feb 14, 2018

Cool with me

@shin1hi

This comment has been minimized.

Contributor

shin1hi commented Feb 14, 2018

@jorisbontje

This comment has been minimized.

jorisbontje commented Feb 15, 2018

Agreed.

1 similar comment
@step21

This comment has been minimized.

Contributor

step21 commented Feb 16, 2018

Agreed.

@Nydrey

This comment has been minimized.

Nydrey commented Feb 16, 2018

@chriseth

This comment has been minimized.

Contributor

chriseth commented Feb 16, 2018

I agree.

@CJentzsch

This comment has been minimized.

Contributor

CJentzsch commented Feb 16, 2018

Agreed

@chfast

This comment has been minimized.

Contributor

chfast commented Feb 20, 2018

I agree.

@kurihei

This comment has been minimized.

Contributor

kurihei commented Feb 20, 2018

Agreed

@cubedro

This comment has been minimized.

Member

cubedro commented Feb 20, 2018

I agree

1 similar comment
@yogeshkampalliwar

This comment has been minimized.

yogeshkampalliwar commented Feb 20, 2018

I agree

@TOMOAKI12345

This comment has been minimized.

Contributor

TOMOAKI12345 commented Feb 20, 2018

I agree.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Feb 21, 2018

16 agreed so far, 47 in total to agree, leaving 31 to agree. Hmm, I could use the git commit log to send one-on-one email follow-ups. I'll wait another week or so.

@ethernomad

This comment has been minimized.

Contributor

ethernomad commented Feb 21, 2018

I agree

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 8, 2018

To save using the Git commit log to email people (who should've got emails any way), I suggest to merge this, since nobody has objected, and there has been ample opportunity for objections. @pirapira

@pirapira

This comment has been minimized.

Member

pirapira commented Mar 8, 2018

The majority hasn't replied about CC0. I cannot turn their silence into a license.

@chriseth

This comment has been minimized.

Contributor

chriseth commented Mar 8, 2018

Oh come on, it's just two letter swaps! ;-)

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 9, 2018

I was thinking of the process of rough consensus (as explained in this document: https://www.rfc-editor.org/rfc/rfc7282.txt) where you give people an opportunity to make objections, and eliminate them if they can be fixed technically, otherwise if not then the proposal can be rejected and an alternative can be pursued. GIven that there has been ample opportunity for people to object, and none have done so, I thought it would be OK to merge this license.

@ghasshee

This comment has been minimized.

Contributor

ghasshee commented Mar 9, 2018

What is the probability that the estimated judgement is agreement by the about one-third samples with 0% rejection which is selected (answered) from the whole entities ?

What kind of distribution should we select for modeling the estimation ?

I know there are still problems of the way of broadcasting discussions and this is no-random selection of samples, that the probability I question seems to be very high, and that it is still a dangerous decision with such an estimate which has faults.

@ghasshee

This comment has been minimized.

Contributor

ghasshee commented Mar 9, 2018

Maybe I know that the consensus likely to be high because of the probability generated by 0% rejection.
And now I read the RFC7282 very roughly.

I felt that there seem to be no explanations of the modeling formally.
This might be the difficulty we are facing.

I am afraid I also know my comments are quite trivial :-)

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 9, 2018

Yeah it's worth the read.

There's a few ways to look at it: get rough consensus (no objections that can't be solved), get the majority to approve, or get everyone to approve. I suggest that we use a rough consensus model. If someone lashes out and says: "hey, you didn't get my approval to change the license", then we can say, well we gave you ample opportunity to make an objection, but you didn't, so we chose to assume that it would be OK to merge the license.

Otherwise I have to nag people by sending them an email asking them to explicitly state that they approve using a CC0 license.

@ghasshee

This comment has been minimized.

Contributor

ghasshee commented Mar 9, 2018

I think the problem is in the deeper area,
Because ethereum is the first attempt for the global consensus machine which no one has ever attempted with Nakamoto Consensus.
Most people here who built the wiki documents are interested in the 'formal process' of the consensus.

So, rough consensus mechanism seems based on the fundamentals of probability and statics, and maybe the people in this community know deeply about it. But they do not have the concrete tool which will adopt rough consensus into the global consensus.

@jaekwon

This comment has been minimized.

jaekwon commented Mar 12, 2018

"I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain."

@ebuchman

This comment has been minimized.

Contributor

ebuchman commented Mar 12, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain

@Leo-Mu

This comment has been minimized.

Contributor

Leo-Mu commented Mar 13, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.
Sorry to be a bit late.

@drcode

This comment has been minimized.

Contributor

drcode commented Mar 13, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

1 similar comment
@anthony-cros

This comment has been minimized.

Contributor

anthony-cros commented Mar 13, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

@Neurone

This comment has been minimized.

Contributor

Neurone commented Mar 15, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain

@jamesray1

This comment has been minimized.

@btceth

This comment has been minimized.

Contributor

btceth commented Mar 15, 2018

@pirapira

This comment has been minimized.

Member

pirapira commented Mar 15, 2018

Now I wonder if there is any significant contribution left.

Perhaps, it's easier to add the license page-wise.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 15, 2018

I've already added it.

https://github.com/ethereum/wiki/wiki/CC0-license

However, I thought it would be good to get this merged, as a formality, and to be more legally enforceable.

If you see my tweet thread, I have pinged many contributors in descending order of contributions.

@pirapira

This comment has been minimized.

Member

pirapira commented Mar 15, 2018

@jamesray1 no, I meant to license some of the pages, whose authors have already agreed.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 15, 2018

Ah that is so much work to match up all the contributors that have agreed with the articles that they have contributed to. I think I'll pass on that task.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 15, 2018

If we can get all or even most of the contributors in that Twitter thread to approve a CC0 license, then I think it should be well and truly OK to merge.

@zaq1tomo

This comment has been minimized.

Contributor

zaq1tomo commented Mar 15, 2018

I agree.

@maurycyp

This comment has been minimized.

Contributor

maurycyp commented Mar 16, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

@hainesc

This comment has been minimized.

Contributor

hainesc commented Mar 16, 2018

I agree.

@jamesray1

This comment has been minimized.

Collaborator

jamesray1 commented Mar 16, 2018

I updated the home page and the CC0 license page, adding a contributor license agreement to help enable future changes to be under a CC0 license and referring to this PR to acknowledge those who have and have not agreed to a CC0 license, where those who have not have all rights reserved for their contributions.

@phonikg

This comment has been minimized.

Contributor

phonikg commented Mar 20, 2018

I agree.

@ryepdx

This comment has been minimized.

ryepdx commented Mar 22, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

@wimel

This comment has been minimized.

wimel commented Apr 24, 2018

I agree.

@fbehrens

This comment has been minimized.

Contributor

fbehrens commented Apr 28, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

@Amorn-Kingthong

This comment has been minimized.

Amorn-Kingthong commented May 1, 2018

ARGGG!:! i want a new mobile

@JaviMerino

This comment has been minimized.

Contributor

JaviMerino commented May 9, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

@Amorn-Kingthong

This comment has been minimized.

Amorn-Kingthong commented May 9, 2018

OK

@obscuren

This comment has been minimized.

Member

obscuren commented May 9, 2018

I approve changing the license for this Ethereum wiki repository to Creative Commons' CC0 license ("No rights reserved"), putting it in the public domain.

@jamesray1 jamesray1 closed this May 29, 2018

@Briechenstein12

ethereum
Create CC0-LICENSE #528
@Briechenstein12

Creating a CC0 license allows for the content of this wiki to be placed in the public domain. This will help to allow for the dissemination of information about Ethereum, the Ethereum ecosystem and Web 3 in a completely permissive manner.

@Platinumwrist

This comment has been minimized.

Platinumwrist commented May 31, 2018

I have contributed to Etherscan/Eth lialakyky@gmail.com Etherscan name CustomClassic Github name lialakyky505

@Briechenstein12

This comment has been minimized.

Briechenstein12 commented on 61a8945 Jun 5, 2018

Create CCO-License

This comment has been minimized.

Collaborator

jamesray1 replied Jun 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment