Tuesday, 2024-04-02

fricklertc-members: would be good if in particular people with some RHEL or RDO affinity could check https://review.opendev.org/c/openstack/openstack-manuals/+/91333209:23
opendevreviewDr. Jens Harbott proposed openstack/openstack-manuals master: [www] Add project data to 2024.1  https://review.opendev.org/c/openstack/openstack-manuals/+/91460212:19
opendevreviewDr. Jens Harbott proposed openstack/openstack-manuals master: [www] Set 2024.1 as released  https://review.opendev.org/c/openstack/openstack-manuals/+/91460312:19
opendevreviewDr. Jens Harbott proposed openstack/openstack-manuals master: [www] Setup 2024.2 Dalmatian  https://review.opendev.org/c/openstack/openstack-manuals/+/91488212:32
fricklertc-members: ^^ after discussion within the release team this a reordered now so that we defer updating the release repo side until after the 2024.1 release has been made tomorrow12:35
fricklerelodilles: so what to do about that failure? adding the new series to tools/www-generator.py seems to fix the error, but the resulting 2024.2 pages still have a broken release link13:54
elodillesfrickler: isn't a similar patch sufficient? https://review.opendev.org/c/openstack/openstack-manuals/+/90349814:02
fricklerelodilles: no because we deferred creating the whole www/2024.2/ folder to 91488214:04
elodillesfrickler: i meant the case when we don't defer o:)14:17
elodillesand stick to use 'dalmatian' for now14:18
fricklerwe already used 'cararal' just "for now" and now we're stuck with it, I'd prefer if we could make sure that this doesn't repeat14:20
elodillesas I said, i'm not feeling comfortable with this, given the release day is tomorrow. but if you insist, then any fix that works is OK to me.14:34
fricklerelodilles: would you feel better if we would merge https://review.opendev.org/c/openstack/releases/+/914619 only after / on top of 914764 ?14:40
fricklerthat would put a bit of strain on the release timeline tomorrow but should be doable I think14:41
elodillesIF we merge https://review.opendev.org/c/openstack/releases/+/914619 that should be definitely AFTER the release. but i still vote for not merging that at all. we finally fixed all 'series name' -> 'release id' related bugs, i don't think we should start this again14:49
elodillesmaybe it's just me and ttx & hberaud have different opinions ^^^14:50
ttxyeah I would rather wait for that one until end of week14:51
fricklerwell IMO it is a bug to have https://releases.openstack.org/dalmatian/index.html and all individual pages as https://docs.openstack.org/releasenotes/project/2024.2.html14:53
gmannI agree that this inconsistency between releasenotes page ^^ should be fixed. We talked about fixing it in last cycle also but we did not14:58
hberaudif chances exists to broke our tooling/process, as we are really close from the final deadline, I'd also suggest to wait After the release as Elod suggested15:01
gmannBoard meeting is started, in case anyone would like to join https://board.openinfra.dev/meetings/2024-04-0215:01
opendevreviewMerged openstack/governance master: [resolution] Adjudication of 2024.2 TC Election  https://review.opendev.org/c/openstack/governance/+/91402416:37
gmanntc-members: quick reminder that today meeting is video call, @18.00 UTC (after 1 hr from now)17:00
spotz[m]thanks for the reminder about video!17:11
rosmaitagmann: should I update https://review.opendev.org/c/openstack/governance/+/913912 to reflect https://review.opendev.org/c/openstack/governance/+/914024 (which has merged)?17:23
gmannrosmaita: yes, please. I think it is all good to update that.17:34
rosmaitaack17:34
opendevreviewBrian Rosmaita proposed openstack/governance master: Add TC results from the 2024.2/Dalmatian election  https://review.opendev.org/c/openstack/governance/+/91391217:35
gmanntc-members meeting time, 18:00
gmann#startmeeting tc18:00
opendevmeetMeeting started Tue Apr  2 18:00:45 2024 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
opendevmeetThe meeting name has been set to 'tc'18:00
gouthamro/18:00
dansmitho/18:00
gmannthis is link to join https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz0918:00
gmannwaiting for couple of min to have all to join18:01
gmannI will be chairing the meeting todyay18:01
rosmaitao/18:01
gmann#topic Roll Call18:01
gmanno/18:01
gmannToday agenda #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee18:04
gmann#topic Follow up on tracked action items18:05
gmannRosmaita to merge https://review.opendev.org/c/openstack/governance/+/914024 if eligible and ensure new TC is seated18:05
rosmaitait has merged!18:05
rosmaita#link https://review.opendev.org/c/openstack/governance/+/91391218:05
gmannGmann to chair this meeting18:06
gmann#topic Gate health check18:07
gmannall looks good and tomorrow is release and it seems no blocker form gate perspective18:10
gmann#action gmann to add grenade skip lelvel job simplification topic in QA PTG18:11
gmann#topic Implementation of Unmaintained branch statuses18:11
gmannnothing from TC actionable on this topic so we agree to remove it from agenda18:12
gmann#topic TC vPTG 2024.218:12
gmann#link https://etherpad.opendev.org/p/apr2024-ptg-os-tc18:12
gmann#link https://etherpad.opendev.org/p/2024.2-leaderless18:14
gmann#topic TC Chair Election18:15
gmannIncoming TC needs to select a new chair and vice chair: https://governance.openstack.org/tc/reference/charter.html#tc-chair18:15
gmannprocess #link https://governance.openstack.org/tc/reference/tc-chair-elections.html18:16
gmannThanks Gautham to show interest for vice chair. 18:19
gmann#topic Open Discussion and Reviews18:19
gmann#link https://review.opendev.org/q/project:openstack/governance+status:open18:19
gouthamr#agreed next week's IRC meeting is canceled in lieu of the PTG 18:24
gouthamr#action gmann will send an email to the openstack-discuss list to cancel next week's TC IRC meeting18:24
gmannthanks for notes18:24
gouthamrcurrently discussing, we're checking if we'll continue to use zoom for future TC video meetings18:25
gouthamrthe PTG discussions are not on zoom-by-default as they were in the past.. 18:26
gouthamrbut fungi mentions that the reason for that is the difficulty in coordinating a bunch of new accounts needed for a PTG and cleaning them up after a PTG... it isn't worth the effort18:26
gouthamr> the ptg organizers can help supply zoom rooms if needed, reach out to them18:26
gouthamrno plan to stop using zoom for future TC meetings; no technical limitations identified either.. these meetings are recorded and recordings are posted on youtube 18:27
gmann++18:27
gmannthis conclude our meeting for today, thanks everyone for joining.18:27
gmann#endmeeting18:27
opendevmeetMeeting ended Tue Apr  2 18:27:57 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:27
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-02-18.00.html18:27
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-02-18.00.txt18:27
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-02-18.00.log.html18:27
fungiyes, adding 20 zoom rooms for different tracks, most of which sat unused for the entire week except during especially busy timeslots, required a lot of setup and testing (human cost from foundation staff), but also the minimum billing periods for those make it quite expensive (financial cost)18:28
fungithe foundation has, for quite some time, been trying to tighten its belt wherever it can, as long as that doesn't result in a significant reduction in benefit to the projects it represents18:29
diablo_rojo_phoneAnd also, we should be using opensours tools anyway. 18:30
diablo_rojo_phone*opensource18:30
fungiyou make opensours with opensour mix18:30
gouthamrtotally; i didn't realize that was what it took... i think the biggest driver was being open worldwide without restrictions and the ability to record meetings for posterity ... i for one wasn't using any other "advanced" features in zoom18:30
fungiand a splash of seltzer18:30
diablo_rojo_phoneSounds like a cocktail at a summit party. 18:30
* gouthamr our drinks are also open source 18:31
gmannrosmaita: this is ready, can you please double check and +W this https://review.opendev.org/c/openstack/governance/+/91391218:31
rosmaitaack18:31
diablo_rojo_phonegouthamr: meetpad has been configured to be able to do recordings now :) 18:31
gouthamrdiablo_rojo_phone: yes! can't wait to try it properly.. i think we had a user error a few weeks ago that killed the recording for a good design discussion... from what i understand meetpad recordings are saved locally, and once the meeting ends, it presents a prompt regarding the recording that must not be ignored or fat-fingered around18:33
fungifwiw it wasn't a configuration option we turned on, so much as a default feature in a version we upgraded to18:33
fungithere are some gotchas with the recording feature (you should stop recording during breaks, and start it again when you resume so that you don't exceed the maximum file size, you still need to upload the recording somewhere once you have it, etc) but it has been tested a few times already18:34
fungialso very, very few projects have ever requested recordings of their sessions in the past so it seemed like a questionable option to optimize for18:35
gouthamrfungi: i wish it becomes more popular.. one or two people (usually the people running the discussion) have to take the pain to do the post processing and uploading, but, its been very helpful 18:36
clarkbI'm an anti recording person myself.18:38
clarkbits one of the situation where theoretically you get valeu out of it but then no one ever does and better note taking is usually more valuable and on top of that its just more corpus for the impersonator bots18:39
opendevreviewDmitriy Rabotyagov proposed openstack/governance master: Transition Freezer project to DPL  https://review.opendev.org/c/openstack/governance/+/91491118:44
opendevreviewMerged openstack/governance master: Add TC results from the 2024.2/Dalmatian election  https://review.opendev.org/c/openstack/governance/+/91391218:45
gmannWith ^^ merge, we have new TC seated for their next term18:46
rosmaita\o/18:47
gmannthanks rosmaita knikolla jamespage for serving as TC and your contribution 18:47
knikolla\o/18:47
gmannand welcome gouthamr gtema as new member and spotz[m] noonedeadpunk slaweq rejoining in TC 18:48
noonedeadpunko/18:48
gouthamr\o/18:49
noonedeadpunksry, missed a meeting today - got pretty much distracted and then it ended :D18:49
gmanngouthamr: gtema: As this is your first term in TC and Jay is on PTO, I sent the TC onboarding email to you both but if you have question feel free to ping any TC members here 18:49
gouthamrthank you gmann and also thank you rosmaita knikolla jamespage for your service18:49
gouthamrgmann++18:49
gmannnoonedeadpunk: oh,it was short one today, we finished in 30 min or so18:49
slaweqthx gmann and welcome gouthamr and gtema :)18:51
gmannAlso, special thanks to bauzas for making room to maintain the affiliation diversity in TC. Really appreciate his volunteer to step down. Looking forward to have him joining TC in future.18:52
gouthamr^ +100018:54
gmannI will leave Jay or election official to announce the new TC members to ML.18:54
noonedeadpunk+++19:02
gmannToday meeting recording has been published @https://www.youtube.com/watch?v=CLZOybmvio419:50
opendevreviewIan Y. Choi proposed openstack/election master: Add 2024.2 Election TC resolution patch link  https://review.opendev.org/c/openstack/election/+/91492520:47
opendevreviewIan Y. Choi proposed openstack/election master: Add 2024.2 Election TC resolution patch link  https://review.opendev.org/c/openstack/election/+/91492520:52
opendevreviewIan Y. Choi proposed openstack/election master: Add 2024.2 Election TC resolution link  https://review.opendev.org/c/openstack/election/+/91492520:53

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