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

Change license to CC0? #113

Closed
smartcontracts opened this issue Oct 28, 2018 · 2 comments
Closed

Change license to CC0? #113

smartcontracts opened this issue Oct 28, 2018 · 2 comments
Labels
question Further information is requested

Comments

@smartcontracts
Copy link
Member

I'd like to propose changing our license to CC0, the "public domain" license. Not much different than MIT, but a little more accessible globally.

@smartcontracts smartcontracts added the question Further information is requested label Oct 28, 2018
@Ro5s
Copy link
Contributor

Ro5s commented Oct 29, 2018

Yeah, CC0 has the most fulsome waiver language I've seen. Seems appropriate here (dealing with situation where some countries don't recognize releasing work into pub domain...). Advantages with retaining MIT seem to be (i) short and simple, (ii) widely used (comfort zone), + (iii) preserves copyright and legal notice. This author also had some interesting criticisms of CC0 vs. MIT on international perspective - - basically, CC0's fulsome language can be a double-edged sword by attempting, e.g., to waive certain 'moral rights' in Section 1(ii) (not copacetic in Norway, among others....).

At risk of veering into full navel-gazing territory: Open Source Initiative has a sorta ambivalent FAQ on this subject, as well, noting: "CC0 was not explicitly rejected, but the License Review Committee was unable to reach consensus that it should be approved, and Creative Commons eventually withdrew the application. The most serious of the concerns raised had to do with the effects of clause 4(a), which reads: 'No ... patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.'. While many open source licenses simply do not mention patents, it is exceedingly rare for open source licenses to explicitly disclaim any conveyance of patent rights, and the Committee felt that approving such a license would set a dangerous precedent, and possibly even weaken patent infringement defenses available to users of software released under CC0."

Edit: So, I think concern about CC0's patent language is less relevant for LearnPlasma. My bias however, would be to stick with MIT due to its (i) simplicity, (ii) lacks cloud of uncertainty.

These are pretty nifty comparisons on granular level: MIT vs. CC0.

@smartcontracts
Copy link
Member Author

smartcontracts commented Oct 29, 2018

@Ro5s This is actually extremely interesting! I wasn't aware of any of these arguments and exactly how difficult it is to dedicate something into the public domain. Well, I think that's a strong argument to keep MIT instead of to move to CC0.

Ro5s added a commit to buildOMG/kb that referenced this issue Nov 3, 2018
Create MIT License. See also discussion of merits of CC0 v. MIT: ethsociety/learn-plasma#113
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants