search

kubevirt / community

Community content
https://kubevirt.io
48 stars 102 forks source link

HashiCorp license changes: avoid upgrading to new packages (for now) since license has changed #238

Closed dhiller closed 1 month ago

dhiller commented 11 months ago

HashiCorp has changed their licensing for all of their products.

HashiCorp announced a transition from the Mozilla Public License v2.0 (MPL 2.0) to the Business Source License (BSL, or BUSL) v1.1 for future releases of all products and several libraries. HashiCorp APIs, SDKs, and almost all other libraries will remain MPL 2.0. source: https://www.hashicorp.com/license-faq

CNCF pointed out that vendored libraries should be safe to use, since they still use MPL.

Repositories with traces of hashicorp:

$ gh search code --owner=kubevirt 'hashicorp' | grep -oE '^kubevirt/([^:])+:' | sort | uniq                                      kubevirt/ci-health:
kubevirt/cluster-network-addons-operator:
kubevirt/containerdisks:
kubevirt/containerized-data-importer:
kubevirt/hyperconverged-cluster-operator:
kubevirt/k8s-seccomp-generator:
kubevirt/kubevirt.github.io:
kubevirt/kubevirt-velero-plugin:
kubevirt/kvm-info-nfd-plugin:
kubevirt/project-infra:
kubevirt/ssp-operator:
kubevirt/tekton-tasks-operator:
kubevirt/terraform-provider-kubevirt:

IIUC we are good for repositories that vendor libraries, since those have the old MPL license.

But we should not update the vendored packages from hashicorp until we know what the path forward is.

dhiller commented 11 months ago

/cc @nirarg @machacekondra

kubevirt-bot commented 8 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

aburdenthehand commented 7 months ago

/remove-lifecycle stale

aburdenthehand commented 7 months ago

/cc @aburdenthehand

kubevirt-bot commented 4 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 3 months ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot commented 2 months ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 2 months ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/community/issues/238#issuecomment-2081506345): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
aburdenthehand commented 2 months ago

/reopen

kubevirt-bot commented 2 months ago

@aburdenthehand: Reopened this issue.

In response to [this](https://github.com/kubevirt/community/issues/238#issuecomment-2085571384): >/reopen > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
kubevirt-bot commented 1 month ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 1 month ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/community/issues/238#issuecomment-2139846742): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.