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
Prompted by If92ab9d473f8ea8c861584dfc6d3e6a9ff7fdb6a, this change
clarifies that it's okay to use any FOSS program as a test
requirement for an OpenStack project.
Change-Id: I77d862b4c867912cb66f100839c875b7063b6b4b
Licensing requirements under the big tent have been unclear at best.
The Foundation bylaws impose some of them, but their interpretation
was left as an exercise to the reader. The TC traditionally came up
with rules for dependencies (through the requirements repository
README) but those were mostly unchecked. Finally, we need flexibility
for the project infrastructure, which should be able to run any
open source solution that fits.
After much back and forth with the Foundation legal counsel on what
could be acceptable under the bylaws, we agreed that the following
proposal was acceptable, and compatible with the current situation.
I propose we add it as a reference document to our governance
repository so that it's easier to point prospective projects to it,
and to track changes in the list of acceptable licenses over time.
Change-Id: I7ed11388e43bd5fcf2e8e6595c353429300387d5
Ghanshyam Mann