Hello Stackers, Next week marks Milestone-1 of the 2024.2 (Dalmatian) release cycle [1]. So as we march on, there have been a number of governance changes that I'd like to brief you about: - The Freezer team now opted to have a distributed project leadership - Thank you for stepping up, noonedeadpunk and khyr0n! - The TC appointed a PTL for the Skyline project - Thank you for stepping up, wu_wenxiang! - The TC has decided that projects can be identified as inactive at any point during a release cycle. When this happens, we would prevent releases for the cycle from such projects. - The "openstack-helm" team has spun up a new repository: "openstack/openstack-helm-plugin," and the "openstack-ansible" team has introduced "openstack/ansible-role-frrouting." === Weekly Meeting === Last week's TC meeting was held on IRC on April 30th, 2024. The meeting was logged to eavesdrop [2]. For the past few release cycles, the OpenStack Technical Committee has been hosting a video meeting call as the first weekly meeting in each month. Last week, we discussed the platform we have been using for these video meetings. Some members expressed concerns about the recording capabilities of Jitsi/Meetpad [3] versus Zoom, while others were open to trying MeetPad again. Ultimately, it was agreed to stick with Zoom for the next meeting. When we host these meetings, we do have a simultaneous IRC conversation - i.e., every discussion is reflected on IRC for those who cannot or do not want to participate in the video meeting. We also upload the recording of the video meeting to the OpenStack TC's YouTube channel [4] for the sake of transparency and for posterity. I'm interested to know what the community thinks about this activity in the TC. Any feedback is most welcome! The discussion then moved to the TC Activities Tracker [5], where gate stability and Python 3.12 compatibility were among the topics discussed. Concerns were raised about the lack of volunteers to make DevStack run on Ubuntu 24.04, and it was noted that some projects still have issues with Python 3.12 compatibility [6]. Project teams must prioritize addressing Python 3.12 compatibility issues before the "E" (2025.1) release cycle - the sooner, the better. If you'd like to contribute your time and effort to testing DevStack with Ubuntu 24.04, please let us know, either here or on OFTC's #openstack-qa channel. This issue was also discussed at the Infra meeting [7]. During the open discussion, the topic of cleanup in global-requirements.txt was raised, particularly regarding the removal of old constraints (excludes) [8] causing issues in some projects. Patches were pushed to address these issues [8]. However, there were concerns that we were losing documentation of known bad versions of these requirements. The effort to fix this up quickly snowballed, and the requirements cleanup has now been reverted [9]. Project teams are encouraged to actively vet their requirements files and raise the minimum versions periodically. Tomorrow's meeting is our monthly Video+IRC meeting, and the call details and agenda are at [10]. We look forward to seeing you there. You're welcome to add new agenda items to weekly meetings. === Goal Proposals === I'd like to request a community review of the following OpenStack community goals and updates: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) - Add timeline to remove enforce_scope in RBAC goal (https://review.opendev.org/c/openstack/governance/+/915179) === Governance Proposals === Merged: Transition Freezer project to DPL | https://review.opendev.org/c/openstack/governance/+/914911 Add frrouting route under OpenStack-Ansible governance | https://review.opendev.org/c/openstack/governance/+/910019 Appoint Wenxiang Wu as PTL of Skyline | https://review.opendev.org/c/openstack/governance/+/915108 Add openstack-helm-plugin git repository | https://review.opendev.org/c/openstack/governance/+/916009 Clarify the timeline for project to move to Inactive state | https://review.opendev.org/c/openstack/governance/+/908880 Move distributed-project-leadership model into doc | https://review.opendev.org/c/openstack/governance/+/916822 Abandoned: Add the Woodpecker charm to OpenStack charms | https://review.opendev.org/c/openstack/governance/+/869752 (Reason: stale) Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 (Reason: stale) Move docs tools into TC governance | https://review.opendev.org/c/openstack/governance/+/914950 (Reason: disagreement) Appoint Jens Harbott as Skyline PTL | https://review.opendev.org/c/openstack/governance/+/914248 (Reason: withdrawal) The following governance proposals are actively being discussed, so please share your view! - Add option to move leaderless project to Inactive status | https://review.opendev.org/c/openstack/governance/+/914726 - Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 - Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun | https://review.opendev.org/c/openstack/governance/+/917517 - 2023 User Survey TC Question Analysis | https://review.opendev.org/c/openstack/governance/+/900516 The following governance proposals need attention: - Appoint Felipe Reyes as OpenStack Charms PTL | https://review.opendev.org/c/openstack/governance/+/914254 (Needs attention from the author) [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-30-18.00.log.html [3] https://meetpad.opendev.org [4] https://www.youtube.com/@openstack-tc [5] https://etherpad.opendev.org/p/tc-2024.2-tracker [6] https://zuul.openstack.org/builds?job_name=openstack-tox-py312&skip=0 [7] https://meetings.opendev.org/meetings/infra/2024/infra.2024-04-30-19.00.log.... [8] https://review.opendev.org/c/openstack/requirements/+/916006 [9] https://review.opendev.org/c/openstack/requirements/+/917869 [10] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting