openstack/governance
Code Issues Proposed changes

Simplifying house rule for project-updates

Browse Source 
Addressing the below comment to simplify the house rule
mentioned in project-updates

- https://review.opendev.org/c/openstack/governance/+/919984/comment/be577d2b_39d96583/

Change-Id: I2d07b5d8a78d1417e806b400f0638c77c525db55
This commit is contained in:
Ghanshyam Mann 2024-05-23 12:30:19 -07:00
parent 7ce8fd50b8
commit 3d29c6c10c
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
reference/house-rules.rst
View File

@ -107,13 +107,13 @@ This topic is used for other changes within an existing project team, like
addition of a new git repository or retirement of an existing repository addition of a new git repository or retirement of an existing repository
maintained by a project team. maintained by a project team.
If there is no objection posted after the addition or retirement of an We require two TC member roll call votes on a change that adds a new
existing repository is proposed (assuming the correct retirement process has repository or retires a repository under a project team. When retiring
been followed), then the change can be approved by the chair if it has at least a repository, TC members must ensure that the retirement process has been
two 2 roll call votes (which can include the vote of the chair and excludes the followed. The change can be merged by the TC chair if there is no objection
change owner) and a code review vote from the PTL of the project (or their and there are two role call votes (including their own but not including the
delegate). If the change is from the PTL or their delegate, this will count as owner of the change) and a code review vote from the PTL of the project (or
an acknowledgment code review vote. their delegate).
One exception to this would be significant team mission statement changes, 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 which should be approved by a formal vote after discussion on the mailing list