)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"8b3d86b93beba1ff7466aa0f0227db371cf8e2cf","unresolved":true,"context_lines":[{"line_number":3,"context_line":"AuthorDate: 2025-06-27 20:52:37 +0200"},{"line_number":4,"context_line":"Commit:     Elod Illes \u003celod.illes@est.tech\u003e"},{"line_number":5,"context_line":"CommitDate: 2025-06-27 20:52:37 +0200"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Remove Monasca from active project"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Monasca was marked as inactive [1] in 2023.2 Bobcat cycle."},{"line_number":10,"context_line":"Since then release team\u0027s inconsistency check that compares governance"},{"line_number":11,"context_line":"project list with the cycle\u0027s deliverables always drops a warning that"},{"line_number":12,"context_line":"Monasca is still present in governance as active project with many"},{"line_number":13,"context_line":"deliverables."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"If there is no one who would want to resurrect Monasca, then let\u0027s"},{"line_number":16,"context_line":"move it from active project list to legacy."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"[1] https://review.opendev.org/c/openstack/governance/+/897520"},{"line_number":19,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"6285b415_7c6369d3","line":16,"range":{"start_line":6,"start_character":0,"end_line":16,"end_character":43},"updated":"2025-06-28 08:10:00.000000000","message":"Monasca is already marked as inactive (not active)[1] in governance since caracal. And TC extneded the inactive status for one more cycle in 2024.2 cycle with hope that it will become active in 2025.1. As per TC process[2], if it does not become active in 2025.1 m-2, TC should discuss it for its retirement. But we forgot to check its status. I raised this concern in TC IRC channel but no active discussion on this[3].\n\nI agree to start the retirement of Monasca as it did not become active within timeline defined by the TC. But please update the commit msg accordingly. It will be good to start the ML on this topic and if no one object on rertirement then start the retirement process[4] \n\n[1] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects\n\n[2] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#timeline\n\n[3] https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2025-06-19.log.html#openstack-tc.2025-06-19.log.html#t2025-06-19T16:42:09\n\n[4] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"52d7f6f4ab228d2e57f988d1f6c740fcdd540c97","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"612702ff_c546f868","updated":"2025-07-08 17:35:58.000000000","message":"Hey @hasan.acar@tubitak.gov.tr, @thuvh87@gmail.com:\n\nwe were wondering how things are going with the maintenance of Monasca. Is this project still useful to you? Have there been any plans to mark it \"active\"? or, would you be okay with us retiring the project?","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"03a3f399fbb9f329a85bb22bd8e3a4ed545d4117","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"638d7890_dcb6c090","updated":"2025-07-24 04:37:39.000000000","message":"Hi @thuvh87@gmail.com @hasan.acar@tubitak.gov.tr:\n\nWe discussed this proposal and further comments within the OpenStack TC and think Monasca has been \"inactive\" for over 18 months - that\u0027s beyond the timeline that we had set forth in https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#timeline\n\nWhile activity in the project is visible, we would like the project leadership to be more responsive, and we\u0027d like to set a deadline for the project team to remain \"inactive\". Could you please propose a change to openstack/governance - to this page: \n\nhttps://github.com/openstack/governance/blob/master/reference/emerging-technology-and-inactive-projects.rst#current-inactive-projects\n\nAdd \"2025.1\" and \"2025.2\" to this list. \n\nTC Discussion regarding this: https://meetings.opendev.org/meetings/tc/2025/tc.2025-07-22-17.00.log.html#l-21","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":13114,"name":"Hoai-Thu Vuong","email":"thuvh87@gmail.com","username":"thuvh"},"change_message_id":"50991f4f4a8c274e3f688e7ed65f1e0f91fc59ff","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"05494668_4deb962f","updated":"2025-07-24 04:46:17.000000000","message":"Hi, I read the meeting log. I think monasca should be moved to legacy. it\u0027s good for community health.","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":35988,"name":"Hasan Acar","display_name":"Hasan Acar","email":"hasan.acar@tubitak.gov.tr","username":"hasanacar"},"change_message_id":"6ca0246db3438bc814ca8b6f375aadd92d0a186d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"88a2cdbf_6b5b029c","updated":"2025-07-18 11:13:19.000000000","message":"Hi, sorry for the late reply! We\u0027ve been caught up with another project lately and haven\u0027t really had the chance to focus on this one. We’re still interested in the Monasca project and would love to be more involved long-term, but honestly, it’s been hard to find the time. Hoai-Thu Vuong might be interested in picking this up.","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"8b3d86b93beba1ff7466aa0f0227db371cf8e2cf","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"220c9efd_d7d38760","updated":"2025-06-28 08:10:00.000000000","message":"This project is already marked as inactive in governance. I agree on the retirement start but need to follow the retirement process -https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":17669,"name":"Doug Szumski","email":"doug@stackhpc.com","username":"DougSzumski"},"change_message_id":"f9460011d71ef960419b654c6259376b9404b39a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5364b1bb_d6cee22b","in_reply_to":"3852ff6b_94df4b1d","updated":"2025-07-18 11:00:37.000000000","message":"We have not been actively involved in the project for a long time - I see some effort has been made to maintain it. Unfortunately I don\u0027t think there is enough activity to sustain the project, and so my vote is to retire it.","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":35988,"name":"Hasan Acar","display_name":"Hasan Acar","email":"hasan.acar@tubitak.gov.tr","username":"hasanacar"},"change_message_id":"6ca0246db3438bc814ca8b6f375aadd92d0a186d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"65936c27_2557421c","in_reply_to":"5364b1bb_d6cee22b","updated":"2025-07-18 11:13:19.000000000","message":"Hi, sorry for the late reply. We\u0027ve been caught up with another project lately and haven\u0027t really had the chance to focus on this one. We’re still interested in the Monasca project and would love to be more involved long-term, but honestly, it’s been hard to find the time. Hoai-Thu Vuong might be interested in picking this up.","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"412748d1186821e9cdc68e2b5b94e3c6daf6cf68","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3852ff6b_94df4b1d","in_reply_to":"612702ff_c546f868","updated":"2025-07-14 17:37:46.000000000","message":"Opening this comment back up, and bumping this.. @hasan.acar@tubitak.gov.tr @thuvh87@gmail.com and anyone from Monasca Core team (cc\u0027ed on this review) - could you let us know how the project is doing?","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":13114,"name":"Hoai-Thu Vuong","email":"thuvh87@gmail.com","username":"thuvh"},"change_message_id":"8755c236a1d6c87c29859e74ff16d437a28722e4","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"73fa5fa1_d29b1ca5","in_reply_to":"65936c27_2557421c","updated":"2025-07-18 19:29:28.000000000","message":"Hi, I have a question, if this project move to legacy zone, will zuul\u0027s job still run? i can spend a little bit of time to work on this project","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"6591cb1af030ec0838b382db213cf7093eae908a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8ab576e7_7ab053f2","in_reply_to":"73fa5fa1_d29b1ca5","updated":"2025-07-22 04:32:53.000000000","message":"Hi @thuvh87@gmail.com, \n\nMoving the project to \"legacy.yaml\" here is an indication that we can begin closing the \"master\" branch for development. Older branches can be maintained for a while if necessary. If you plan to continue the development of Monasca, I\u0027d recommend re-constituting the core team and contesting the PTL elections (Nominations are accepted from Aug 6th 2025 [1])\n\nIs this something you can commit to?\n\n[1] https://governance.openstack.org/election/","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":13114,"name":"Hoai-Thu Vuong","email":"thuvh87@gmail.com","username":"thuvh"},"change_message_id":"c8b76c775f6d87bd791d43c12849659b86fb3035","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6fc9c34a_341cb87b","in_reply_to":"8ab576e7_7ab053f2","updated":"2025-07-22 09:42:53.000000000","message":"So, I would like keep it active. I will try maintaining project.","commit_id":"3fff4cb5680a9a3975718ca73c7799975f773d54"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"89811a25009faa2f90eba747f4b9fca6b740bea4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"82001809_5657b940","updated":"2025-09-03 21:35:36.000000000","message":"@yusuf.kaya@tubitak.gov.tr:\n\nI think we need some more feedback from you. As @fungi@yuggoth.org clarified, the \"x/\" namespace would be inappropriate to house these Monasca repositories. The TC is split on whether we should proceed with this retirement or not. We\u0027ve decided to defer the decision to a new TC that will be seated after Sep 17, 2025. \n\nFor now, I\u0027ll propose extending the \"inactive\" state through the 2025.2 release cycle: https://review.opendev.org/c/openstack/governance/+/959392\n\nIn the meantime, could you please let us know:\n\n1) What amount of time/resources are you able to dedicate to revive the Monasca Project team? The TC would like to ensure we have enough bandwidth to handle release activities, CI maintenance and upkeep while also building an open community around the project.\n\n\n2) If we lack the bandwidth, a section of the TC preferred that you fork the project code to a different namespace on opendev.org (call it \"monasca\" perhaps) - although this comes with the caveat that the existing CI jobs, including their meta configuration, such as usernames and passwords to communicate with github/pypi/etc would not work on the new repositories. If you\u0027re unfamiliar with these, it might be a steep learning curve.\n\nOfcourse, there\u0027s no obligation to keep these test jobs, or even fork the projects into opendev.org - you can choose whatever testing you prefer, or host these projects on GitHub.com or any other service.\n\nHowever, if the goal is to return this project to OpenStack governance, we\u0027d need you to follow https://governance.openstack.org/tc/reference/new-projects-requirements.html to ensure that the Monasca repos meet all the requirements to be returned.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"16260f806c20e0c9877ebd68d2768bd1d4e50904","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"43b2170b_0be53cb0","updated":"2025-08-20 16:49:51.000000000","message":"As we have new volunteer, I am changing my vote to reconsider or delay the retirement","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"276cde8250ea659f7d3e88297c07371105c0831a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"a7e8a84f_4d3d0c21","updated":"2025-08-12 05:24:26.000000000","message":"Hello, as a follow up to the discussion here and on the openstack-discuss mailing list [1], we\u0027re proceeding with the project team\u0027s retirement. I\u0027m using a hashtag: \"retire-monasca\" to track all the review changes [2]. I\u0027m also tracking these changes on this etherpad: https://etherpad.opendev.org/p/monasca-retirement\n\nPlease feel free to seek clarifications. \n\n[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/F4XQ7QU2S4WCNOVCGW3ZONI4IYX4KVFW/\n[2] https://review.opendev.org/q/hashtag:%22monasca-retirement%22+(status:open%20OR%20status:merged)","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":37533,"name":"Yusuf Kaya","display_name":"Yusuf Kaya","email":"yusuf.kaya@tubitak.gov.tr","username":"yusufkaya"},"change_message_id":"7550b64dbfcc0160605d51b9f255a9781f467c1b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"215ca9d1_6597600b","updated":"2025-08-20 07:20:47.000000000","message":"I noticed that retiring this project is currently being considered. I would like to step in and take responsibility for its maintenance and further development. I see value in keeping this project alive and would like to contribute actively to ensure it remains usable and up to date.\nIf the retirement process is unavoidable, I kindly request that the project be transferred under the X namespace instead of being retired, so that the community can still benefit from it and I can continue contributing.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"2006aa317d78fd9bf6e085ec4e367fe0c10da2f3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bbb8a639_ba311394","updated":"2025-09-30 08:34:02.000000000","message":"I prefer 959392","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"6d350ce50924f7fd78cca01c240d0d8f6dd7ab5f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8948422e_efd5e206","updated":"2025-08-29 05:36:07.000000000","message":"Let\u0027s properly retire it, it\u0027s been in limbo state for too long.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"c734acd60a873b3b9278b13c890fcb02cfb2a4d4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"a7f5b738_195967ae","updated":"2025-08-12 13:40:01.000000000","message":"Looks like we have to clear the project contents before we merge this.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"abe383572f506acbeb21f2ca7ffd0849f5874085","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"78131b30_dc962fbc","updated":"2025-08-26 17:26:31.000000000","message":"based on the evidences and the current state, I prefer it to be properly retired and then eventually come back if really the state improves, rather than awaiting for it to be better.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2b8ef084477d84b120b84f08123c75fd28224666","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"991eb279_65d96a47","updated":"2025-08-12 15:20:16.000000000","message":"proposal lgtm, gate will pass once repo contents removal are merged.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"c2ed9a75c883a9dc02ef480ab38b5bd3071190c1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"350d4c22_3a1dcf87","in_reply_to":"215ca9d1_6597600b","updated":"2025-08-20 16:35:16.000000000","message":"Unresolving comment; \n\nHi Yusuf, \n\nAre you currently using/deploying Monasca in your OpenStack Cloud? I see that you haven\u0027t contributed to this project so far; I\u0027m trying to understand your familiarity with the project\u0027s codebase, and its future maintenance. To remain under the \"openstack/\" namespace, a project (and its deliverables) have to meet several criteria which we maintain in a guide [1]. Monasca used to meet these requirements at some point, and its core maintainer team has now disbanded. So, to revert to its prior state and sustain it - it might need a team of maintainers unfortunately, and the project team must commit to its renewal [2]. \n\nI do think moving out to the x/ namespace is fine - and that would allow the project\u0027s deliverables to live on opendev.org without any OpenStack governance requirements. I\u0027ll let infra folks chime in here in case there are any other conditions.\n\ncc @fungi@yuggoth.org @cboylan@sapwetik.org","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":13114,"name":"Hoai-Thu Vuong","email":"thuvh87@gmail.com","username":"thuvh"},"change_message_id":"413b2e9bf31a73aa7664e5620fc75fbaca0f74f1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e8f27a69_b5ed661a","in_reply_to":"2edb1fbc_75c40291","updated":"2025-08-21 03:27:58.000000000","message":"I agree with you. In the past, my company used monasca and provide monitor for customers. Now, we change to another solution. And I have not enough time to maintain. So I vote for retirement.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"16260f806c20e0c9877ebd68d2768bd1d4e50904","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d09cd761_2dc5a114","in_reply_to":"350d4c22_3a1dcf87","updated":"2025-08-20 16:49:51.000000000","message":"I think if we have a volunteer to maintain it, then we should reconsider the retirement decision. \n\nI am not sure it is good idea to move it to x/ namespace, which might come back to /openstack namespace later. Also, if I remember correctly, OpenDev does not encourage projects to move to x/namespace, but instead considers some non x/ namespace.\n\nAnyways, this project is marked Inactive, and if there is a clear commitment from a new volunteer (Yusuf or a few more if there are), then we can extend the inactive state for another cycle and think of retirement after that. This will not harm or add any extra work for anyone, and give more time to the new volunteer to make it active.\n\nNOTE: We have done this for many projects when we hand over the projects to completely new maintainers who have not contributed to the project before they took the maintenance with the help of the TC. Mistral is one successful example.\n\n@yusuf.kaya@tubitak.gov.tr If you are ok, can you please add your nomination for Monasca PTL (today is the deadline, but even if that does not get merged, it will be good info for TC to consider their decision).\n- https://governance.openstack.org/election/\n- This is the process to nominate for PTL- https://governance.openstack.org/election/#how-to-submit-a-candidacy\n\nOr we have the DPL model alternative to the PTL model - https://governance.openstack.org/tc/reference/distributed-project-leadership.html","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"59534b728bfe86352567b37698493fab0adaabed","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bd56bd18_3060ded5","in_reply_to":"65cfae07_ff286f75","updated":"2025-08-22 07:41:21.000000000","message":"Thanks Ghanshyam for the patch, probably that will do the trick we (release team) need, we will be able to adapt our tool to ignore inactive projects o:)\n\n(and indeed, this was my goal. see my original commit message:\n\n    Monasca was marked as inactive [1] in 2023.2 Bobcat cycle.\n    Since then release team\u0027s inconsistency check that compares governance\n    project list with the cycle\u0027s deliverables always drops a warning that\n    Monasca is still present in governance as active project with many\n    deliverables.\n)","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"59b416abaf761d1ff0477155ac8723fa62f30a9d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"65cfae07_ff286f75","in_reply_to":"8114d9ab_86b9acfe","updated":"2025-08-21 17:16:48.000000000","message":"@elod.illes@est.tech I am still not understanding the purpose of moving it to legacy.yaml if we are not retiring this. Is this needed by release team to know if they need to release this project or not? If so then we mark the project inactive in doc[1], and that is a signal/info to the release team that these inactive projects are not going to be released in that cycle. The legacy.yaml is only kept for the history of retired projects; using that for other purposes can be confusing.\n\nFor release tooling automation (I think that is your main purpose here), we can mark the inactive project \"status:inactive\" in project.yaml. Providing inactive project info in project.yaml and other places is something we discussed many times but did not implement. I am proposing it in this change, feel free to comment/update that if anything else can be useful for release tooling.\n\n- https://review.opendev.org/c/openstack/governance/+/958229\n\n\n[1] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"a723ec64b210735b36d5ecab2693eaf6e8ef7496","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8fc74668_5010724b","in_reply_to":"82001809_5657b940","updated":"2025-09-30 18:45:04.000000000","message":"Hi @yusuf.kaya@tubitak.gov.tr\n\nBumping this again, could you please take a look and respond. We\u0027ve currently stalled the retirement of this project by extending its \u0027inactive\u0027 state through 2025.2. However, we will proceed with the retirement in case you\u0027ve changed your mind based on the comment above.\n\nThanks!","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"49c2beb0daf5b356f4eec406d5eb7141dbd67852","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"2edb1fbc_75c40291","in_reply_to":"d09cd761_2dc5a114","updated":"2025-08-20 17:49:48.000000000","message":"my vote is to continue with the retirement.  peoplo with no or almost no track record of previous contributions show up, little happens, they leave again. we have waited like 3? years for real contributions now, enough is enough. people can fork the project and maintain it outside of openstack if they want to.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"ea6a6952aff4cd88466e1fec6e683df85ec0aceb","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8114d9ab_86b9acfe","in_reply_to":"e8f27a69_b5ed661a","updated":"2025-08-21 13:09:32.000000000","message":"I\u0027m not that strict with the retirement, maybe i\u0027m too optimistic but I\u0027d rather give a chance to any new volunteer to maintain a project, even though we have the experience that volunteers tend to disappear after some short time.\n\nNevertheless, I would probably still move monasca project to legacy.yaml but without doing the complete \u0027retire\u0027 process, i.e. repository contents don\u0027t need to be deleted. monasca repositories should stay the way they are right now, but we don\u0027t plan to release them in 2026.1 Gazpacho, rather just let the new volunteers to maintain the repositories. Later on if we see that Monasca deliverables are well maintained, we can discuss about 1) moving them back from legacy.yaml to projects.yaml 2) and including them in the next coordinated release.\n\nI don\u0027t know if this is feasible, though, or is this contradicting some of our rules or causing issues with any of our tools.","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"87caa627a51fb1ff7b7e2f178fb5c5d66a79436e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3c4bf096_268c2a1b","updated":"2025-10-08 15:55:33.000000000","message":"As I said in https://review.opendev.org/c/openstack/governance/+/959392\n\nI\u0027m aware of at least one foundation member that is looking at adding Monasca into their suite in the next 6 months.   If we do have a PTL candidate I\u0027m in favor of keeping Monasca inactive with a focus on CI, community goals and tech debt.","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":13114,"name":"Hoai-Thu Vuong","email":"thuvh87@gmail.com","username":"thuvh"},"change_message_id":"ed8201a99713b3e877925c3b0963b9d86f98d651","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"2400a54b_fdc5c398","updated":"2025-10-14 02:18:49.000000000","message":"I have a question: in case i would like to release monasca, what should I do? is there any guide?\n\n\"release: means fix mirror bugs to keep monasca can work","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":13114,"name":"Hoai-Thu Vuong","email":"thuvh87@gmail.com","username":"thuvh"},"change_message_id":"75bd26ed7c7907800eea703df24616ea2fb72120","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"92d15aea_2ebb8f08","in_reply_to":"20f364fd_8fb860cf","updated":"2025-10-17 07:21:02.000000000","message":"thank you everyone. i think this question helps someone who would like to maintain monasca, can make plan easier.","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"80cb578e29ff50939daa926c17f5e36cadc80df5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"be4442ad_b4ea984a","in_reply_to":"2400a54b_fdc5c398","updated":"2025-10-14 03:12:15.000000000","message":"The general process is documented here:\nhttps://releases.openstack.org/reference/using.html#requesting-a-release\n\nHowever As monasca is currently in the inactive state I don\u0027t think that applies.  Certainly the release team doesn\u0027t have the tooling setup for monasca.\n\nMy opinion (not speaking for the TC) is that, you can\u0027t without a solid commitment to revitalising at least the monasca CI.","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"29f04b2fe6ccbe658845bc4ab048304433afea7e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":4,"id":"d463693b_3133bd59","in_reply_to":"add78360_a811966c","updated":"2025-10-15 15:42:18.000000000","message":"If I remember correctly the process for projects, that are not part of the coordinated release cycle, is to grant someone right (maybe via ACL in openstack/project-config repo) to create tags in monasca-* repositories, then that person can push tags and tagging triggers [1] the post-release jobs (publishes the package to pypi and on tarballs.openstack.org).\n\n[1] see the second step here: https://releases.openstack.org/reference/release_infra.html","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"2cd69c1e9a37a1525e7bc3aa185f0a6b906ddfd9","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":4,"id":"add78360_a811966c","in_reply_to":"be4442ad_b4ea984a","updated":"2025-10-15 03:41:22.000000000","message":"releases can be requested for \"Inactive\" projects too.. @elod.illes@est.tech can you clarify/confirm how/if this could work?","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"c89308bab53bcb9589d6d5fb6d3790dc3321f2eb","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":4,"id":"20f364fd_8fb860cf","in_reply_to":"d463693b_3133bd59","updated":"2025-10-15 19:55:55.000000000","message":"Thank you @elod.illes@est.tech\n\nIs this something you\u0027re comfortable pursuing @thuvh87@gmail.com?","commit_id":"b1f372aaab618cd999374f2bcb222c867fdc9d64"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"4ebbf16f05935ff713f63db20170928343f2dceb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"c72dea88_f528e261","updated":"2025-10-21 10:05:53.000000000","message":"As I said in https://review.opendev.org/c/openstack/governance/+/959392\n\nI\u0027m aware of at least one foundation member that is looking at adding Monasca into their suite in the next 6 months.  This was discussed in the recent TC meeting[1].\n\nThe work to bring Monasca back into good standing isn\u0027t substantially more even if it is retired.\n\n[1] https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-21-08.00.log.html#l-32","commit_id":"59590696be260c925ddbc6d3cacdb1c76f61190d"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"b249e730fdc97b5893c5ec7291fbf5ced9accefd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"837ebe38_940e30ce","updated":"2025-11-24 22:15:50.000000000","message":"Ugh, the LICENSE file was left behind in each of the 14 Monasca repos and that\u0027s causing the \"validate-legacy\" script to fail :/ \n\nFixing that would mean dropping the LICENSE file from all 14 repos; but, it\u0027ll mean that the README updates are off, so that\u0027ll have to be corrected too.. imho, something that\u0027s not worth doing. i\u0027ll just add these repos to the ignore list in a different change: https://review.opendev.org/c/openstack/governance/+/968268","commit_id":"59590696be260c925ddbc6d3cacdb1c76f61190d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"9bc6f4d95fec303d01de69865ba636c363fcc3a3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"a7d866f2_e3da6128","updated":"2025-11-24 20:57:53.000000000","message":"recheck all repos emptied","commit_id":"59590696be260c925ddbc6d3cacdb1c76f61190d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"858f10f7f4e91f29ef30a4dd685c447f33d58fb3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"9db7db27_54acfb84","updated":"2025-10-20 20:19:32.000000000","message":"so there have been a couple of \"I want to\" statements, but I haven\u0027t seen any actual action being done in terms of maintaining this project. so IMHO it is high time to proceed with the retirement, as this no longer fulfills the requirements for being under OpenStack governance. this retirement doesn\u0027t delete any git history, people can still pick up the code and continue to work with it in their own environment or even under the opendev framework if they want to","commit_id":"59590696be260c925ddbc6d3cacdb1c76f61190d"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"351964de44c6419f6365fd22a84f8116ed40f8cd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"22401880_c2c82491","updated":"2025-11-28 20:04:56.000000000","message":"@all, \n\nAlthough this patch was rebased, it doesn\u0027t reset the clock on this change merging soon. It\u0027s been around long enough (5 months) and has been discussed at length. Since the repository cleanup has now been completed, please make any comments/reviews asap. I\u0027m hoping to merge this by Monday, December 1st 2025.","commit_id":"03be45bb000dd3fcac89ce9b3fbfc18220c909d6"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"b35ab38fb31ab8c15f4c26024d8d237d45869599","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"ce267c71_e629e4a2","updated":"2025-12-01 18:48:27.000000000","message":"Approving this now and will proceed with the remaining cleanup. \n\n@yusuf.kaya@tubitak.gov.tr and others that may be interested in continuing the project outside OpenStack governance, please do let us know if we can help in any way; and thank you for your continued interest in this project.","commit_id":"03be45bb000dd3fcac89ce9b3fbfc18220c909d6"}],"reference/projects.yaml":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"15d973ac01c3aeb65ecadb2a7dc6c21c970fc1f8","unresolved":true,"context_lines":[{"line_number":784,"context_line":"    mistral-extra:"},{"line_number":785,"context_line":"      repos:"},{"line_number":786,"context_line":"        - openstack/mistral-extra"},{"line_number":787,"context_line":""},{"line_number":788,"context_line":"neutron:"},{"line_number":789,"context_line":"  ptl:"},{"line_number":790,"context_line":"    name: Brian Haley"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"4aca4b03_9b9638f2","line":787,"updated":"2025-08-14 08:07:12.000000000","message":"nit: we usually don\u0027t have empty lines between projects, so this should be dropped? fine to do in a follow-up as not to loose votes, though","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"b4f882c50cc1f84a3d3e9ec987bc02a16bd60982","unresolved":true,"context_lines":[{"line_number":784,"context_line":"    mistral-extra:"},{"line_number":785,"context_line":"      repos:"},{"line_number":786,"context_line":"        - openstack/mistral-extra"},{"line_number":787,"context_line":""},{"line_number":788,"context_line":"neutron:"},{"line_number":789,"context_line":"  ptl:"},{"line_number":790,"context_line":"    name: Brian Haley"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5be55b7a_9c944f67","line":787,"in_reply_to":"4aca4b03_9b9638f2","updated":"2025-08-14 21:04:04.000000000","message":"ack, will fix this","commit_id":"3fe28dd0cc20f770c0325693dd63091a5a4b7e04"}]}