[tc][all][qinling] Retiring the Qinling project
gmann at ghanshyammann.com
Mon Dec 7 20:30:46 UTC 2020
---- On Thu, 12 Nov 2020 10:26:58 -0600 Ghanshyam Mann <gmann at ghanshyammann.com> wrote ----
> ---- On Thu, 12 Nov 2020 09:23:41 -0600 Stephen Finucane <stephenfin at redhat.com> wrote ----
> > On Tue, 2020-11-10 at 13:16 -0600, Ghanshyam Mann wrote:
> > Hello Everyone,
> > As you know, Qinling 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 Qinling repos
> > except few gate fixes or community goal commits.
> > Based on all these checks and no maintainer for Qinling, 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, Qinling 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 Qinling contributors and PTLs (especially lxkong )
> > for maintaining this project.
> > No comments on the actual retirement, but don't forget that someone
> > from the Foundation will need to update the OpenStack Map available at
> > https://www.openstack.org/openstack-map and included on
> > https://www.openstack.org/software/.
> Yes, that is part of removing the dependencies/usage of the retiring projects step.
Most of the retirement patches are merged now (next is to merge the project-config and governance patch), please
merge all the dependencies removal patches to avoid any break in respective project gate/features.
> > Stephen
> > 
> > https://governance.openstack.org/tc/reference/dropping-projects.html
> >  https://etherpad.opendev.org/p/tc-wallaby-ptg
> > 
> > https://www.stackalytics.com/?release=victoria&module=qinling-group&metric=commits
> > 
> > https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html
> > 
> > https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository
> > -gmann
More information about the openstack-discuss