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

Projects that rely on BOSL exceptions should say that they do #36

Closed
daira opened this issue Jun 28, 2022 · 1 comment · Fixed by #141
Closed

Projects that rely on BOSL exceptions should say that they do #36

daira opened this issue Jun 28, 2022 · 1 comment · Fixed by #141

Comments

@daira
Copy link
Contributor

daira commented Jun 28, 2022

This is important licensing information since it affects how those projects can be forked. zcash_script depends on orchard via zcash_primitives and zcash_note_encryption: see

zcash_script/Cargo.toml

Lines 57 to 58 in c9fbc44

zcash_note_encryption = "0.1"
zcash_primitives = { version = "0.6", features = ["transparent-inputs"] }

and zcash/librustzcash#576.

Suggested wording is:

Downstream code forks should note that the code in this repository depends on
the 'orchard' crate, which is licensed under the Bootstrap Open Source License.
A license exception is provided allowing some derived works that are linked or
combined with the 'orchard' crate to be copied or distributed under the original
licenses (in this case MIT / Apache 2.0), provided that the included portions of
the 'orchard' code remain subject to BOSL.
See https://github.com/zcash/orchard/blob/main/COPYING for details of which
derived works can make use of this exception.

See also:

@oxarbitrage
Copy link
Contributor

I'm proposing the following actions and would like your input on whether we should implement them now. My plan is to submit a PR with the following changes:

  1. Incorporate dual license files (APACHE/MIT) into this project, aligning with what Zebra and Zcash do.

  2. Update the README by adding a license section, using a wording similar to Zebra's README as a reference: Zebra License Section.

  3. Integrate the recommended wording from @daira regarding the BOSL into the newly created license section on the README.

Your thoughts on this would be greatly appreciated!

@mpguerra mpguerra added this to Zebra Apr 10, 2024
@github-project-automation github-project-automation bot moved this to New in Zebra Apr 10, 2024
@mpguerra mpguerra linked a pull request Apr 12, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from New to Done in Zebra Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants