Backport of [COMPLIANCE] Update MPL-2.0 LICENSE into release/1.14.x #15314
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-consul-core
force-pushed
the
backport/compliance/add-license/remarkably-true-wasp
branch
from
0dfd912
to
160b14c
Compare
hc-github-team-consul-core
deleted the
backport/compliance/add-license/remarkably-true-wasp
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #14964 to be assessed for backporting due to the inclusion of the label backport/1.14.
The below text is copied from the body of the original PR.
Hi there 馃憢
This PR was auto-generated as part of an internal review of public repositories that are not in compliance with HashiCorp's licensing standards.
Frequently Asked Questions
Why am I getting this PR?
This pull request was created because one or more of the following criteria was found:LICENSEfileLICENSEfile was present, but had a non-conforming name (e.g.,license.txt)LICENSEfile was present, but was missing an appropriate copyright statementMore info is available in the RFC
How do you determine the copyright date?
The copyright date given in this PR is supposed to be the year the repository or project was created (whichever is older). If you believe the copyright date given in this PR is not valid, please reach out to:#proj-software-copyright
I don't think this repo should be licensed under the terms of the Mozilla Public License 2.0. Who should I reach out to?
If you believe this repository should not use an MPL 2.0 License, please reach out to legal@hashicorp.com. Exemptions are considered on a case-by-case basis, but common reasons include if the project is co-managed by another entity that requires differing license terms, or if the project is part of an ecosystem that commonly uses a different license type (e.g., MIT or Apache 2.0).Please approve and merge this PR in a timely manner to keep this source code compliant with our OSS license agreement. If you have any questions or feedback, reach out to #proj-software-copyright.
Thank you!
Made with 鉂わ笍 @hashicorp
Overview of commits