openstack/governance
Code Issues Proposed changes

Clarify the project retirement vs project's repository retirement

Browse Source 
In TC house rule, we introduced the project-updates topic so that
we can speed up the process for updates (including addition or retirement
of repository) in existing projects. But this was not meant for the
retirement of complete project. Any retirement of complete project
or a new project application are the big change in OpenStack umbrella
and should require the detailed discussion. That is why it should fall
under formal-vote topic.

For retiring the projct, we have been using the mixed topic where
sometime we use formal-vote and sometime project-updates.

Clarfiy the same in our house rule doc also.

Change-Id: I591c92fb84b5ca22905cf703be3c27f690899513
This commit is contained in:
Ghanshyam Mann 2024-05-17 12:07:13 -07:00
parent 1c4f3b0078
commit 7ce8fd50b8
1 changed files with 13 additions and 8 deletions

21
reference/house-rules.rst

@ -104,20 +104,25 @@ Other project team updates
:Gerrit topic: ``project-update``
This topic is used for other changes within an existing project team, like
addition of a new git repository or retirement.
addition of a new git repository or retirement of an existing repository
maintained by a project team.
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)
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.
If there is no objection posted after the addition or retirement of an
existing repository 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) 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
or the gerrit change.
A new project team application or retirement of a project team should be
approved by a formal vote after discussion on the mailing list or the
gerrit change.
If a technical committee member disagrees with the addition or retirement of a
project, they can propose a revert which would then be discussed by our usual
``formal-vote`` rules.