[tc][all][qinling] Retiring the Qinling project
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[1]. TC discussed the leaderless project in PTG[2] 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[3]. 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 [4] and the detailed process is in the project guide docs [5]. 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. [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] https://etherpad.opendev.org/p/tc-wallaby-ptg [3] https://www.stackalytics.com/?release=victoria&module=qinling-group&metric=commits [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-repositor... [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-rep... -gmann
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[1]. TC discussed the leaderless project in PTG[2] 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[3]. 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 [4] and the detailed process is in the project guide docs [5]. 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/. Stephen [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] https://etherpad.opendev.org/p/tc-wallaby-ptg [3] https://www.stackalytics.com/?release=victoria&module=qinling-group&metric=commits [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-repositor... [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-rep... -gmann
Out of curiosity, and surely someone from the foundation will need to answer this question, but is there any plan to begin to migrate the openstack.org website to more community control or edit community capability since it has already been updated to be much more about the project and not the foundation? For example, for ironicbaremetal.org, we're able to go update content by updating one of the template files the site is built with, in order to fix links, update the latest version, etc. The openstack.org site is far more complex though so maybe it is not really feasible in the short term. Anyway, just a thought. Julia On Thu, Nov 12, 2020 at 7:26 AM Stephen Finucane <stephenfin@redhat.com> wrote:
[trim]
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/.
Stephen
[trim]
---- On Thu, 12 Nov 2020 09:38:34 -0600 Julia Kreger <juliaashleykreger@gmail.com> wrote ----
Out of curiosity, and surely someone from the foundation will need to answer this question, but is there any plan to begin to migrate the openstack.org website to more community control or edit community capability since it has already been updated to be much more about the project and not the foundation?
openstack-map repo is currently in OSF namespace but anyone can submit the changes and approval on changes is from Foundation. Example: Tricirlce retirement - https://review.opendev.org/#/c/735675/ -gmann
For example, for ironicbaremetal.org, we're able to go update content by updating one of the template files the site is built with, in order to fix links, update the latest version, etc. The openstack.org site is far more complex though so maybe it is not really feasible in the short term.
Anyway, just a thought.
Julia
On Thu, Nov 12, 2020 at 7:26 AM Stephen Finucane <stephenfin@redhat.com> wrote:
[trim]
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/.
Stephen
[trim]
Julia Kreger wrote:
Out of curiosity, and surely someone from the foundation will need to answer this question, but is there any plan to begin to migrate the openstack.org website to more community control or edit community capability since it has already been updated to be much more about the project and not the foundation?
For example, for ironicbaremetal.org, we're able to go update content by updating one of the template files the site is built with, in order to fix links, update the latest version, etc. The openstack.org site is far more complex though so maybe it is not really feasible in the short term.
That's definitely the general direction we want to take with openstack.org, but it will take a lot of time to separate out the various backends involved. Regarding the map, as Ghanshyam says, the requirements are driven from the osf/openstack-map repository so please submit any change there. I'll take the opportunity to remind people that the YAML data in that repository also directly drives the content for the openstack.org/software pages. So if you want to modify how each project appears there, that's already doable. -- Thierry
---- On Thu, 12 Nov 2020 09:23:41 -0600 Stephen Finucane <stephenfin@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[1].
TC discussed the leaderless project in PTG[2] 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[3].
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 [4] and the detailed process is in the project guide docs [5].
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. -gmann
Stephen
[1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] https://etherpad.opendev.org/p/tc-wallaby-ptg [3] https://www.stackalytics.com/?release=victoria&module=qinling-group&metric=commits [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-repositor... [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-rep...
-gmann
---- On Thu, 12 Nov 2020 10:26:58 -0600 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ----
---- On Thu, 12 Nov 2020 09:23:41 -0600 Stephen Finucane <stephenfin@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[1].
TC discussed the leaderless project in PTG[2] 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[3].
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 [4] and the detailed process is in the project guide docs [5].
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.
Updates: 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. https://review.opendev.org/q/topic:%22retire-qinling%22+(status:open%20OR%20...) -gmann
-gmann
Stephen
[1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] https://etherpad.opendev.org/p/tc-wallaby-ptg [3] https://www.stackalytics.com/?release=victoria&module=qinling-group&metric=commits [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-repositor... [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-rep...
-gmann
participants (4)
-
Ghanshyam Mann
-
Julia Kreger
-
Stephen Finucane
-
Thierry Carrez