Make tc managed tag names consistent
TC managed tags don't follow the naming "standard" we've been following for other tags. There are 2 tags and neither of them use a `tc` prefix or groupping. This patch renames the tc-approved-release to tc:approved-release Change-Id: I2674acefd9018c4f043ce27c9ada201290e64e3f
This commit is contained in:
Flavio Percoco
parent
887ecbdf36
commit
84b12c5af1
|
|
@ -176,7 +176,7 @@ cinder:
|
|||
contributor: http://docs.openstack.org/developer/cinder/
|
||||
api: http://developer.openstack.org/api-ref/block-storage/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- vulnerability:managed
|
||||
|
|
@ -650,7 +650,7 @@ glance:
|
|||
tags:
|
||||
- assert:follows-standard-deprecation
|
||||
- assert:supports-upgrade
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- starter-kit:compute
|
||||
|
|
@ -699,7 +699,7 @@ heat:
|
|||
contributor: http://docs.openstack.org/developer/heat/
|
||||
api: http://developer.openstack.org/api-ref/orchestration/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- vulnerability:managed
|
||||
|
|
@ -782,7 +782,7 @@ horizon:
|
|||
# Is not really needed to refer to in this file?
|
||||
api: http://docs.openstack.org/developer/horizon/#api-reference
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- vulnerability:managed
|
||||
|
|
@ -2260,7 +2260,7 @@ ironic:
|
|||
contributor: http://docs.openstack.org/developer/ironic/
|
||||
api: http://developer.openstack.org/api-ref/baremetal/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-intermediary
|
||||
- type:service
|
||||
- stable:follows-policy
|
||||
|
|
@ -2401,7 +2401,7 @@ keystone:
|
|||
contributor: http://docs.openstack.org/developer/keystone/
|
||||
api: http://developer.openstack.org/api-ref/identity/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- starter-kit:compute
|
||||
|
|
@ -2904,7 +2904,7 @@ neutron:
|
|||
docs:
|
||||
contributor: http://docs.openstack.org/developer/neutron/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- stable:follows-policy
|
||||
- type:service
|
||||
|
|
@ -2925,7 +2925,7 @@ neutron:
|
|||
docs:
|
||||
api: http://developer.openstack.org/api-ref/networking/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-intermediary
|
||||
- stable:follows-policy
|
||||
- type:library
|
||||
|
|
@ -2972,7 +2972,7 @@ nova:
|
|||
contributor: http://docs.openstack.org/developer/nova/
|
||||
api: http://developer.openstack.org/api-ref/compute/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- starter-kit:compute
|
||||
|
|
@ -6071,7 +6071,7 @@ sahara:
|
|||
contributor: http://docs.openstack.org/developer/sahara/
|
||||
api: http://docs.openstack.org/developer/sahara/restapi.html
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- vulnerability:managed
|
||||
|
|
@ -6314,7 +6314,7 @@ swift:
|
|||
contributor: http://docs.openstack.org/developer/swift/
|
||||
api: http://developer.openstack.org/api-ref/object-storage/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-intermediary
|
||||
- type:service
|
||||
- vulnerability:managed
|
||||
|
|
@ -6406,7 +6406,7 @@ Telemetry:
|
|||
tags:
|
||||
- assert:follows-standard-deprecation
|
||||
- assert:supports-upgrade
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-intermediary
|
||||
- type:service
|
||||
ceilometer-powervm:
|
||||
|
|
@ -6614,7 +6614,7 @@ trove:
|
|||
contributor: http://docs.openstack.org/developer/trove/
|
||||
api: http://developer.openstack.org/api-ref/database/
|
||||
tags:
|
||||
- tc-approved-release
|
||||
- tc:approved-release
|
||||
- release:cycle-with-milestones
|
||||
- type:service
|
||||
- vulnerability:managed
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ TC Managed Tags
|
|||
:glob:
|
||||
|
||||
starter-kit_compute
|
||||
tc-approved-release
|
||||
tc_approved-release
|
||||
|
||||
Team Description Tags
|
||||
=====================
|
||||
|
|
|
|||
|
|
@ -4,97 +4,9 @@
|
|||
Unported License.
|
||||
http://creativecommons.org/licenses/by/3.0/legalcode
|
||||
|
||||
.. _`tag-tc-approved-release`:
|
||||
|
||||
=====================
|
||||
tc-approved-release
|
||||
=====================
|
||||
|
||||
.. NOTE(dhellmann): I don't especially like the name of this tag, but
|
||||
I decided its use would be more easily communicated if we stuck
|
||||
with the designation from the bylaws rather than making up a
|
||||
different name.
|
||||
|
||||
This tag is used to indicate the projects the TC recommends to the
|
||||
OpenStack Foundation Board as candidates for trademark use under the
|
||||
OpenStack Foundation trademark policy.
|
||||
|
||||
|
||||
Application to current projects
|
||||
===============================
|
||||
|
||||
.. tagged-projects:: tc-approved-release
|
||||
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
||||
The "OpenStack TC Approved Release" is used as the superset of
|
||||
projects used by the OpenStack Foundation when creating commercial
|
||||
trademark programs. A commercial trademark program would not be able
|
||||
to have any requirements for code or functionality outside of what is
|
||||
included in this group. The foundation may choose to create trademark
|
||||
programs only related to a subset of the projects.
|
||||
|
||||
The projects included in this group should generally represent the
|
||||
most mature OpenStack projects. OpenStack Foundation commercial
|
||||
trademark programs use criteria developed by the Interop working group
|
||||
(formerly the DefCore committee) of the Foundation board of
|
||||
directors. This criteria is partially based on a set of capabilities
|
||||
provided by OpenStack Projects. The capabilities adopted by the
|
||||
Interop committee are ones that are mature, well adopted, and not
|
||||
expected to change in the near future.
|
||||
|
||||
This tag is applied to projects the TC considers suitable to be
|
||||
included in the set of "Trademark Designated OpenStack Software" as
|
||||
defined in the Foundation bylaws. Applying the tag is an indication
|
||||
that the TC is including the project in the "OpenStack TC Approved
|
||||
Release", following the guidelines laid out in sections 4.1 and 4.13
|
||||
of `the OpenStack Foundation Bylaws`_.
|
||||
|
||||
.. _the OpenStack Foundation Bylaws: http://www.openstack.org/legal/bylaws-of-the-openstack-foundation
|
||||
|
||||
Requirements
|
||||
============
|
||||
|
||||
A project that receives the "tc-approved-release" tag should at a
|
||||
minimum meet the following requirements:
|
||||
|
||||
* The TC approves the request for the tag to be applied to a project.
|
||||
|
||||
*Additional criteria for applying this tag will be worked out at a
|
||||
future date.*
|
||||
|
||||
Tag application process
|
||||
=======================
|
||||
|
||||
The sole purpose of this tag is defining the pool of projects that
|
||||
could be used for the OpenStack Trademark program. It is the role of
|
||||
the Board (as well as working groups like the Interop committee) to
|
||||
best understand the demand for the commercial trademark by OpenStack
|
||||
users and vendors.
|
||||
|
||||
As such, changes to this tag are expected to come from the Interop
|
||||
working group based on their judgment that the marketplace has evolved
|
||||
and a new set of projects should be used in future versions of
|
||||
trademark programs. They should propose adding or removing this tag to
|
||||
a project by proposing a change to the openstack/governance
|
||||
repository. The change is reviewed by the Technical Committee and
|
||||
approved using standard resolution approval rules, including
|
||||
discussion at at least one Technical Committee public IRC meeting.
|
||||
|
||||
|
||||
|
||||
Deprecation
|
||||
===========
|
||||
|
||||
Deprecation of the use of this tag is governed by the bylaws, the
|
||||
trademark policy set out by the board, and the procedures the Board
|
||||
and TC have agreed to follow for communicating changes to the
|
||||
"Trademark Designated OpenStack Software".
|
||||
|
||||
.. note::
|
||||
|
||||
We need a reference to that agreement, when we have it. We also
|
||||
need a reference to the deprecation policy the Board adopts, since
|
||||
that will influence our policy by at least setting a minimum.
|
||||
This tag has been renamed to :ref:`tag-tc:approved-release`
|
||||
|
|
|
|||
|
|
@ -0,0 +1,100 @@
|
|||
::
|
||||
|
||||
This work is licensed under a Creative Commons Attribution 3.0
|
||||
Unported License.
|
||||
http://creativecommons.org/licenses/by/3.0/legalcode
|
||||
|
||||
.. _`tag-tc:approved-release`:
|
||||
|
||||
=====================
|
||||
tc:approved-release
|
||||
=====================
|
||||
|
||||
.. NOTE(dhellmann): I don't especially like the name of this tag, but
|
||||
I decided its use would be more easily communicated if we stuck
|
||||
with the designation from the bylaws rather than making up a
|
||||
different name.
|
||||
|
||||
This tag is used to indicate the projects the TC recommends to the
|
||||
OpenStack Foundation Board as candidates for trademark use under the
|
||||
OpenStack Foundation trademark policy.
|
||||
|
||||
|
||||
Application to current projects
|
||||
===============================
|
||||
|
||||
.. tagged-projects:: tc:approved-release
|
||||
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
||||
The "OpenStack TC Approved Release" is used as the superset of
|
||||
projects used by the OpenStack Foundation when creating commercial
|
||||
trademark programs. A commercial trademark program would not be able
|
||||
to have any requirements for code or functionality outside of what is
|
||||
included in this group. The foundation may choose to create trademark
|
||||
programs only related to a subset of the projects.
|
||||
|
||||
The projects included in this group should generally represent the
|
||||
most mature OpenStack projects. OpenStack Foundation commercial
|
||||
trademark programs use criteria developed by the Interop working group
|
||||
(formerly the DefCore committee) of the Foundation board of
|
||||
directors. This criteria is partially based on a set of capabilities
|
||||
provided by OpenStack Projects. The capabilities adopted by the
|
||||
Interop committee are ones that are mature, well adopted, and not
|
||||
expected to change in the near future.
|
||||
|
||||
This tag is applied to projects the TC considers suitable to be
|
||||
included in the set of "Trademark Designated OpenStack Software" as
|
||||
defined in the Foundation bylaws. Applying the tag is an indication
|
||||
that the TC is including the project in the "OpenStack TC Approved
|
||||
Release", following the guidelines laid out in sections 4.1 and 4.13
|
||||
of `the OpenStack Foundation Bylaws`_.
|
||||
|
||||
.. _the OpenStack Foundation Bylaws: http://www.openstack.org/legal/bylaws-of-the-openstack-foundation
|
||||
|
||||
Requirements
|
||||
============
|
||||
|
||||
A project that receives the "tc:approved-release" tag should at a
|
||||
minimum meet the following requirements:
|
||||
|
||||
* The TC approves the request for the tag to be applied to a project.
|
||||
|
||||
*Additional criteria for applying this tag will be worked out at a
|
||||
future date.*
|
||||
|
||||
Tag application process
|
||||
=======================
|
||||
|
||||
The sole purpose of this tag is defining the pool of projects that
|
||||
could be used for the OpenStack Trademark program. It is the role of
|
||||
the Board (as well as working groups like the Interop committee) to
|
||||
best understand the demand for the commercial trademark by OpenStack
|
||||
users and vendors.
|
||||
|
||||
As such, changes to this tag are expected to come from the Interop
|
||||
working group based on their judgment that the marketplace has evolved
|
||||
and a new set of projects should be used in future versions of
|
||||
trademark programs. They should propose adding or removing this tag to
|
||||
a project by proposing a change to the openstack/governance
|
||||
repository. The change is reviewed by the Technical Committee and
|
||||
approved using standard resolution approval rules, including
|
||||
discussion at at least one Technical Committee public IRC meeting.
|
||||
|
||||
|
||||
|
||||
Deprecation
|
||||
===========
|
||||
|
||||
Deprecation of the use of this tag is governed by the bylaws, the
|
||||
trademark policy set out by the board, and the procedures the Board
|
||||
and TC have agreed to follow for communicating changes to the
|
||||
"Trademark Designated OpenStack Software".
|
||||
|
||||
.. note::
|
||||
|
||||
We need a reference to that agreement, when we have it. We also
|
||||
need a reference to the deprecation policy the Board adopts, since
|
||||
that will influence our policy by at least setting a minimum.
|
||||
Loading…
Reference in New Issue