Tuesday, 2025-09-30

tonybjust confirming that I won't be at the TC meeting in 8(ish) hours.09:03
*** bauzas0 is now known as bauzas10:43
gouthamrack tonyb ; we’ll discuss the alternate slot keeping in mind your earlier comments re timeslots13:23
bauzasgouthamr: I saw that teams started to reserve some rooms for the PTG, do we have any consensus about asking our service teams to be having some days for cross-project discussions ? (eg. monday/tuesday)13:52
fungias a cross-project topic, i'm going to add a maintainer/contributor experience office hour on thursday @14z14:02
*** vhari_ is now known as vhari14:13
gouthamrfungi: would you consider doing that mon-tue? or during the TC slot on friday?14:37
gouthamrbauzas: yes, we do.. moderators must have received instructions from diablo_rojo_phone that Mon-Tue should be for cross project discussions14:37
gouthamrmaybe the nova, cloudkitty, manila, telemetry slots on Monday are cross-project slots - i don't know how we can differentiate14:39
fungigouthamr: i think we'd want to discuss things about it with the tc collectively too, but probably can't take an hour of your time for that14:39
fungiwe were thinking later in the week would be better in order to collect more info on what related topics got discussed by various teams during the ptg, but were wavering on whether early or late in the week worked best (each has its own benefits and down-sides)14:40
gouthamryeah that's hard .. 14:44
fungii'll check with clarkb and ildikov on moving it to the start of the week instead14:46
clarkbI tend to try and keep my PTG week flexible so I'm sure I'm the person with the fewest conflicts14:47
clarkbso I would schedule what works for everyone else then I'll do my best to be there14:48
*** gibi_ is now known as gibi16:07
gouthamrtc-members: a gentle reminder that the weekly IRC meeting will happen here in ~35 minutes: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee16:24
bauzasgouthamr: unfortunately again, not being able to be on the meeting16:30
gouthamr#startmeeting tc17:00
opendevmeetMeeting started Tue Sep 30 17:00:11 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
opendevmeetThe meeting name has been set to 'tc'17:00
gouthamrWelcome 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
gouthamrToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee17:00
gouthamr#topic Roll Call17:00
frickler\m/17:01
gouthamrcourtesy-ping: noonedeadpunk, spotz[m], gtema, cardoe, mnasiadka17:02
mnasiadkao/17:02
cardoeo/17:02
* gouthamr waits17:04
gouthamralright, lets get started.. 17:05
gouthamr#topic Last Week's AIs17:05
gouthamrwe took an AI to check on the "leaderless" teams:17:06
gouthamrOpenStack Charms: this has a PTL nominee since our meetin g last week: https://review.opendev.org/c/openstack/governance/+/962121 17:06
gouthamr^ please do check the comments for questions concerning the project, and its leadership that we had asked in past meetings17:06
gouthamrit has the requisite votes to merge tomorrow.. in case you'd like to add yours, please do17:07
gouthamrfor the rest, lets look at:17:08
gouthamr#link https://etherpad.opendev.org/p/2026.1-leaderless 17:08
noonedeadpunkoops sorry17:08
noonedeadpunko/17:08
gouthamrthe Venus project looks quite "abandoned" to me... i think its worth retiring the deliverables and the project team17:08
gouthamr"There are 0 merged patches generated within 180 days"17:09
noonedeadpunksad it didn't fly. as idea was really nice of free and powerful central log solution17:09
fricklerdon't we need to go via marking inactive first? like to give contributors a chance to show up?17:09
noonedeadpunkespecially if it would collaborate with vitrage for rca :D17:10
gouthamrprojects can directly be retired, there's no need to go through "inactive" phase: https://governance.openstack.org/tc/reference/dropping-projects.html#process17:11
gouthamrbut, i don't see any harm in going that route.. 17:11
noonedeadpunkthey can, but I think question was regarding of opprotunity to pick up the ball17:11
gouthamrcaveat: we still have the issue of visibility of an "inactive" project17:12
gouthamrto end users and operators17:12
gouthamrassuming we can worry about that as a separate issue.. are there any proponents of direct retirment here?17:13
gouthamrif not: 17:14
gouthamr#action: mark venus as "inactive" and alert the openstack-discuss ML 17:14
gouthamrokay, lets chat about vitrage.. 17:14
gouthamrwe haven't had any volunteers show up here, despite the ML bump 17:15
gouthamrand there may be issues for maintainers to resolve in the meantime that could force our hand in case we're unable to get attention17:15
gouthamris it worth putting through the same bucket, i.e., marking "inactive"?17:16
cardoemakes sense to me17:17
* gouthamr thinks out aloud - an "inactive" project that remains in that state beyond the Gazpacho release will be retired in the "H" release17:17
fungiremember that inactive projects become super fun to deal with when the vmt receives vulnerability reports for them17:18
fricklerG is 2026.1? why can't we give up on those confusing names?17:18
fungiwe'll be escalating those to the tc members, typically17:18
noonedeadpunkEh, well. I may step up at the end of the day for Vitrage17:19
noonedeadpunkWith summit arriving I just having less and less cycles available for anything though17:19
clarkbfrickler: I have to look at the release schedule every time to make sense of them17:20
clarkbbut yes https://releases.openstack.org/ confirms G is 2026.117:20
noonedeadpunkand my criteria of stepping in I set if I will get actually time to look into failing tempest tests17:20
noonedeadpunk(and I have not have any time yet)17:20
gouthamrits possible to tag the project "inactive" and if things get better by M-2, it can be added to the release17:21
noonedeadpunkso seems like I've failed own criteria...17:21
noonedeadpunkSo Jan0517:21
noonedeadpunkyeah, ok, sounds reasonable17:21
gouthamryes: Jan 05 - Jan 09, the "R-12" week is Gazpacho-2 milestone17:22
noonedeadpunkso pretty much a revert for Inactive should be created and stepping in as PTL I guess?17:22
gouthamrtwo separate things, imo17:22
gouthamrinactive projects can have a PTL17:22
gouthamrmight need one really so they can form a team 17:23
noonedeadpunkbut we move it to inactive because of absent ptl :)17:23
gouthamrye17:23
noonedeadpunkso they're very related :) inactive can be with ptl, but not vice versa17:23
fungiit can be without ptl if the team has a full slate of active dpl liaisons17:24
noonedeadpunkoh, yes, sure17:24
noonedeadpunkright17:24
fungibut yes, a longstanding misconception is that dpl doesn't solve the problem of not having enough volunteers to lead the team, if anything it needs more volunteers17:25
gouthamr#action: mark vitrage as "inactive" and alert the openstack-discuss ML 17:26
gouthamrthe last project in this list is monasca17:26
gouthamrthe project stats for this have been confusing, but, we kinda knew that there was _some_ activity17:26
gouthamri.e., a couple of maintainers who now are okay with retirement17:27
gouthamrso i floated a patch to mark the project "inactive" through 2025.2, i need some more eyes here: https://review.opendev.org/c/openstack/governance/+/95939217:28
gouthamrwe will NOT retire the project in 2025.2, but we may do so in 2026.117:28
gouthamrso, this update is procedural 17:29
* gouthamr will refresh the retirement change since it's gone into merge conflict17:29
frickler"may do so"? what's blocking us from proceeding with the retirement right away?17:30
gouthamrmy time17:30
fricklerso just ask for a volunteer to create the necessary cleanup patches and we are fine?17:31
gouthamrnot a joke, i followed up with the requester, but didn't hear back - i'm unsure if they've gerrit emails filtered.. so i wanted to send them a note elsewhere17:31
gouthamrbut, i don't understand what problem we have with https://review.opendev.org/c/openstack/governance/+/95939217:32
gouthamri mean, it's the reality, correct? we're making no promises regarding 2026.1 on that change17:33
fricklerit doesn't help anyone, that's my problem17:33
gouthamrsorry, i'm going to point out that it was a process that the TC adopted.. we can change the process if you'd like to stop doing it17:33
gouthamrin all likeliness, we'll come around and undo the change in a few weeks, as part of the retirement17:34
gouthamri want to separate the concerns and make incremental progress 17:35
fricklerwell, just go ahead, then? no need to discuss this endlessly, let's move on17:36
gouthamrwell, i need votes on a "formal-vote" patch like this one17:37
gouthamrnoonedeadpunk: cardoe could you please review https://review.opendev.org/c/openstack/governance/+/959392.. it's okay to -1, it'll get dropped if there are enough -1s17:38
cardoeI already +1'd it17:38
gouthamrah, didn't refresh17:38
gouthamrokay, lets move on to other AIs17:38
cardoeI'm okay extending.17:38
gouthamrre: Default MySQL/MariaDB charset/collations changes, noonedeadpunk any updates on this?17:38
gouthamrprobably not.. 17:39
noonedeadpunkI think I need to propose community goal for that17:40
noonedeadpunkbut it has not been done yet17:40
gouthamr+1, no rush, just had that in my notes.. 17:40
gouthamrthe last AI that i had was around TC roles17:40
gouthamri nominated myself as chair17:40
gouthamrand there were no other nominations.. so i'll proceed with the next step17:40
noonedeadpunkthanks for stepping in!17:41
gouthamri do need a vice-chair nominee, if you're interested, please let me know17:41
gouthamr(this extends to the others not here currently) 17:41
gouthamri'll throw up a change for the chair, and it can be updated to add the vice-chair too17:41
gouthamrthe TC also had liaisons for (1) DPL projects and (2) OpenStack VMT17:42
gouthamrfreezer: https://opendev.org/openstack/governance/src/commit/1a2ac945da2fbcc1e0f391d2effeca362b63622f/reference/projects.yaml#L252-L25417:44
gouthamrOslo: https://opendev.org/openstack/governance/src/commit/1a2ac945da2fbcc1e0f391d2effeca362b63622f/reference/projects.yaml#L1969-L197117:44
gouthamrRelease Management: https://opendev.org/openstack/governance/src/commit/1a2ac945da2fbcc1e0f391d2effeca362b63622f/reference/projects.yaml#L2259-L226117:44
gouthamrRequirements: https://opendev.org/openstack/governance/src/commit/1a2ac945da2fbcc1e0f391d2effeca362b63622f/reference/projects.yaml#L2298-L229917:44
gouthamr#link http://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management17:45
gouthamr^ we need to refresh these, and i would like volunteers please 17:45
gouthamrif you're interested, you can nominate yourself right away - propose changes to the governance repo directly by replacing gmaan.. 17:45
gouthamrfor the VMT, i'll continue, and b a u z a s may as well.. 17:46
fungimuch appreciated!17:46
gouthamrhe'll confirm async17:46
gouthamrwe can chat about all of this lazily, async.. so everyone has an opportunity to respond.. i'll just take note to make all of these changes by next week17:47
gouthamrany questions, concerns?17:47
gouthamr#topic Skyline Health / Release / Patch Merging17:48
gouthamri think this was a very positive interaction17:48
noonedeadpunk++17:48
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/Z6TG6JLN2M25T3CIMZHATSVKUVAFJVDK/17:48
gouthamrvery glad that you took the lead on this, cardoe and the responses from wu-wenxiang were enlightening, and positive17:49
frickleryes, good progress has been made, which may now stall for a bit due to a major chinese holiday17:50
cardoeYeah which is okay.17:50
gouthamri personally think it'll be nice to get sowmya added to the core maintainers team, and have them coordinate any further inclusions17:50
cardoeI've told her that I'm happy to mentor her.17:51
fricklershowing some review activity would be a good next step IMO17:51
cardoeThat's what I was actually telling her yesterday.17:51
gouthamrperfect, maybe a slot at the PTG may be a good place to gather anyone else that's interested17:52
gouthamranyone can propose these, fungi and diablo_rojo_phone can help create a spot assuming there's room17:52
gouthamri'd join and ask noob questions17:54
frickleriiuc most current cores aren't comfortable with audio/video calls17:55
gouthamrthe maintainers may choose not to join, they prefer long form async communication as they've stated.. but, you may find other interested people willing to come speak17:55
gouthamrfrickler: yes17:55
gouthamrbut i'm sure they'll like the recorded feedback on an etherpad or an ML summary17:56
fricklersure17:56
gouthamrcardoe: this may need some of your handholding, if you think its a good idea17:57
gouthamranything else for $topic?17:57
cardoeYeah I'm trying to think.17:58
cardoeI don't know.17:58
cardoeI don't want to pressure the current folks with methods they aren't comfortable with or with timing that doesn't work.17:58
cardoeBut I certainly want to find a way to get more folks engaged.17:58
cardoeI know that in the past for me when I'd see projects where only changes were being merged for co-workers its cause folks were done with the project and just forced to engage from their job.17:59
cardoeSo that's where I thought it was heading.17:59
gouthamryeah, its now apparent that the project survives because of the goodwill of the people that started it.. we need to augment the team to help it sustain/thrive nevertheless. 18:00
gouthamrtime check18:01
gouthamrwe're over the hour18:01
gouthamr#topic A call for PTG Topics (gouthamr)18:01
gouthamr#link https://etherpad.opendev.org/p/oct2025-ptg-os-tc18:01
gouthamr^ this is just informational today, please do add any topics here for the PTG discussions. I reserved some room (Tuesday and Friday) tentatively, we can discuss async and add or remove slots 18:01
gouthamr#topic Open Discussion18:01
gouthamranything else to add to the minutes today?18:01
fricklerin combination with the discussion about the timing for the meeting, I'd also like to see confirmation whether there is still a majority that wants to do video meetings18:02
gouthamr^ yes18:02
gouthamrwe're coming up on one18:02
gouthamrand i think its worth asking18:03
spotz[m]I'm good either way. Before I forget I should be here next week but will be out the following 218:03
gouthamrlets run a poll! :) 18:03
gouthamri'll add some "alternate" time slots that were missing from the original poll18:03
fricklerand I'd like to have a meeting slot that fits EU+APAC once a month, so something in the 8-12 UTC range18:03
fricklerand I'll also be offline the whole next week and maybe beyond, just ftr18:04
gouthamrack18:04
mnasiadkafrickler: The EU+APAC slot would probably imply an APAC or EU vice-chair?18:04
gouthamri'll share this poll18:04
gouthamrmnasiadka: yes18:04
fricklermnasiadka: that would sure be very helpful, thanks for volunteering :D18:05
mnasiadkaI didn’t say I’m volunteering - but if there’s no other volunteer - I can put my name forward…18:05
gouthamrmnasiadka: +1 ty18:05
gouthamri'll run a poll with these questions too, so people can add their opinions async18:05
gouthamrthanks everyone, lets wrap it up here18:06
gouthamr#endmeeting18:06
opendevmeetMeeting ended Tue Sep 30 18:06:04 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:06
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-30-17.00.html18:06
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-30-17.00.txt18:06
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-30-17.00.log.html18:06
mnasiadkagouthamr: where do I need to sign with my blood for vice chair? :-)18:17
gouthamr\m/ coming up one sec :D 18:21
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Add 2026.1 TC chair and vice-chair  https://review.opendev.org/c/openstack/governance/+/96261418:24
gouthamrmnasiadka: ^ :) 18:25
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Retire Monasca project  https://review.opendev.org/c/openstack/governance/+/95367118:43
opendevreviewMerged openstack/governance master: Appoint Felipe Reyes as PTL for OpenStack Charms  https://review.opendev.org/c/openstack/governance/+/96212118:43
opendevreviewMerged openstack/governance master: Extend Monasca's inactive state  https://review.opendev.org/c/openstack/governance/+/95939218:48
gouthamrbased on the cycle highlights, i think watcher, skyline and neutron folks could add to the OpenInfra Live episode this week.. 18:55
gouthamrcc: wu-wenxiang, haleyb, sean-k-mooney 18:55
gouthamrhttps://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/IU4PXKDSIUYGWDFHWHGKHMC24A7NKBSE/18:55
sean-k-mooneymaybe although im not sure i personaly want to. i can bring it up tomorwo internally18:57
sean-k-mooneywhen it the session18:57
gouthamrThursday, 1400 UTC18:57
gouthamrty, if someone can do it, they'll need to respond to the thread so aprice can share the calendar/deets18:58
sean-k-mooney i can ask folks if anyone want to give an overview of the accompliments for the cycle tomorwow18:58
gouthamr++18:58
opendevreviewGoutham Pacha Ravi proposed openstack/governance master: Retire Monasca project  https://review.opendev.org/c/openstack/governance/+/95367119:04
tonybLooking at the various repos we own there are a few (10) changes that are "old".  Is there any merit to keeping them open or can they be abandoned or set to WiP (although I doubt very much there will be any progress)23:29
tonybFor reference: 23:30
tonybhttps://review.opendev.org/q/is:open+-is:wip+before:2024-01-01+(project:openstack/api-site+OR+project:openstack/openstack-manuals+OR+project:openstack/project-team-guide+OR+project:openstack/service-types-authority+OR+project:openstack/constellations+OR+project:openstack/goal-tools+OR+project:openstack/ideas+OR+project:openstack/openstack+OR+project:openstack/governance+OR+project:openstack/governance-website+OR+project:openst23:30
tonyback/governance-sigs+OR+project:openstack/election)23:30
tonybhttps://review.opendev.org/q/is:open+-is:wip+before:2024-01-01+(project:openstack/api-site+OR+project:openstack/openstack-manuals+OR+project:openstack/project-team-guide+OR+project:openstack/service-types-authority+OR+project:openstack/constellations+OR+project:openstack/goal-tools+OR+project:openstack/ideas+OR+project:openstack/openstack)23:30
tonybthe second link doesn't get mangled23:31
tonybAlso in case anyone else find it helpful: http://tiny.cc/os-tc-dash23:36

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!