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

List of components and their dependent component licenses #683

Closed
maxgolov opened this issue Apr 19, 2021 · 2 comments
Closed

List of components and their dependent component licenses #683

maxgolov opened this issue Apr 19, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@maxgolov
Copy link
Contributor

maxgolov commented Apr 19, 2021

List of components and their Copyright notices / Licenses

All code contributed in this repo is licensed under Apache License v2.0 with a few notable exceptions:

  • MPark Variant - Boost license. This code can be removed entirely and replaced by Google Abseil implementation, that is Apache License v2.0 ( Switch to abseil::variant as default variant class across api #572 ) . That ultimately allows all of OpenTelemetry C++ API be licensed under the same Apache License v2.0.

  • HTTP client presently depends on libcurl , which is implemented under its own MIT/X-alike license . This is required for Zipkin and Elastic exporters.

  • nlohmann/json - Required for Zipkin and Elastic exporter. Required for zPages. And Optional for specific subtype of ETW exporter. The library is licensed under MIT License. Products builds that are shipping with OTLP gRPC exporter or ETW exporter, and NOT including zPages - do not require this module, but it may come in handy for other aspects, e.g. remote provisioning of exporter using JSON configuration.

  • TraceLogging Dynamic for Windows library - strongly recommended for ETW exporter, as default transport channel - is also MIT License. Products shipping on Linux do not require this component.

  • Certain other parts of OTLP exporter may require Boost ? cc: @ThomsonTan to confirm on where it will be required.

Proposal

The goal is to create a markdown document that captures above detail with all the licenses; alongside with build options that enable these components mentioned above. Not every build combo requires all the licenses. Having the OSS components document enables any product commercially shipping with OpenTelemetry C++ SDK to easily list all the required licenses in their distro, prepackaged build of SDK. Reference example of OSS components document that we need to add to the repo.

@lalitb lalitb added this to the 1.0.0-rc.1 milestone Apr 26, 2021
@lalitb lalitb added the documentation Improvements or additions to documentation label Apr 27, 2021
@lalitb
Copy link
Member

lalitb commented Jun 3, 2021

Moving to GA milestone as this is documentation change.

@lalitb lalitb modified the milestones: 1.0.0-rc.1, 1.0.0 GA Jun 3, 2021
@lalitb
Copy link
Member

lalitb commented Jun 25, 2021

#844 resolves this.

@lalitb lalitb closed this as completed Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants