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 #576

Closed
daira opened this issue Jun 28, 2022 · 0 comments · Fixed by #577
Closed

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

daira opened this issue Jun 28, 2022 · 0 comments · Fixed by #577

Comments

@daira
Copy link
Contributor

daira commented Jun 28, 2022

This is important licensing information since it affects how those projects can be forked. The following librustzcash crates and components depend on orchard:

A copy of the notice is needed for each potentially reusable crate or component.

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:

@daira daira added this to the Release 5.1.0 milestone Jun 28, 2022
daira added a commit to daira/librustzcash that referenced this issue Jun 28, 2022
fixes zcash#576

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
adityapk00 pushed a commit to adityapk00/librustzcash that referenced this issue Aug 8, 2022
fixes zcash#576

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant