add license text for 0BSD #27
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This project has been relicensed from CC0-1.0 to 0BSD per #26. This PR adds a file with the license text for the 0BSD license, and ensures that "cargo package" / "cargo publish" picks up the file in both the
hexfandhexf-parsecrates.While including the license text is not a hard requirement for 0BSD (whereas it is hard requirement for other licenses like MIT or Apache-2.0), it is still good practice to do so. It also helps Linux distributions which package this project. (For context, I'm working on this because hexf-parse is a dependency of the fancy new "ruff" Python linter / formatter).
If this PR is accepted, it would be great if you could publish a new version of hexf / hexf-parse to crates.io to make the 0BSD-relicensed code available there. Thank you!