17:00:18 #startmeeting tc 17:00:18 Meeting started Tue Apr 15 17:00:18 2025 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:18 The meeting name has been set to 'tc' 17:00:29 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 17:00:33 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 17:00:36 #topic Roll Call 17:00:45 o/ 17:01:02 \o 17:01:10 o/ 17:01:23 o/ 17:03:41 courtesy-ping: gmann, spotz[m], mnasiadka, bauzas 17:04:15 ah crap 17:04:29 noted absence: g m a n n 17:04:37 iirc mnasiadka is down under 17:04:54 ah, ack 17:05:10 alright, lets get started 17:05:20 #topic Last Week's AIs 17:05:45 ^ this would be a loaded topic, i am yet to unpack all of the TC PTG notes and enumerate AIs 17:06:14 but, lets look at AIs from the week prior 17:06:23 1) Skyline Engagement 17:07:22 we took an AI to reach out to skyline contributors about reproducibility concerns and encourage PTG participation 17:08:07 i received an email from the PTL wu_wenxiang that the PTG timings weren't feasible for the team 17:08:19 they'd prefer a conversation between 1:00 UTC to 10:00 UTC 17:08:20 We didn't get a chance to talk about binary artifacts during the PTG 17:09:04 I tossed on there talking about containers generally as well. 17:10:05 yes, the other request on the email was that we could share discussion topics/questions before the meeting because of fluency/communication concerns 17:10:22 well. for EU based ppl 8UTC-10UTC could be doable to sync with them 17:10:25 we did talk about the topic some in the security sig sessions 17:10:43 (binary artifact challenges i mean) 17:11:11 but indeed, async might be better to minimize language confusion 17:11:27 yeah, they'd be more effective with async communication 17:12:02 so lets defer to email 17:12:17 is there a reason to keep it off the ML, then? 17:12:18 UTC 8:00 to 10:00 is 3am to 5am for me. 17:12:43 i also see that they're using different emails to respond to my original email 17:12:44 (the reason I said about EU) 17:13:08 i don't know if there's some firewalling of sorts, on either end: "I guess that the emails sent from my mailbox might be blocked" 17:13:22 as 8UTC is 10 am for me 17:13:59 ack, i'll try to keep the conversation on the list, but noting that, if we don't get responses, it might be because of something weird like this 17:14:12 fungi: i'll poke you later to check on some list subscriptions 17:14:47 i.e., if you could check/share if individuals on the skyline team are subscribed to openstack-discuss 17:15:04 gouthamr: maybe mention that it is also possible to read/respond via the web interface 17:15:45 ah true, its clunky though, but will suggest it 17:16:02 can do 17:16:17 i've got some time right after this meeting 17:16:41 So I think without having to engage them at all we can have a discussion about binary artifacts. 17:16:43 happy to look up whatever you need 17:16:59 ack 17:17:02 thank you fungi 17:17:33 cardoe: as fungi said, we just mentioned it in the security-sig room.. our notes didn't capture it here, because the discussion wasn't too detailed 17:17:38 just a status of where we are 17:17:48 #link https://etherpad.opendev.org/p/apr2025-ptg-os-security-sig (OSSG PTG Etherpad) 17:18:21 i'll work on this AI further and share some more next week 17:18:27 I saw that more as VMT discussion. 17:18:42 Not on reproducibility which is what the issue with skyline was. 17:18:53 Which is certainly related 17:18:56 we touched on the security risks and need for things like sboms with containers and packages 17:19:06 not necessarily vmt, just security more generally 17:19:43 from a vmt perspective, we just flat refuse to cover container/package-specific vulnerabilities, and focus on vulnerabilities in our source distribution only 17:20:39 Anyway, I think the topic is similar to security-sig but not 100% aligned. 17:20:42 We can move on. 17:20:53 though cases where projects are committing third-party dependencies into their repositories crosses the line into source distribution vulnerabilities 17:21:24 next couple of AIs are related to goal updates for the FIPS and privsep migration goals 17:21:47 we heard more about this during PTG week. there's some homework left to do here, i'll track these 17:22:15 and we had two other AIs, tacked to folks not present here.. 17:22:51 we've work to do wrt upgrade jobs across projects 17:23:21 and bauzas meant to reconnect with seongsoocho and ianychoi for updates on translation tool migration and SIG activities 17:23:52 the i18n SIG met last week at the PTG: 17:24:00 #link https://etherpad.opendev.org/p/apr2025-ptg-i18n (i18n PTG Etherpad) 17:24:54 there are some status updates there ^ 17:25:13 a couple of actionable items, but, we probably could use context 17:26:19 does anyone, perhaps fungi noonedeadpunk have anything urgent to bring up here? or should we chat about this next week when we've had some time to digest the AIs 17:27:03 i do not 17:27:10 nothing urgent 17:27:22 stuff we need to cover, but doesn't have to be today 17:27:32 (wrt i18n/weblate) 17:27:46 okay, i'll add a topic to our next meeting regarding this 17:29:41 #topic OpenStack User Survey follow up 17:29:49 so the user survey for 2025 is live 17:30:53 #link https://www.openstack.org/user-survey/survey-2025 (2025 OpenStack User Survey) 17:31:07 but allison tells me we can seek edits to the questions 17:31:18 \o/ 17:31:42 there were 7 questions the TC had posed in the past 17:33:34 i can put those up in an etherpad: https://etherpad.opendev.org/p/tc-2025.2-tracker 17:35:28 lets try to probably critique these questions, and see if something is irrelevant and can be removed 17:35:43 its also an opportunity to add questions 17:36:02 so if you can think of something worth asking, please feel free to add it to the etherpad 17:37:05 my next question to aprice would be to get results of the 2024 User Survey 17:37:19 so we can work on a report like these: 17:37:23 #link https://governance.openstack.org/tc/#summary-of-user-survey-questions-responses 17:38:15 any opinions/concerns to share regarding this? 17:38:47 sounds like a good plan to me 17:38:54 yeah this all seems good 17:39:30 ty, lets move on.. 17:39:41 the next topic will be a sticky one here for a while 17:39:51 #topic PTG Follow up 17:39:51 #link https://etherpad.opendev.org/p/apr2025-ptg-os-tc 17:40:30 as i shared on the ML, the summary is a WIP, but, please do add your thoughts to the minutes you see on the pad 17:41:31 #link https://www.youtube.com/playlist?list=PLhwOhbQKWT7XYzqrx21j1uizxNxnbDf5Q (TC PTG Recordings) 17:42:31 it was a lot to unpack, but i really enjoyed the brainstorm we had over these 4 sessions, and will likely refer back to these minutes and recordings for a while 17:43:39 one thing that got sufficient airtime is this resolution that'll need next steps 17:43:46 #link https://review.opendev.org/c/openstack/governance/+/944817 ([resolution] Extend scope of VMT to cover all project teams) 17:44:41 we do need some more roll call votes here, please take a look and add your +1 or -1 and any comments 17:46:02 that's all i had for $topic today 17:46:21 does anyone have anything else to share? 17:46:32 how was the PTG? did you need a stiff drink at the end of each day? 17:46:57 just lots of jumping between sessions felt like I was rude cause I had to leave 17:47:55 ah, that's well understood i think, unless you were saying something and dropped off mid-sentence 17:47:57 :D 17:48:13 but i heard your concerns regarding the scheduling 17:48:18 i think the virutal ptg are worse for that. its feels like you shodul attend as much as you can but as a result you end up back to back ot back between rooms 17:48:46 at least the in person event you got 5-10 mins while you walks between rooms to recharge 17:48:56 true 17:49:07 #link https://etherpad.opendev.org/p/apr2025_ptg_feedback (PTG Feedback) 17:50:20 think mandatory breaks, pre-published agendas, cross project space all are good asks, we can try to be a bit better with the next round with some changes 17:51:26 some porject definlty did build in some room. if you were in multiple tracks they didnt alwasy align but i dont think it was specificly any worse this time then the past few 17:52:22 but ya planing ot use 50 mins out of the 1 hour blocks and taking that break i think helps 17:52:36 ++ 17:53:43 * gouthamr copies this feedback into the etherpad 17:54:03 alright, we're left with 7 minutes, and two more topics 17:54:06 lets check on these 17:54:10 #topic Gate Health 17:54:13 i liked seeing some "happy hour" blocks in agendas 17:54:21 fungi++ 17:55:12 we should do more of that, and try the unconference style meetups that ironic folks were telling us about 17:56:24 did grenade get updated to do the new upgrade paths? I should just go look 17:56:42 have there been any failures? 17:57:08 iirc gmann did the right things 17:57:27 #link https://review.opendev.org/q/topic:%22qa-2025-1-release%22 17:57:38 #link https://review.opendev.org/c/openstack/grenade/+/945244 17:57:46 #link https://review.opendev.org/c/openstack/grenade/+/945245 17:58:48 note to carloss: gmann suggested a manila non-voting grenade job against this repo ^ 17:59:20 clarkb: hope those links answer the question 17:59:44 yup looks good 17:59:46 we've one minute left 17:59:51 (or not) 18:00:00 gouthamr: ack, ty :) 18:00:08 just a quick link to the TC tracker for 2025.2 18:00:10 #link https://etherpad.opendev.org/p/tc-2025.1-tracker (Technical Committee activity tracker - 2025.1) 18:00:28 please add anything you'd like to track through these meetings here ^ 18:00:43 with that, we don't have time for Open Discussion today 18:00:54 but does anyone want to say something to record in the minutes? 18:01:39 thank you all for participating today, this meeting will return next week! 18:01:39 #endmeeting