0453e047ec
As per the definition of this tag "The “OpenStack TC Approved Release” is used as the superset of projects used by the OpenStack Foundation when creating commercial trademark programs." (read full definition in [1]) this tag was used to know if project under OpenStack is mature so that it can be considered as possible candidate for trademark programs. This situation was in early stage of OpenStack hen we used to have incubated vs integrated project status but now everything in project.yaml file is consider as mature, following release, active etc. Bylaw requirements are (section 4.1, 4.13[2]) "The Technical Committee shall designate a subset of the OpenStack Project an “OpenStack Technical Committee Approved Release” from time to time. The Board of Directors may determine "Trademark Designated OpenStack Software" from time to time, which will be a subset of the "OpenStack Technical Committee Approved Release" as provided in Section 4.1(b)(ii) and (iii)" (read full text in bylaw link[2]) We do not need any changes in bylaw as all projects listed in projects.yaml file are applicable as "OpenStack Technical Committee Approved Release" and if any of the current trademarked software is going to be deleted from the projects.yaml then it need to be done with Coordination Procedures listed in bylaw. This commit proposes to remove this tag and add section in place of this tag defintion to consider all the projects listed in projects.yaml as "OpenStack Technical Committee Approved Release". [1] https://governance.openstack.org/tc/reference/tags/tc_approved-release.html#rationale [2] https://www.openstack.org/legal/bylaws-of-the-openstack-foundation Change-Id: I0955c20a74eea8cac5f920bba60be1a334d50754
2.2 KiB
Licensing requirements
Official OpenStack projects need to follow a number of rules when it comes to licensing.
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.
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.