openstack
/
governance
Code Issues Proposed changes

Require PTL signoff for project-update changes 

We should not allow changes to a project unless someone from the project
(e.g. the PTL or their delegate) agrees to the change.

Change-Id: I9e52035da299d7ae3e55e4636d0a1c66ca3c2e36
Signed-off-by: Graham Hayes <gr@ham.ie>
This commit is contained in:
Graham Hayes 2020-05-13 11:38:24 +01:00
parent 0cbc632a38
commit e381ababb4
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
reference/house-rules.rst
View File

@ -101,7 +101,10 @@ addition of a new git repository, retirement or self-assertion of a tag.
If there is no objection posted after the addition or retirement of a project
is proposed (assuming the correct retirement process has been followed), then
the change can be approved by the chair if it has at least two 2 roll call
votes, which can include the vote of the chair and excludes the change owner.
votes (which can include the vote of the chair and excludes the change owner)
and a code review vote from the PTL of the project (or their delegate).
If the change is from the PTL or their delegate, this will count as an
acknowledgment code review vote.
One exception to this would be significant team mission statement changes,
which should be approved by a formal vote after discussion on the mailing list