Hello Stackers,

We're counting down 19 weeks to the 2024.2 (Dalmatian) release [1], and it's been a week of spring cleaning at the OpenStack Technical Committee. This is likely the case with project repositories across the board. There have been a few governance changes in the past week that I'd like to brief you on.

At the outset, we merged an update to the upper-constraints, allowing SQLAlchemy 2.0, dropping sqlalchemy-migrate, and bumping the version of Alembic [2]. If you happen to meet Stephen Finucane (sfinucane) in person, do buy him a beverage of his choice, or several. This was no small effort. Thanks, Stephen!

Over the past several releases, we've seen decreased activity in some OpenStack projects. We tagged these projects as "Inactive" [3] during past release cycles. We pursued the retirement of some of these projects in the past week. A shout out to Ghanshyam Mann (gmann) for driving this effort! We followed our process on project team removals [4]. It's possible, however, that there are unexpected side effects of deleting code in these project repositories. This could be CI jobs failing in actively maintained projects because they relied on deleted code from retired repositories or documentation updates that we missed. Please bear with us as we learn and adjust, and do let us know if we could improve the tooling or our retirement process.

=== Weekly Meeting ===

Last week's IRC meeting coincided with the Sovereign Cloud Stack Summit (May 14th) and the Open Infra Day (May 15th) in Berlin, Germany. However, we had a quorum and were able to go through a number of important discussion items [5].

- We discussed the removal of eventlet and migration to other concurrency/threading patterns. The consensus remained that shared tooling like oslo libraries should not dictate a specific threading model. A suggestion was made for the TC to provide recommendations rather than enforce a specific model. We're looking for help with this! All projects currently relying on eventlet must be finding ways to remove their use of it, and we're looking to use your expertise to frame a recommendation across the board. - On the topic of cleaning up additional maintainers on OpenStack packages on PyPi, Clark Boylan (clarkb) and Jeremy Stanley (fungi) helped me isolate PyPi repositories that "openstackci" didn't have permissions to make edits. We have earmarked [6] packages where we'll be removing additional maintainers this week. There's more work to be done here. So please keep an eye on future updates. - Dan Smith (dansmith) revived an old effort to setup OSC as a service on devstack; the patch has now merged [7]. Please consider using it locally and on CI jobs if you would like the speedup. There are some CI changes popping up already [8].

Our next weekly IRC meeting is tomorrow. The agenda for this meeting is up [9]. Please join us, and remember, you can always add new meeting items!

=== Governance Proposals ===

==== Merged ====

Retire Solum project | https://review.opendev.org/c/openstack/governance/+/919211 Retire Murano project | https://review.opendev.org/c/openstack/governance/+/919358 Retire Sahara project | https://review.opendev.org/c/openstack/governance/+/919374 Retire Senlin project | https://review.opendev.org/c/openstack/governance/+/919347 Retire ec2-api project | https://review.opendev.org/c/openstack/governance/+/919394 Neutron: Retire networking-ovn | https://review.opendev.org/c/openstack/governance/+/919700

==== Open for review/discussion ====

Migrate eventlet usages to asyncio | https://review.opendev.org/c/openstack/governance/+/902585 Clarify the project retirement vs project's repository retirement | https://review.opendev.org/c/openstack/governance/+/919984 Retire devstack-gate | https://review.opendev.org/c/openstack/governance/+/919629 Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833

And finally, the OpenStack Technical Committee serves you! We're always willing to chat with you and would love feedback.

=== How to contact the TC === You can reach out to the TC in multiple ways: 1. Email: you can send an email with the tag [tc] on this email list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [9].

Thank you very much for reading!

On behalf of the OpenStack TC,

Goutham Pacha Ravi (gouthamr) OpenStack TC Chair

[1] https://releases.openstack.org/dalmatian/schedule.html [2] https://review.opendev.org/c/openstack/requirements/+/879743 [3] https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... [4] https://governance.openstack.org/tc/reference/dropping-projects.html [5] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-14-18.00.log.html [6] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 [7] https://review.opendev.org/c/openstack/devstack/+/676016 [8] https://review.opendev.org/q/topic:%22ocaas%22 [9] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting