Cla License Agreement

The CLA does not change the terms of the default open source license used by our software such as MPL2 or MIT. You remain free to use our projects in your own projects or companies, to republish modified sources and much more. Please refer to the corresponding license for the project you are contributing to for more information. A Contributor License Agreement (CLA) defines the conditions under which intellectual property has contributed to a business/project, usually open source licensed software. The question is, if the project`s open source license isn`t enough to make managers feel comfortable accepting the code, why should end users be comfortable enough to do so? In other words, why grant project managers rights and protection beyond the rights and protections granted to end users (and other contributors)? Most of the time, this is a sign that the license the project uses is not enough for the project industry or the legal attitude of the manager, and switching to a more patent-friendly license like Apache can completely solve the need for a CLA. To clarify the intellectual property license granted by contributions from a natural or legal person, HashiCorp, Inc. («HashiCorp») have a Contributor License Agreement («CLA») signed by each Contributor and certifying that it is compatible with the following license terms. This license does not change your rights to use your own contributions for any other purpose. Other arguments against CLA suggest that an inbound=outbound contribution policy should be implicit when contributing to an open source project, which discusses the need for a CLA. While GitHub`s terms of service explicitly define such a contribution policy as the standard, the «inbound=outbound» directive may not be a secure acceptance for open source projects hosted on other platforms. Although a licensor who provides an original work requested from a licensee for distribution may involve a non-exclusive copyright license, it is not certain that a court would find that a voluntary contribution to an open source project creates an implied copyright license or an implicit «inbound = outbound» directive.

If you wish to submit a work that is not your original creation, you may submit it separately from each contribution to HashiCorp, provide full details of its source and any licenses or other restrictions (including, but not limited to, patents, trademarks and related license agreements) of which you are personally aware, and indicate the work as «filed on behalf of a third party: [called here] ». . . .