openstack/governance
Code Issues Proposed changes

Grant Cross-Project Spec Team Voting in Specs

Browse Source 
This resolution is to recognize the cross-project spec team that reviews
cross-project specifications. This will allow the team to approve
specifications independently of the Technical Committee.

Change-Id: Id8e8b207fe47691414efcb51e6e24887f129a800
This commit is contained in:
Mike Perez 2016-04-14 22:30:28 -07:00
parent e75cd13d53
commit 08d6d1045e
1 changed files with 52 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
resolutions/20160414-grant-cross-project-spec-team-voting.rst Normal file
View File

@ -0,0 +1,52 @@
===============================================================
2016-04-14 Grant Cross-Project Team Voting in CP Specifications
===============================================================
Introduction
------------
Since the inception of the `cross-project specification repository
<http://git.openstack.org/cgit/openstack/openstack-specs>`_ the Technical
Committee has had privileges in OpenStack's gerrit review system to +2
a specification, as oppose to a +1 which any individual member of the community
can give today.
The goal of this resolution is to recognize the `cross-project specification
liaison team
<http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons>`_
by allowing them to have the ability to +2 specifications, since they should
know better than anyone else if a specification will work with their project.
Previous Workflow
-----------------
When a cross-project specification is proposed, the cross-project specification
liaisons, are responsible for providing feedback when a specification involves
their project.
Once there is consensus among the cross-project specification liaisons, the
specification is added to the Technical Committee's meeting agenda to be rubber
stamped to be merged.
New Workflow
------------
When a cross-project specification is proposed, the cross-project specification
liaisons will review it as usual. There will be a list of projects that are
known to be involved at the time within a specification. Those cross-project
specification liaisons will need to sign off on the specification with a +2.
Assuming there is consensus with those that are involved, the specification
will be merged (Workflow+1) by the cross-project chair after final discussion
in the `cross-project meeting
<https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting>`_.
In the cases where consensus cannot be met with the projects involved
with a cross-project specification, the specification can be appealed to the
Technical Committee to discuss a final decision.
Projects that have nothing to do with the specification may provide feedback in
the review, but the decision is up to those that will ultimately have to
implement the specification in their project.