openstack/governance
Code Issues Proposed changes

Add option to move leaderless project to Inactive status

Browse Source 
When we have the leaderless project, we should also check the
project activity and if any project is not up to date to their
basic activies then TC should discuss it to mark Inactive.

Ref: This was discussed in previous PTG (2023.2 vPTG):
- https://etherpad.opendev.org/p/tc-2024.1-tracker#L7

Change-Id: I7bcdb6051b6504b4155df06b263ae9bd9bf11b05
This commit is contained in:
Ghanshyam Mann 2024-03-28 15:30:35 -07:00
parent 0bfee6cf42
commit f527be33b5
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
reference/house-rules.rst
View File

@ -151,8 +151,14 @@ Appointing Project Leaders/Liaisons
In a resolution regarding :ref:`leaderless programs`, the TC was granted In a resolution regarding :ref:`leaderless programs`, the TC was granted
authority to appoint the leader to any official project where the authority to appoint the leader to any official project where the
`election`_ process failed to produce a leader. The TC preference will `election`_ process failed to produce a leader. The TC should consider
be to move such project to Distributed Project Leadership model the criteria defined in `inactive projects document <../emerging-technology-and-inactive-projects>`_
to judge project inactivity. If a project can be considered inactive,
and no one has volunteered to lead the project as their PTL, the project
can automatically be marked as Inactive. If there are volunteers to lead
a seemingly inactive project, the TC can appoint the volunteers as leaders
and monitor the project's activity. The TC preference will be to move such
project to Distributed Project Leadership model
(see :doc:`/resolutions/20200803-distributed-project-leadership`) than (see :doc:`/resolutions/20200803-distributed-project-leadership`) than
appointing the PTL. When this happens, ``reference/projects.yaml`` in the appointing the PTL. When this happens, ``reference/projects.yaml`` in the
``governance`` repository should be updated to indicate the DPL model ``governance`` repository should be updated to indicate the DPL model