Skip to content

[License Exception Request] MySql.Data - License GPL-2.0-only license WITH Universal-FOSS-exception-1.0 license. #995

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

Open
2 of 12 tasks
Kielek opened this issue Apr 8, 2025 · 2 comments
Assignees

Comments

@Kielek
Copy link

Kielek commented Apr 8, 2025

For which CNCF project are you requesting exceptions?

OpenTelemetry .NET Automatic Instrumentation

Are you an official maintainer of this project?

Yes

List of components requiring an exception

Component Upstream URL License(s) Purpose
MySql.Data https://www.nuget.org/packages/MySql.Data GPL-2.0-only license WITH Universal-FOSS-exception-1.0 license Testing only. Checking if we are able to listen events (spans) from the MySql.Data

Are all of the components mandatory dependencies for the project to function as intended?

No

If no, please explain

It is using only during the build and testing pipeline. There is no reference in the final artifacts, distributed binaries.

How will the components be included in or with the project's code and distributions?

  • Incorporated code
  • Vendored component
  • Build-time dependency
  • Build and test tooling
  • Install-time dependency
  • Required upstream dependencies
  • Other (please describe below)

If any of the above selections don't apply to all of the components listed in the table above, please explain

No response

Which of the following best describes how the components interact with the project's own code?

  • Static linking: e.g., compiled together with project code into a single binary
  • Dynamic linking: e.g., compiled into a separate binary, running together with project code in a single address space at run-time
  • Separate process: e.g., separate executable running in a different process space, interacting with project code only via mechanisms such as pipes, sockets, etc.
  • Network interaction only: e.g., logically separated over a network and communicating only via mechanisms such as network API call, exchanging JSON data, etc.
  • Other (please describe below)

If any of the above selections don't apply to all of the components listed in the table above, please explain

It is using only during the build and testing pipeline. There is no reference in the final artifacts, distributed binaries.

Will any of the components be modified?

No

If yes, please specify which components will be modified, and briefly describe the purpose and nature of the modifications.

No response

Will the project be seeking to contribute the modifications back to the upstream project?

None

@Kielek
Copy link
Author

Kielek commented Apr 8, 2025

Cross linking with open-telemetry/community#2558
@danielgblanco, @trask, FYI

@danielgblanco
Copy link
Contributor

Cross-linking here Service Desk support ticket CNCFSD-2670 in case @jeefy , @joannalee333 or @krook need more context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants