18:00:06 <gouthamr> #startmeeting tc
18:00:06 <opendevmeet> Meeting started Tue Jan 28 18:00:06 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:06 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:06 <opendevmeet> The meeting name has been set to 'tc'
18:00:24 <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:29 <gouthamr> Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
18:00:32 <gouthamr> #topic Roll Call
18:00:42 <slaweq> o/
18:00:44 <bauzas> \o
18:00:50 <noonedeadpunk> o/
18:00:53 <frickler> \o
18:01:08 <gouthamr> noted absence: c a r d o e
18:01:54 <gtema> o/
18:02:49 <gouthamr> courtesy ping: spotz[m] gmann
18:05:28 <gouthamr> alright we're at :05 and have quorum, lets get started
18:05:37 <gouthamr> #topic Last week's AIs
18:06:00 <gouthamr> we had one on the review permissions for openstackdocstheme
18:06:30 <gouthamr> gtema: i did see some buzz on #openstack-oslo, did you get your concerns addressed?
18:06:41 <gtema> nope
18:07:08 <gtema> I wasn't following since I have not joined the room so far
18:07:14 <gtema> but permissions are not there
18:07:33 <gouthamr> ah ack; they were hashing out a good time to restart meetings; and this topic remains on their agenda for when they do
18:07:48 <gouthamr> lets check back on this..
18:08:06 <gouthamr> next AI was around election setup.. we can cross this one out
18:08:49 <gouthamr> bauzas: thanks for setting up the election config, and slaweq sent out the kick off email.. the official nomination period opens in 8 days (5th Feb), but, we did see a couple early nominations
18:09:14 <bauzas> already ? cool
18:09:25 <gouthamr> my bad, just one so far ..
18:09:46 <gouthamr> but for the right, anticipated reason: "Pushing that out so early, because I will be off 1-14th Feb"
18:10:08 <gouthamr> zuul voted +1 too, so this looks nice
18:10:39 <gouthamr> ianychoi posted that he/slaweq will review this once the nomination window opens officially
18:10:55 <slaweq> yeap
18:10:55 <gouthamr> #link https://review.opendev.org/c/openstack/election/+/939935 (early nomination)
18:10:57 <slaweq> we will do
18:11:03 <gouthamr> ++
18:11:39 <gouthamr> the last AI we were tracking was around Freezer releases for this cycle
18:12:11 <gouthamr> noonedeadpunk proposed this one
18:12:21 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/939792 (Add resolution for late Freezer release)
18:13:09 <gouthamr> ^ please add to your review queue
18:13:23 <gouthamr> that's all the AIs I was tracking, did anyone have anything else?
18:16:19 <gouthamr> okay, lets move on:
18:16:23 <gouthamr> #topic DPL model reset
18:17:05 <gouthamr> #link https://review.opendev.org/q/hashtag:%22dpl-reset%22+(status:open+OR+status:merged+OR+status:abandoned)
18:17:22 <gouthamr> we have three patches left to circle back on here ^
18:17:44 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/939488 (Reset the DPL model for Watcher project)
18:18:21 <gouthamr> ^ i'd like some eyes on this change in particular since the team has proposed follow up patches
18:19:12 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/940167 (Adopt DPL model for watcher 2025.2)
18:19:24 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/940168/ (add watcher project update liaison)
18:19:27 <noonedeadpunk> I wonder how we're gonna land these
18:19:36 <noonedeadpunk> as apparently first one we need to abandon?
18:19:54 <noonedeadpunk> or well...
18:20:01 <gouthamr> no, merge :( i find that kinda silly, but, it works
18:20:25 <noonedeadpunk> merging smth that have so many -1 would hurt eyes
18:20:32 <cardoe> We floated using DPL for Ironic at some point.
18:20:44 <gouthamr> reset and then reset the reset - but achieve the objective that we'd allow the one inactive liaison to be removed if they're not showing up
18:20:53 <cardoe> So would like to see how it progresses.
18:20:54 <gouthamr> oy cardoe, eyes on the road
18:21:31 <cardoe> I’m the passenger! Just didn’t know if I would have service.
18:21:39 <noonedeadpunk> but then re-add as project_update_onboarding?
18:21:55 <noonedeadpunk> it's very compicated way of doing that... but yeah, will work.
18:22:28 <gouthamr> cardoe: hahaha, thanks for chiming in.. makes sense regarding ironic, the team would need to discuss it and nominate liaisons starting next week
18:22:35 <gmann> o/ sorry I am late.
18:23:05 <gouthamr> noonedeadpunk: yes, the re-adding could be held off until chenker responds, apparently they've been inactive through this epoxy cycle
18:23:35 <gmann> yeah, main idea here is to refresh the liaison so merging the reset DPL is no harm
18:24:02 <cardoe> So won’t be this cycle
18:24:26 <cardoe> But just looking at how it goes. Since it bounces around a bit.
18:24:30 <gmann> even a single liaison is not active there is no harm to reset model first and then adopt it again with active liaison
18:25:09 <gmann> we have time till feb 5th to finalize the DPL projects and the rest all goes for election
18:25:12 <gouthamr> ack
18:25:20 <gouthamr> can we drop this one, gmann?
18:25:26 <gouthamr> #link https://review.opendev.org/c/openstack/governance/+/939486 (Reset the DPL model for Release project)
18:26:10 <gmann> gouthamr: done
18:27:01 <gmann> for olso, it might go for PTL but we need to wait for Daniel response. I think it is ok he Daniel would like to go with PTL model
18:27:30 <gmann> gouthamr: can you reachout to Daniel  about it either continue DPL or confirm for the PTL?
18:27:49 <gouthamr> ack can do gmann
18:27:53 <gmann> we try to chat but TZ is not matching with our msg to each other
18:27:56 <gmann> thanks
18:28:29 <gouthamr> alright, that covers all the teams.. anything else regarding $topic?
18:29:20 <gouthamr> #topic A check on gate health
18:29:31 <gouthamr> any gate flakiness to report this week?
18:30:05 <gmann> I did not notice any
18:30:14 <gmann> things merging in regular way last week
18:30:52 <bauzas> nothing I sa
18:30:54 <bauzas> saw*
18:31:42 <gouthamr> ack ty, not jinxing it :)
18:32:03 <gouthamr> #topic TC Tracker
18:32:07 <gouthamr> #link https://etherpad.opendev.org/p/tc-2025.1-tracker (Technical Committee activity tracker - 2025.1)
18:32:55 <gouthamr> i'll go through this and add some status updates
18:34:23 <gouthamr> #link https://review.opendev.org/c/openstack/releases/+/937515 (Transition unmaintained/victoria to EOL)
18:34:52 <gouthamr> ^ we're approaching the deadline for this (2025-01-31)
18:35:33 <frickler> still no actionable feedback sadly. and no other -1 response than elodilles_pto's
18:36:30 <gouthamr> ah, hopefully elod gets back on what repos we should ignore.. else this looks good to merge
18:37:16 <gouthamr> it'd be ugly to undo this in parts if we don't get a response, correct?
18:37:57 <frickler> undoing eol tags? that's essentially not possible
18:38:18 <gouthamr> no, leave the tags behind but re-create branches
18:39:08 <frickler> then the cleanup tool would want to delete the branches again everytime it is run
18:39:50 <gouthamr> haha, that'd not be fun..
18:40:24 <gouthamr> i do hope we get some response before 30th Jan (the real deadline according to the commit message)
18:41:09 <gouthamr> any other tracker items to bring up?
18:41:59 <gmann> do we know when elodilles_pto will be back? I mean if we need to extend deadline it should be ok?
18:42:39 <slaweq> I can ask tomorrow morning @lajoskatona, he should probably know as they are from the same company
18:43:38 <bauzas> probably next week
18:44:03 <bauzas> because we skipped his section on the nova meeting and I was told it should be back next week
18:44:15 <frickler> IMO there was enough time to prepare for the deadline, we were already gracious with giving more then 4 weeks
18:45:05 <slaweq> frickler +1
18:46:11 <gouthamr> the release team can choose to merge this, or, if there's no response we can recommend that action in the next week's meeting
18:46:22 <gouthamr> how does that sound?
18:46:39 <gmann> ++
18:47:04 <frickler> most of the release team isn't around this week either, with ttx travelling, so likely nothing will happen earlier anyway
18:47:11 <gouthamr> ack
18:47:21 <gouthamr> ty, lets move on
18:47:22 <gouthamr> #topic Open Discussion
18:47:53 <gouthamr> plenty of time today for this..
18:51:38 <gouthamr> so, PTG is scheduled!
18:51:54 <gouthamr> i will need a volunteer amongst gmann, bauzas, frickler or cardoe to request a spot..
18:52:24 <bauzas> I already requested for nova
18:52:39 <bauzas> but in theory I won't lead the PTG since I leave my PTL seat
18:53:01 <gouthamr> ah same, i'd fill out the survey, and add one of you as the moderator.. you don't have to do it.. i just won't add myself because of the TC term
18:53:26 <bauzas> so I could help but for the first time since 3.5 years, I'd like to enjoy for once a PTG without leading anything
18:53:45 <gouthamr> we'd likely find a volunteer among the new TC and adjust.. this survey just sets up the list of people getting PTG organizer emails
18:53:54 <gouthamr> bauzas++
18:54:22 <bauzas> any other volunteer ? I can sign, if needed
18:54:25 <cardoe> I can as well.
18:54:29 <bauzas> thanks
18:54:38 <gouthamr> perfect, thank you cardoe ..
18:56:34 <gouthamr> alright, since the discussion has slowed down, lets take 4 mins back :)
18:56:40 <gouthamr> thank you all for attending
18:56:55 <gouthamr> next week is our monthly video+irc meeting, i
18:57:01 <gouthamr> will share details with the summary
18:57:05 <gtema> awesome :) finally end of work
18:57:05 <gouthamr> see you then!
18:57:20 <slaweq> see you o/
18:57:24 <noonedeadpunk> o/
18:57:25 <gouthamr> gtema: i can hear the can popping!
18:57:28 <gouthamr> #endmeeting