18:00:08 <gouthamr> #startmeeting tc
18:00:08 <opendevmeet> Meeting started Tue Feb 25 18:00:08 2025 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:08 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:08 <opendevmeet> The meeting name has been set to 'tc'
18:00:18 <gouthamr> 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:21 <gouthamr> Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
18:00:24 <gouthamr> #topic Roll Call
18:00:27 <noonedeadpunk> o/
18:00:32 <slaweq> o/
18:00:34 <gtema> o/
18:00:44 <mharley[m]> o/
18:01:39 <gouthamr> noted absence: g m a n n, c a r d o e, s p o t z, b a u z a s
18:02:41 <frickler> \o
18:04:10 <gouthamr> i think that's everyone, thank you for joining.. lets get started
18:04:16 <gouthamr> #topic Last Week's AIs
18:04:37 <spotz[m]> Here for the start any ways:) But will fade away in 20
18:05:32 <gouthamr> we took an AI regarding the electoral roll generation to include TC repos
18:06:13 <gouthamr> i proposed extra-acs as an example to the tc-repos
18:06:19 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/942296 (Add Extra-ACs to the tech committee repos)
18:07:56 <gouthamr> #link https://review.opendev.org/c/openstack/election/+/941612 (Add tc repositories for electoral roll generation)
18:08:13 <gouthamr> i need some reviews on the extra-acs
18:08:50 <gouthamr> that's all for this AI..
18:08:55 <gouthamr> next one, EOL transition process for unmaintained branches
18:09:47 <gouthamr> #link https://review.opendev.org/c/openstack/releases/+/941458 (Transition unmaintained/wallaby to EOL)
18:09:47 <gouthamr> #link https://review.opendev.org/c/openstack/releases/+/942201 (Transition unmaintained/xena to EOL)
18:09:47 <gouthamr> #link https://review.opendev.org/c/openstack/releases/+/942218 ([8] Transition unmaintained/yoga to EOL)
18:10:01 <gouthamr> ^ thanks for posting these, frickler
18:10:07 <gouthamr> anything to mention wrt these?
18:10:41 <frickler> I updated things a bit according to what elodilles wanted. no other feedback
18:12:41 <gouthamr> ack, ty
18:12:54 <gouthamr> next up, reviewing CI usage patterns and highlight outliers for optimization
18:13:12 <gouthamr> slaweq: we took an AI to post your findings to the ML
18:13:27 <slaweq> ahh, sorry, I forgot to send it
18:13:36 <slaweq> I will do it tomorrow morning for sure
18:13:39 <slaweq> sorry about that
18:14:06 <gouthamr> no problem at all :)
18:14:20 <gouthamr> project teams are distracted with the Feature Freeze this week anyway
18:14:27 <gouthamr> so no rush.. i can check back on this next week
18:14:37 <slaweq> thx
18:14:38 <gouthamr> that's all the new AIs we had, besides the ones in the TC tracker
18:14:51 <gouthamr> was anyone else working on any other AIs?
18:15:24 <gouthamr> sounds like none..
18:15:45 <gouthamr> #topic PTG Planning
18:15:54 <gouthamr> the PTG Planning etherpad is here:
18:16:08 <gouthamr> #link #link https://etherpad.opendev.org/p/apr2025-ptg-os-tc (OS-TC Flamingo PTG Etherpad)
18:16:33 <gouthamr> its got topics and notes from our discussions in the past few weeks
18:16:46 <gouthamr> please feel free to expand these and throw in new items
18:17:13 <gouthamr> we have a bit over a whole month to organize the discussions
18:17:24 <gouthamr> and gather relevant folks
18:17:44 <gouthamr> that's all that needed to be said about the PTG for now..
18:17:54 <gouthamr> any questions/concerns to note regarding $topic?
18:18:29 <spotz[m]> I will be PTO during the PTG
18:18:48 <gouthamr> spotz[m]: ah, bummer
18:19:10 <gouthamr> we'll be sure to record things as usual :) so do enjoy the PTO
18:19:38 <spotz[m]> I’ll be in the UK bumming around:)
18:19:58 <gouthamr> nice!
18:20:31 <mharley[m]> Hi, folks. First time in this room. I’m the candidate for Barbican PTL.
18:20:31 <mharley[m]> Not sure if this is the right time to mention it or if there will be a specific time to discuss it.
18:20:50 <fungi> that's the next topic in the agenda, looks like
18:21:02 <gouthamr> mharley[m]: ack, ty for joining us.. we'll get to that topic next
18:21:03 <spotz[m]> Once a Barbicaneer always a Barbicaneer!
18:21:29 <mharley[m]> TY
18:21:44 <gouthamr> if you haven't already, do register for the PTG: https://ptg.openinfra.org/ - doing this will add you to an email list for updates
18:22:03 <gouthamr> and allow the event organizers to gather attendance statistics
18:22:51 <gouthamr> alright lets move on to the next topic..
18:22:56 <gouthamr> #topic 2025.2 Elections
18:23:13 <gouthamr> ^ i've renamed the topic to begin discussing from the top
18:23:32 <gouthamr> first off, thanks for all the hard work on the elections slaweq and ianychoi
18:23:52 <gouthamr> thanks also for new and returning PTLs and TC members
18:24:23 <gouthamr> slaweq: what election processes are left to complete?
18:25:07 <gouthamr> i see a couple of changes that need to merge:
18:25:08 <gouthamr> #link https://review.opendev.org/c/openstack/election/+/942506 (Close 2025.2 Election Results)
18:25:30 <spotz[m]> Time I think at least for TC due to campaigning
18:25:54 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/942507 (Add TC/PTL results from 2025.2 election)
18:26:26 <gouthamr> ^ this needs to be rebased since we merged liaisons for Ironic that updated its leadership_type
18:27:19 <gouthamr> spotz[m]: yes; there was an update made to the previously published election schedule this week
18:27:44 <gouthamr> s/made/proposed//
18:28:07 <slaweq> there is no voting needed, so I think that on Thursday we can merge patches propsed by ianychoi and I will send email to conclude the whole process and we should be good I think
18:28:22 <gouthamr> ++
18:28:23 <gouthamr> https://review.opendev.org/c/openstack/election/+/942506/1/configuration.yaml
18:29:22 <fungi> i'll note that there's an openinfra foundation newsletter going out tomorrow and i'd like to congratulate the newly-elected tc members and ptls, but not sure what i should link to at this point, especially if they won't be officially announced until the next day
18:29:26 <gouthamr> does the new PTL/TC term begin after Epoxy RC1 has been tagged?
18:30:31 <gouthamr> fungi: yeah :(
18:31:14 <fungi> technical committee members have traditionally taken their seats as of the next meeting following the election, though i don't recall how we handled it in the past elections where no poll was required
18:31:34 <gouthamr> yes ^ i was trying to find examples of what we may have done
18:32:05 <fungi> with ptl's it's a little fuzzy and generally up to the teams, but where there are strong ties to the release cycle they sometimes start at rc1 because things merging to master thereafter are targeting the subsequent release
18:32:26 <fungi> other teams have approached it more around ptg planning
18:32:48 <gouthamr> the last time the TC was seated without elections was 2023.2
18:32:48 <gouthamr> https://governance.openstack.org/election/results/bobcat/tc.html
18:33:29 <frickler> IMHO it would make sense to wait until the end of the planned election period, so the cutover would happen at the same time whether an actual election is needed or not
18:33:54 <gouthamr> ^ i agree
18:34:18 <gouthamr> imho we don't really need to adjust anything whether or not elections occur..
18:34:36 <frickler> so that's for the governance change. the election results change could be merged right away
18:34:51 <gouthamr> i agree with the officials announcing results when they prefer - for now they've set the date as 2025-02-26
18:35:17 <gouthamr> which basically would have been the beginning of the poll period
18:36:58 <gouthamr> any reason to not do this?
18:37:49 <slaweq> It can be. I just didn't want to do it while officially we are still in the campaign period
18:38:09 <gouthamr> this = slaweq and ianychoi can merge the election results in the election repo on  2025-02-26 as they've planned, we merge the governance change after that with enough TC folks voting for it
18:39:19 <gouthamr> slaweq: makes sense
18:39:51 <gouthamr> i think we can spell this bit down in the election processes
18:40:09 <gouthamr> its not unusual for us to skip elections - has happened a few times before
18:40:19 <gouthamr> and we don't need one off solutions each time this has happened
18:40:24 <frickler> +1
18:41:10 <gouthamr> okay, hearing no objections
18:41:37 <fungi> for the 2023.2 election, james replaced arne, elections were closed out with https://review.opendev.org/c/openstack/election/+/874970 which merged 2023-02-24, the election configuration for that round had nominations end 2023-02-15 with voting scheduled to conclude 2023-03-08, so the election results were merged during what would have been the campaigning period
18:41:39 <gouthamr> fungi: sorry about the newsletter - maybe you could still share the anticipation that results of the election will be available a day later :)
18:41:58 <gouthamr> fungi: ah
18:42:28 <gouthamr> thanks for finding that..
18:42:32 <slaweq> if you are all ok with this, I can merge this election results patch tomorrow morning
18:42:53 <gouthamr> works for me, it is the date you've mentioned: 2025-02-26
18:43:26 <gouthamr> and i can follow up with the governance change.. (please review and +1)
18:44:05 <frickler> we need to talk about oslo being leaderless due to the DPL reset, so nobody can approve release patches. at the same time there are release critical bug fixes that are waiting for a release
18:44:33 <mharley[m]> So, my candidacy patch failed in Zuul because the last year I was mostly working on downstream.
18:44:33 <mharley[m]> For this year, I plan to get more engaged with upstream.
18:45:24 <gouthamr> thanks, lets switch to this sub-topic of "leaderless" project teams
18:45:33 <gouthamr> mharley[m]: can you propose a patch like: https://review.opendev.org/c/openstack/governance/+/928881
18:45:51 <gouthamr> you can abandon https://review.opendev.org/c/openstack/election/+/942110 since it cannot merge
18:46:01 <frickler> it needs to be based upon the results patch
18:46:09 <frickler> which needs a rebase itself first
18:46:11 <gouthamr> ^ yes
18:47:09 <mharley[m]> gouthamr: apologies, but I’m a bit confused. So I have to submit a new candidacy patch?  Is that what you’re saying?
18:47:36 <frickler> mharley[m]: not for candidacy but for appointment
18:47:52 <mharley[m]> I’m out of home now. Sorry if it’s a basic question, but don’t have access to my laptop.
18:47:53 <gouthamr> mharley[m]: no, not a candidacy.. if your nomination hasn't merged by the nomination deadline, the TC needs to find/appoint a project lead
18:47:57 <fungi> different repository
18:48:11 <fungi> governance instead of election
18:48:11 <gouthamr> mharley[m]: and that's done directly on the "openstack/governance" repository
18:48:42 <gouthamr> mharley[m]: so when you're able to, follow https://review.opendev.org/c/openstack/governance/+/928881 as an example, and add your details under the "barbican" project
18:49:01 <mharley[m]> OK, so the action item from my side is to submit a patch in the governance repository as the last link above, right?
18:49:22 <gouthamr> yes, and abandon your election patch: https://review.opendev.org/c/openstack/election/+/942110
18:49:33 <gouthamr> beware of what frickler just mentioned as well, though
18:50:00 <mharley[m]> Gotcha. This needs to be done tonight (I’m in Europe), since the merge will happen tomorrow morning. Is that correct?
18:50:12 <gouthamr> your change to openstack/governance will need to follow the other update we're making: https://review.opendev.org/c/openstack/governance/+/942507
18:50:18 <gouthamr> mharley[m]: nope, no rush
18:50:54 <mharley[m]> I’ll check those links tomorrow then.
18:51:02 <gouthamr> mharley[m]: a bit about this process.. do it as soon as you're able.. but, if you delay, we'll ping you :D
18:51:23 <fungi> the election results change merging tomorrow simply records the outcome of elections the officials oversaw, appointments for missing ptls are a separate process handled by the tc
18:51:34 <mharley[m]> Understood, gouthamr.
18:51:56 <mharley[m]> * Understood, gouthamr and fungi.
18:52:28 <gouthamr> mharley[m]: and when you do have the patch up, the patch will gather reviews for at least a week.. so things will seem to be slow.. its good to keep a watch in case the patch needs to change due to comments, or you need to resolve merge conflicts
18:53:23 <gouthamr> i do appreciate that you're at the right meeting, asking the right questions :)
18:54:43 <mharley[m]> My pleasure. Yep, got a participation advice from dmendiza. 😉
18:55:04 <gouthamr> frickler: about oslo,
18:55:17 <gouthamr> frickler: damani and tkajinam are still the release liaisons
18:55:48 <gouthamr> can you share what's blocked now?
18:56:22 <gouthamr> frickler: oslo's 2025.2 leadership is uncertain, but, tkajinam did mention that he can continue to be release liaison and assist when possible
18:56:25 <frickler> https://review.opendev.org/c/openstack/releases/+/942681 is one example
18:56:46 <frickler> so the automatic check doesn't trigger even if tkajinam proposed the change
18:57:08 <gouthamr> oh :(
18:57:14 <gouthamr> can you override it/
18:57:53 <gouthamr> since this is two processes being at loggerheads with each other
18:58:13 <gouthamr> we reset the liaisons prior to elections, and don't add them back until after elections..
18:58:38 <frickler> well technically I can, but as I said in the release channel, having formal TC approval would seem better to me
18:58:40 <gouthamr> and the release liaison (or PTL) is necessary to trigger the PTL-Approved vote
18:58:57 <gouthamr> ack, i can clarify on the patch
18:59:34 <frickler> ok, thx
19:00:21 <gouthamr> alright, we're at time
19:00:47 <gouthamr> we can continue discussing the leaderless projects.. but i think its worth sharing the process on the ML because we had some late nominations that need appointments
19:01:25 <gouthamr> i don't think we'll resolve the leadership situation with oslo right away though.. i'll add an item to the team's meeting agenda
19:02:22 <gouthamr> thank you all for attending
19:02:24 <slaweq> o/
19:02:27 <gouthamr> #endmeeting