openstack/governance
Code Issues Proposed changes
b635df1cd0
governance/reference/licensing.rst
Thierry Carrez 5e733b599d Remove 'Big Tent' mention from licensing reqs 
There was one leftover 'Big Tent' mention in the licensing
requrements doc.

Change-Id: I1273eb916f021f94fde3b4a1e2937a736b8170d5
2017-07-18 04:43:27 +02:00

2.3 KiB
Raw Blame History

Licensing requirements

Official OpenStack projects need to follow a number of rules when it comes to licensing.

In order to be considered for inclusion in the tag-tc:approved-release, the project must be licensed under Apache License, Version 2.0 (ASLv2).

OpenStack projects and libraries (produced by official OpenStack project teams) should generally be licensed under ASLv2, and otherwise must be licensed under a license supported by the Contributor License Agreement (CLA) which allows redistribution by the OpenStack Foundation under ASLv2 (currently only the MIT and both forms of the BSD license meet this requirement). In particular, service projects are recommended to always pick ASLv2 so that they may be included in the TC-approved release in the future.

In order to be acceptable as dependencies of OpenStack projects, external libraries (produced and published by 3rd-party developers) must be licensed under an OSI-approved license that does not restrict distribution of the consuming project. The list of acceptable licenses includes ASLv2, BSD (both forms), MIT, PSF, LGPL, ISC, and MPL. Licenses considered incompatible with this requirement include GPLv2, GPLv3, and AGPL.

[A]GPL libraries used during validation or testing phases of development fall into a gray area - they are not presumed to be compatible or incompatible and instead are reviewed on a case by case basis. Please use the legal-discuss mailing list to bring up any such cases.

Projects run as part of the OpenStack Infrastructure (in order to produce OpenStack software) may be licensed under any OSI-approved license.

This includes tools that are run with or on OpenStack projects only during validation or testing phases of development (e.g., a source code linter).

Other licenses (not explicitly listed in this document) may be considered in the future on a case-by-case basis by the Technical Committee, with the help of the OpenStack Foundation legal counsel.