Investigate HashiCorp license changes

[savitharaghunathan]

Investigate the impact of HashiCorp license changes

Tasks

Beta Give feedback

1. github.com/hashicorp/errwrap v1.1.0 - MPL 2.0 CNCF GB Exception
2. github.com/hashicorp/go-multierror v1.1.1 - MPL 2.0 CNCF GB Exception
3. github.com/hashicorp/go-version v1.6.0 - MPL 2.0 CNCF GB Exception
4. github.com/hashicorp/hcl v1.0.0 - MPL 2.0 CNCF GB Exception
5. Vagrant in dev env and setup docs

CNCF Tracking issue: cncf/foundation#617

[savitharaghunathan]

CNCF published some guidelines here - https://github.com/cncf/foundation/blob/main/source-available-recommendations.md

[sseago]

Yeah, we've been wondering the same about Velero use of hashicorp code. The first thing to do is figure out which hashicorp packages will actually get a license change. At least one source I saw suggested that while their product-oriented repos would all change to the new license, most of their libraries will not.

[sseago]

Looks like, of the packages mentioned above, the only one with a license change is vagrant -- the others are libraries which, as of 16 Aug 2023, still list MPL in repo-root/LICENSE. It looks like all of the products that are moving to the new license were updated on 10 Aug.

[savitharaghunathan]

Looks like, of the packages mentioned above, the only one with a license change is vagrant -- the others are libraries which, as of 16 Aug 2023, still list MPL in repo-root/LICENSE. It looks like all of the products that are moving to the new license were updated on 10 Aug.

Thanks @sseago :)

[djzager]

Closing as I think our work here is done. Reopen otherwise please.