A few questions about OpenStack projects archival strategy
Dear OpenStack team,
I hope this email finds you well.
I am Ali Arabat, a PhD student in Software Engineering at École de Technologie Supérieure in Montreal, University of Quebec, Canada, conducting research studies on the evolution of multi-component systems, among which OpenStack plays a significant role. Through this email, we would like to ask a few questions related to our study on OpenStack.
Our study revealed a significant increase in the number of cross-component changes over time. However, Such cross-component changes have decreased after archiving a large number of projects beyond 500. Therefore, we would like to have clarification and answers to a few questions as follows:
What are the main factors in archiving OpenStack projects? Are there any policies established by OpenStack to archive such projects i.e., end of life? Who generally decides to abandon a given project?
We highly value your input and we genuinely appreciate your time.
Thank you for considering our request, and we look forward to your valuable input.
Best regards,
---------------------------------------
Ali Arabat Ph.D. student in Software Engineering Department of Software Engineering and IT École de Technologie Supérieure (ÉTS) | University of Quebec 1100, rue Notre-Dame Ouest, Montréal, QC H3C 1K3, Canada
On Thu, 2023-11-30 at 21:48 +0000, arabat50@gmail.com wrote:
Dear OpenStack team, I hope this email finds you well. I am Ali Arabat, a PhD student in Software Engineering at École de Technologie Supérieure in Montreal, University of Quebec, Canada, conducting research studies on the evolution of multi-component systems, among which OpenStack plays a significant role. Through this email, we would like to ask a few questions related to our study on OpenStack.
Our study revealed a significant increase in the number of cross-component changes over time. However, Such cross- component changes have decreased after archiving a large number of projects beyond 500. Therefore, we would like to have clarification and answers to a few questions as follows:
What are the main factors in archiving OpenStack projects?
the main one is the presence of active maintianers.
Are there any policies established by OpenStack to archive such projects i.e., end of life?
there is some documentation on the mechanics of what to do when retriging (arciving) a proejct https://docs.openstack.org/project-team-guide/repository.html#retiring-a-rep... including the deprecation process that we should follow https://docs.openstack.org/project-team-guide/repository.html#deprecating-a-...
im not aware if there is a single formal governace policy or not but there are several refernce documents in the governace repos on this topic this resolustion is proably the closest https://github.com/openstack/governance/blob/ceadfb2d440bdf8eb5232956983bb27... but these refecne documents are relevent too. https://github.com/openstack/governance/blob/ceadfb2d440bdf8eb5232956983bb27... https://github.com/openstack/governance/blob/ceadfb2d440bdf8eb5232956983bb27... https://github.com/openstack/governance/blob/ceadfb2d440bdf8eb5232956983bb27...
Who generally decides to abandon a given project?
the maintianers of that project followed by the TC (technical committee) formallay archiving the project when no new maintainers can be found.
We highly value your input and we genuinely appreciate your time.
Thank you for considering our request, and we look forward to your valuable input.
Best regards,
Ali Arabat Ph.D. student in Software Engineering Department of Software Engineering and IT École de Technologie Supérieure (ÉTS) | University of Quebec 1100, rue Notre-Dame Ouest, Montréal, QC H3C 1K3, Canada
participants (2)
-
arabat50＠gmail.com
-
smooney＠redhat.com