Comments (10)
Sorry for late reply (I thank @youknowone for ping). And yeah, that sounds problematic. I'm very much okay to relicense---or additionally license---my contribution in other PD-equivalent licenses.
Which one to adopt
My use of a PD-equivalent license was inspired of the SQLite public domain dedication, but I wanted to be more concrete when it comes to a legal matter. Therefore if it's just my own code, theoretically I can just state that CC0-1.0 section 4(a) is to be ignored. But that would be legally questionable to say the least.
I personally didn't use the Unlicense (or WTFPL or other tongue-in-cheek licenses) because it is a polar opposite of a "concrete" license. Indeed, CC0 as a public domain dedication is so concrete that it prevents other interpretations including a patent grant. The Unlicense is the only PD-equivalent license besides from CC0-1.0 that has received an approval from FSF, but it's not like that FSF explicitly disapproved other PD-equivalent licenses, so I don't care about that much.
I have also briefly considered two more options.
- The Blue Oak Model License 1.0.0, which is a relatively new PD-equivalent license but with an explicit patent grant. It is not yet OSI-approved, but it was recently submitted to the review, so I believe it will be eventually approved (OSI approved the Unlicense after all). The major downside is a lack of popularity and legal precedent.
- Yet another option is to combine two licenses for a public domain dedication and a patent grant respectively. CC0-1.0 is a perfect license for the former, so it may give the best of both worlds if properly done. But I don't know how to do that. For example,
CC0-1.0 OR 0BSD
will allow either a PD dedication or patent grant but not both, which is practically okay but legally dubious. An unconditional waiver (when legally allowed) will require a conjunctive dual-licensing which is much more complicated. (There is an analysis ofCC0-1.0 AND MIT
, but not done by a laywer.)
Therefore my option is to switch to the Zero-Clause BSD (SPDX identifier 0BSD
), as per the Chris Morgan's recommendations.
Agreements
The crate has accumulated more code since my last major contribution though, so it's time to call everyone around. Judging from the diff, I think non-trivial changes can be classified as folllows:
- An entire fuzzing infrastructure by @hcsch
- Additional tests by @sanxiyn, @ajtribick, @sunfishcode and @youknowone (in the order of first relevant contribution)
- Non-code or minor changes by @pchickey, @littledivy and some others listed above (ditto)
It is arguable whether changes in 2 or 3 require relicensing, but for now I've pinged everyone. If you agree to relicense your work please copy and paste the following comment:
* [ ] I agree to relicense my contributions to `hexf` in the terms of the [Zero-Clause BSD](https://opensource.org/license/0bsd/) license as published by the Open Source Initiative.
...and explicitly mark the check box. My own is as follows:
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
Good idea moving off of CC0. I've read about that being problematic for code before.
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
👍
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
- I agree to relicense my contributions to
hexf
in the terms of the Zero-Clause BSD license as published by the Open Source Initiative.
from hexf.
Thank you for confirmations, and sorry again for my procrastination!
from hexf.
Awesome - thank you all for the quick turnaround here! 💯
from hexf.
Related Issues (10)
- Consider using a union instead
- thread 'main' panicked at 'attempt to shift left with overflow'
- is this project abandoned? HOT 1
- Publish the most recent 0.2 to crates.io? HOT 2
- Unable to parse hex floats without decimal point
- Works with Rust 1.43 HOT 2
- A better API for handling input that has already been parsed HOT 7
- Hex literals with large exponents are incorrectly rejected
- parsing fails for input "0x0.1E" HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hexf.