18:00:04 #startmeeting tc 18:00:04 Meeting started Tue Dec 5 18:00:04 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:04 The meeting name has been set to 'tc' 18:00:09 #info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel, where the recording will be uploaded soon. 18:00:12 #link https://www.youtube.com/channel/UCBuGwBXOmWHydSE09RM84wQ 18:00:16 Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. 18:00:19 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee. 18:00:21 #topic Roll Call 18:00:29 o/ 18:00:37 o/ 18:00:37 o/ 18:00:56 o/ 18:01:35 #info One indicated absence: knikolla 18:02:07 #info dansmith out rest of 2023 as indicated last week 18:02:30 o/ 18:02:46 #topic Follow up on tracked action items 18:02:52 #info Rosmaita work with fungi on the gerrit meta-acls (for unmaintained branch statuses) 18:03:02 i guess i should dial in 18:03:06 a bunch of stuff happened last week to report on 18:03:14 fungi: I am happy to proxy comments to the zoom chat if you have them 18:03:16 the Amendment to the Unmaintained status resolution that provides for a global openstack-unmaintained-core team merged 18:03:16 #link https://review.opendev.org/c/openstack/governance/+/900940 18:03:24 Hervé Beraud proposed openstack/governance master: [WIP] Modernize Openstack Networking Programming Model https://review.opendev.org/c/openstack/governance/+/902585 18:03:34 a Gerrit group was created: openstack-unmaintained-core 18:03:35 #link https://review.opendev.org/admin/groups/4d728691952c04b8b2ec828eabc96b98dc124d69 18:03:45 The tech-committee owns the group indirectly via the openstack-unmaintained-core-owners group 18:03:45 #link https://review.opendev.org/admin/groups/d230bd1886601f1b2bcf0e5680a8ae204e4c07b6 18:04:05 so openstack-unmaintained-core-owners will now show up for you in Your > Groups in gerrit 18:04:05 what this means is that TC members can add/remove people to/from openstack-unmaintained-core 18:04:05 but, TC members aren't member of openstack-unmaintained-core (unless explicitly added) 18:04:27 we already have 2 volunteers for openstack-unmaintained-core 18:04:27 namely, Elod Illes and Tony Breeds 18:04:39 I went ahead and added them because if they don't understand the openstack backport policy, then nobody does! 18:04:39 plus, with the openstack-unmaintained-core group initially populated, it's now self-maintaining 18:04:39 so nothing more for us to do there other than watch the excitement 18:05:04 As far as the abilities of openstack-unmaintained-core goes ... 18:05:04 This Gerrit ACL change gives the group its gerrit powers: https://review.opendev.org/c/openstack/project-config/+/902110 18:05:14 \o/ 18:05:15 #link https://review.opendev.org/c/openstack/project-config/+/902110 18:05:19 That patch also adjusts the project-config tests so that if a project team overrides the global group, they'll still have to give "abandon" permissions to the Release Managers (so they can clear out any un-merged patches before deleting an unmaintained/* branch) 18:05:58 This leaves the situation as: 18:05:58 - the global openstack-unmaintained-core group maintains all branches in all projects in Unmaintained status 18:05:58 - individual projects can opt-in to having their own ${project}-unmaintained-core teams if they really want to 18:06:26 this ^^ was mentioned in my "[tc][releases][ptl][all] 'Unmaintained' branch update" email a few weeks back 18:06:26 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ZYAZG43BLJJVXCYZVPYQX5733BYDVVNL/ 18:06:45 except maybe update Kristi's project team guide patch? 18:06:45 #link https://review.opendev.org/c/openstack/project-team-guide/+/897505 18:07:11 the final thing is that I attended the release team meeting last week and gave them an update 18:07:11 #link https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-12-01-14.00.log.html#l-28 18:07:11 they are aware that we're basically ready to go with Unmaintained branches 18:07:11 and you'll notice that in that discussion I said that the TC will help out in any way we can! 18:07:59 that's all from me 18:08:29 JayF: fwiw you can bump up your mic volume if you like :) 18:09:09 I suggested we send an email to PTLs/projects with a call to action: if you want your own unmaintained core group; create a change that looks like [example change or commit] 18:11:22 new groups do start out empty, yes. you'll need a gerrit admin to insert an initial member (we usually add the ptl at the initial member) 18:12:11 if the acl change grants permissions to an existing group, then you sidestep that problem, yes 18:14:42 #info TC consensus is to complete project team guide changes, then complete communication and execute unmaintained branch changes 18:14:54 #topic Gate Health Check 18:16:14 #info Melwitt's recent ML post about Nova gate issues is worth attention 18:16:18 no other gate issues worth discussion 18:16:23 #topic Leaderless projects 18:16:35 #link https://etherpad.opendev.org/p/2024.1-leaderless 18:17:18 #link https://review.opendev.org/c/openstack/governance/+/902623/ 18:17:24 is the top of that chain of 4 to mark inactive 18:18:07 The topic for unmaintained branch statuses implementation was handled during action items; skipping dedicated agenda item. 18:18:12 #topic 2024.1 TC Tracker 18:18:17 #link https://etherpad.opendev.org/p/tc-2024.1-tracker 18:18:46 #topic Open Discussion 18:18:58 #info Eventlet status 18:19:16 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YO5CZDVAJ6QSF734ALWSGNOQDDAIOXKI/ 18:19:30 #link https://review.opendev.org/c/openstack/governance/+/902585 18:21:04 #info OIF Board meeting 18:21:29 #info Bylaw changes impacting OpenStack have been approved by the board; TC will need to approve the related charter changes as a result. 18:26:37 i have a feeling that if we have revisions we want made to the proposed bylaws change, that's not going to happen in time for the 2024 election 18:27:19 better to consider it as a "go ahead" or "not until 2025" decision 18:27:32 the tc can make official decisions in resolutions 18:27:36 #action gmann to push up TC Charter change, in response to OIF bylaws changes, for TC to vote on 18:29:19 #action gmann to push up a TC resolution expressing approval for the approved OIF bylaws change 18:30:02 #action JayF to engage with OIF board to determine required timing for those two TC approvals 18:30:04 i was already asking foundation executives whether there's a precise deadline 18:30:38 i will let you know as soon as i find out 18:31:01 thanks 18:31:06 ++ thank you 18:31:35 cinderlib is a cycle-trailing release 18:32:32 while i'm waiting for an answer from jbryce, if we want to consider the eve of the start of the individual member director vote as a deadline, that would be 2024-01-07 18:33:13 that's probably the most conservative deadline 18:37:35 #info Cinderlib is being retired; discussed needed communication for the retirement. Suggested reaching out on mailing list as a minimum bar, reaching out to known users or on socials as a nice-to-have. 18:37:39 #link https://docs.openstack.org/project-team-guide/repository.html#deprecating-a-repository 18:37:47 Any other topics for open discussion from IRC side? 18:37:48 related to gate health, a new version of ansible has made a (minor) breaking change for security reasons, which may require revising some existing job playbooks. details can be found on the zuul-discuss ml: 18:37:56 #link https://lists.zuul-ci.org/archives/list/zuul-discuss@lists.zuul-ci.org/thread/C7A2U7HGVH2W6NV2IPCQP6KAHOZKOMXX/ Breaking change in Ansible 2.15.7 (Ansible 8) 18:38:19 this will take effect during opendev's zuul restart on saturday 18:38:37 if anyone sees interesting sudden breakage next week, this could be why 18:38:42 ++ thanks for that 18:38:48 anything else new? 18:39:08 there is the asyncio stuff 18:39:22 no word back from jbryce on a deadline for the bylaws approval yet, but i'll update the tc members in here as soon as he gets back to me 18:39:34 Thank you :) 18:40:43 clarkb: JayF mentioned the eventlet/asyncio discussion at the start of the meeting 18:40:57 ah I must've missed it while I was settlign in 18:41:07 meantioned it at the top of open discussion 18:41:11 see 18:18 timestamp here 18:41:19 I've been juggling hvac stuff 18:41:59 sounds heavy 18:42:00 #info TC consensus to cancel Dec 26 2023 and Jan 2 2024 meetings. 18:42:46 Meeting video recording will be posted to youtube shortly. 18:42:48 #endmeeting