[tc][all][karbor] Retiring the Karbor project
Arkady.Kanevsky at dell.com
Tue Nov 10 22:59:20 UTC 2020
Let’s make sure we update https://www.openstack.org/software/ with the change.
The same it true for all retiring projects.
From: Kendall Nelson <kennelson11 at gmail.com>
Sent: Tuesday, November 10, 2020 3:21 PM
To: OpenStack Discuss
Subject: [tc][all][karbor] Retiring the Karbor project
As you know, Karbor is a leaderless project for the Wallaby cycle, which means there is no PTL
candidate to lead it in the Wallaby cycle. 'No PTL' and no liaisons for DPL model is one of the criteria
which triggers TC to start checking the health, maintainers of the project for dropping the project
from OpenStack Governance.
TC discussed the leaderless project in PTG and checked if the project has maintainers and what
activities are done in the Victoria development cycle. It seems no functional changes in Karbor repos
except few gate fixes or community goal commits.
Based on all these checks and no maintainer for Karbor, TC decided to drop this project from OpenStack
governance in the Wallaby cycle. Ref: Mandatory Repository Retirement resolution  and the detailed process
is in the project guide docs .
If your organization product/customer use/rely on this project then this is the right time to step forward to
maintain it otherwise from the Wallaby cycle, Karbor will move out of OpenStack governance by keeping
their repo under OpenStack namespace with an empty master branch with 'Not Maintained' message in README.
If someone from old or new maintainers shows interest to continue its development then it can be re-added
to OpenStack governance.
With that thanks to Karbor contributors and PTLs (especially Pengju Jiao) for maintaining this project.
-Kendall Nelson (diablo_rojo)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss