cncf / foundation

☁️♮🏛 This repo contains several documents related to the operation of the CNCF. File non-technical issues related to CNCF here.
https://cncf.io
Other
546 stars 522 forks source link

[License Exception Request] [Crossplane] [MPL-2.0] #787

Open jeanduplessis opened 2 months ago

jeanduplessis commented 2 months ago

Component details

The https://github.com/crossplane/upjet/ project relies on MPL licensed code from Hashicorp for integration with their Terraform providers.

The list of MPL licensed code referenced in the project are:

Direct dependencies

Indirect dependencies

License name

Mozilla Public License (MPL) version 2.0

Code modified?

The dependencies are referenced externally and remains unmodified. https://github.com/crossplane/upjet/blob/main/go.mod

Changes contributed?

Not applicable currently, but if changes are needed we would look to contribute directly upstream as a first step.

Any alternatives?

We looked at OpenTofu, but since OpenTofu project is also MPL licensed and depends on many of the same dependencies as we do from github.com/hashicorp/, there are no viable alternatives currently.

Integrates with other components?

The MPL licensed components are used by Upjet to be able to integrate with the Terraform providers and generate Crossplane-compatible providers.

jeanduplessis commented 1 month ago

In addition to the MPL licensed dependencies used by crossplane/upjet the following dependencies are used by the providers generated by Upjet:

Dependencies

jeanduplessis commented 1 month ago

@krook Would it be accurate to assume this, https://github.com/cncf/foundation/issues/619#issuecomment-2127627367, applies here as well?

jeanduplessis commented 1 month ago

Also if an MPL licensed repo was forked and modified, but not vendored, and still linked to at build time, I assume it is still in compliance with the granted exception.

krook commented 1 month ago

@krook Would it be accurate to assume this, #619 (comment), applies here as well?

Yes, the GB approval of a license exception for Issue #619 does apply to all CNCF projects, but the conditions of the prior GB approval still apply (i.e., "used in unmodified form by linking to the dependency at build time").

krook commented 1 month ago

Also if an MPL licensed repo was forked and modified, but not vendored, and still linked to at build time, I assume it is still in compliance with the granted exception.

Unfortunately not. The exception granted by the GB for Issue #619 was only for use of those dependencies "so long as they are used in unmodified form by linking to the dependency at build time." If an exception is desired for a modified fork, the project needs to open a separate license exception request.

yordis commented 1 week ago

Hey folks, any updates on this one?