openstack
/
governance
Code Issues Proposed changes

Merge "Clarify the timeline for project to move to Inactive state"

This commit is contained in:
Zuul 2024-05-03 19:38:50 +00:00 committed by Gerrit Code Review
parent c9f76489d4 746291ce9c
commit e76ce3cde0
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
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
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
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
@ -88,6 +94,10 @@ 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
of that project.
If TC detects inactive project or project becomes inactive after the release
milestone-2 of the cycle, TC needs to take decision based on the severity and
risk to continue the project release.
Tracking
========