openstack
/
governance
Code Issues Proposed changes

propose approval policy for goal responses 

Change-Id: Ifb6cf2cd87621f6b043031013d7aec8bbf524ac6
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
changes/99/356699/4
Doug Hellmann 2016-08-17 16:36:42 -04:00
parent a47b61806c
commit fcc9b0e8a3
2 changed files with 27 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -11,5 +11,9 @@ Directory structure:
can be expressed as a resolution.
Those must be named YYYYMMDD-short-name with YYYYMMDD being the
proposal date in order to allow basic sorting.
goals/
Documentation for OpenStack community-wide goals, organized by
release cycle. These pages will be updated with project status
info over time, and if goals are revised.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.

23
reference/house-rules.rst
View File

@ -47,6 +47,29 @@ In corner cases where the change is time-sensitive (like a deliverable
reorganization which blocks a release request), the chair may fast-track the
change, but should report on that exception at the next TC meeting.
Goal Updates from PTLs
----------------------
PTLs will acknowledge community-wide goals at the start of each cycle
by providing links to artifacts for tracking the work, or an
explanation of why work is not going to be done. They will also
provide references to completion artifacts at the end of each cycle
for goals where work was needed. These patches should be reviewed by
TC members for completeness and clarity (is enough information
provided for interested parties to track the work, or is the
justification for not doing work clear enough).
The patches to add team acknowledgments, planning artifacts, and
completion artifacts to the goal document do not need to go through
the formal vote process, and so lazy consensus rules will be used. If
there is no objection posted one week after the most recent version of
a change is proposed, then the change can be approved by the chair.
If a TC member feels that one of these responses needs to be discussed
by the entire TC, they should place it on the agenda for an upcoming
meeting and the change should not be approved until after the
discussion is completed.
Rolling back fast-tracked changes
---------------------------------