openstack/governance
Code Issues Proposed changes

Modify the timeline for project to move to Inactive state

Browse Source 
Currently we try to monitor and move the inactive project to
Inactive state before milestone-2 which is deadline from the
release team. But there are chances that project can become inactive
after milestone-2 and in that case we should mark it Inactive in
that cycle itself so that user of it get a clear message about
their maintenance status.

Modifying the process doc to explicitly cover this case.

Change-Id: I0c3908c93bc12db1fb8ef0d2c433352a83e49554
This commit is contained in:
Ghanshyam Mann 2024-02-12 21:30:18 -08:00
parent e2a47de10a
commit e69637440f
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
reference/emerging-technology-and-inactive-projects.rst
View File

@ -74,6 +74,12 @@ If project is not able to become an official OpenStack project within that
timeframe, TC will discuss with the team if more time is required for the timeframe, TC will discuss with the team if more time is required for the
project to meet the :doc:`new-projects-requirements` or will retire the project. project to meet the :doc:`new-projects-requirements` or will retire the project.
The TC will monitor the existing projects at different stages of the development
cycle and if any project becomes inactive due to lack of maintainers and is not
able to do the mandatory activities then the project will be marked as inactive.
We will try to detect and mark a project inactive in the early stage of the
development cycle but it can happen at any phase of development cycle.
An existing project should be reinstated as an active OpenStack project before An existing project should be reinstated as an active OpenStack project before
the release milestone-2 of the cycle they entered the ``inactive`` state to the release milestone-2 of the cycle they entered the ``inactive`` state to
become ``active`` again and to be released in that cycle. In the case where an become ``active`` again and to be released in that cycle. In the case where an
@ -88,6 +94,13 @@ state, the TC will discuss with the team if project will be retired before the
release milestone-2 of the cycle. In such a case there will be no new releases release milestone-2 of the cycle. In such a case there will be no new releases
of that project. of that project.
If any project becomes inactive after the release milestone-2 of the cycle, the
TC will inform release team so that they can decide on their release for that
cycle.
For inactive project, we can try (if their gate allow us) to add an inactive status
warning in the project ``README.rst`` file.
Tracking Tracking
======== ========