Tuesday, 2025-06-03

opendevreviewGuillaume Boutry proposed openstack/openstack-manuals master: Drop EOL version from ubuntu guide  https://review.opendev.org/c/openstack/openstack-manuals/+/95163408:55
gouthamrtc-members: gentle reminder that we’ll be meeting in ~55 minutes on Zoom and this IRC channel: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee16:05
dansmithi can haz? https://review.opendev.org/c/openstack/governance/+/95156916:52
gouthamryes will workflow after https://review.opendev.org/c/openstack/project-config/+/951570 lands16:53
dansmithgouthamr: thanks!16:54
fungidansmith: gouthamr: i just got caught up and approved the project-config change now16:55
fungionce the deploy pipeline completes for it, should be able to recheck the governance change and get a +1 from zuul16:56
dansmithack thanks16:56
fungiso hopefully after the meeting16:56
fungibut also you can start using it right away even if the governance change hasn't merged yet16:57
dansmithcool16:59
gouthamr#startmeeting tc17:00
opendevmeetMeeting started Tue Jun  3 17:00:47 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
gouthamr#info Today's meeting is being held primarily via video call. Action items and meeting minutes will be documented in IRC but for a full replay of the meeting, please visit the OpenStack TC youtube channel, where the recording will be uploaded soon.17:01
spotz[m]o/17:01
gouthamr#link https://www.youtube.com/@openstack-tc17:01
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:01
gouthamrToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee17:01
gouthamr#topic Roll Call17:01
noonedeadpunko/17:01
gmaano/17:01
bauzaso/17:01
gtemao/17:01
bauzas(joining Zoom in a sec, once my laptop is fully rejuvenated)17:02
cardoeZoom is installing an update... sorry...17:02
spotz[m]I’m waiting on the wiki for link17:03
gouthamrcourtesy-ping: mnasiadka 17:03
mnasiadkaSorry - got a company wide meeting today - will not be very talkative17:04
mnasiadkao/17:04
gouthamr#topic Last Week's AIs17:05
gouthamrthe main one was around the DCO17:06
gouthamrat this point most folks here have opined on the proposal: 17:06
gouthamr#link https://review.opendev.org/c/openstack/governance/+/950463  ([resolution] Replace CLA with DCO for all contributions)17:06
gouthamrgmaan says that the translations sign off question raised on the patch can be treated separately17:07
gouthamrthere's no ICLA/CLA enforcement on Zanata17:08
bauzassorry folks, I have a headset issue17:08
bauzasI can just hear from you now17:08
gouthamrand ianychoi noted that he didn't enforce ICLA for translators17:09
gouthamrwe can't onboard any new contributors to Zanata17:12
gouthamrweblate could enforce a CLA/DCO 17:13
gouthamrbut right now, a translator can't signup on OpenStack weblate either17:13
gouthamrthings are in-flight to productize weblate as we know17:13
gouthamrwe have 4 interns from CMU Pittsburgh and Qatar working over the next ~12 weeks to port  scripts working with Zanata today to Weblate17:14
cardoeWondering if we can break up the DCO change into steps instead of the big pivot that it is right now.17:15
gouthamrso, we can't block the DCO enforcement for code/doc contributions on the issue of enforcing it for translators17:15
gouthamrclarkb says weblate will allow the enforcement that zanata lacked17:16
gouthamrzanata is abandoned upstream, and we may have security bugs - and there's an urgency to finish our migration off of it17:16
cardoe+1 to gmaan's suggestion17:16
gouthamrgmaan agrees that we should separate the concerns and the TC resolution is a blocker for the whole DCO effort17:16
gouthamrnoonedeadpunk is concerned that we'll be tacking on more tech-debt17:17
gouthamrclarkb says that we need a stop gap for translators that we can work out 17:18
gouthamrmaybe a translator can send a note to the openstack-discuss with the DCO sign off17:18
clarkbfwiw I'm not sure we need one, just suggesting that that might be an option17:18
gouthamr+117:19
gouthamr#agreed on the zoom call to separate the translation CLA concern into a separate resolution and proceed with merging the existing resolution17:21
gouthamrthat was the major AI we had17:22
gouthamrthe other one was around gate failures in out-of-tree ML2 plugins 17:22
gouthamrJayF: did you happen to report a bug against devstack or neutron for the issue you mentioned last week17:22
gouthamrwas anyone else tracking anything else?17:23
JayFgouthamr: it's not really a bug? Just a combination of devstack tech debt being cleaned up, which made us cleanup some tech debt too, but it wasn't really straightforward.17:23
gouthamrin terms of AIs17:23
gouthamrah ack JayF 17:23
JayFfrustrating and time consuming but kinda unavoidable unless devstack wants to gate against ironic17:23
gouthamri see17:23
JayFand I'm not sure I want that :)17:23
gouthamrack, sounds good .. good to see that ironic fixed the issue in the plugin17:24
gouthamrthere's a question on Zoom17:24
JayFJust please folks keep in mind that Ironic often has to reconfigure things in our plugin, so be kind to that use case17:24
gouthamrabout the tooling patches to add "signed-off-by" to automated bot changes17:24
gouthamrJayF++17:24
JayF(the UWSGI config pattern makes that extremely difficult)17:24
gouthamrfungi says there's no blocker, we can approve all the open tooling changes17:25
gouthamrttx is checking with legal if there are any implications if bots add this sign off17:25
gouthamrbauzas is seeking clarifications regarding Gerrit Web UI patch updates post the DCO enforcement dates17:26
gouthamrhe's concerned that the formatting of the sign off will not be properly enforced17:27
gouthamrfungi says that we'll have this pain temporarily17:28
gouthamrhe says we need to mention this in the contributor documentation for this17:28
gouthamr#action: gouthamr will update https://review.opendev.org/c/openstack/contributor-guide/+/950839 to address this concern17:29
gmaan++17:29
spotz[m]I think Sylvain is talking about the corner case I talked about last week17:30
gouthamralright, we might have some teething pains regarding this17:33
gouthamrthe sooner we do this the better, that's been the thought17:33
gouthamr#topic Pending governance proposals and review timelines17:34
gouthamr 17:34
gouthamr#link https://review.opendev.org/q/project:openstack/governance+status:open 17:34
cardoeAnother one that could get some eyes is https://review.opendev.org/c/openstack/project-team-guide/+/94848417:35
gouthamrany concerns with any open changes that we need to chat about right now17:35
gouthamrbauzas is requesting a summary of our course of action on the governance proposal17:36
gouthamrcardoe: thank you for pointing it out.. 17:37
gouthamrwe can workflow it after two core reviewers have approved17:37
gouthamr#topic Changing OpenInfra User Survey Questions17:37
gouthamr 17:37
gouthamrwe won't be changing any questions for the 2025 user survey17:38
gouthamrwe could be prepared in advance for the next one though17:38
gouthamrplease feel free to edit the topic on the tc tracker etherpad17:38
gouthamr#topic Improving Contributor experience, contd.17:38
gouthamr#link https://etherpad.opendev.org/p/tc-2025.2-tracker (the summary of the Contributor/Maintainer surveys for Epoxy)17:39
gouthamr#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3YCEOEVDZRG5UU3FMPEP4F6EZIXDAVGU/ (summary posted by ildikov on the ML)17:40
gouthamrthe survey responses indicated that maintainers have trouble getting review attention 17:41
gouthamr:( 17:41
gouthamrthat's  73% of their issue17:41
gouthamrthe same question was posed to contributors, and 68% of the time that "Trouble getting reviews" was the reason/challenge indicated17:43
gouthamrbauzas says the root of this is a communiciation problem17:44
spotz[m]Sounds like a good Forum session? It's a more advanced version of a talk I've submitted for summit17:44
gouthamrit's good for live feedback17:44
opendevreviewMerged openstack/project-team-guide master: Add notes on reviving projects/deliverables  https://review.opendev.org/c/openstack/project-team-guide/+/94848417:44
gouthamras PTL bauzas had talked to contributors/operators multiple times over the years to show them how the Nova team prioritizes reviews.. 17:46
gouthamrspotz[m] says operator hours at the PTG probably didn't gather enough critical audience or have clear outcomes of what to get out of them.. because we didn't plan early enough17:48
gouthamrops meetups in person (like the one alongside the Summit in Berlin, 2022) worked better17:48
gouthamrlets take advantage of the upcoming Paris summit to have an in-person ops meetup, and for project updates as well so maintainers can talk to contributors17:49
gouthamrnoonedeadpunk says that it is problematic to understand how each project team prioritizes things17:50
gouthamr(as a contributor to multiple projects)17:50
gouthamrhe thinks we should be reinforcing guidelines to project teams 17:51
gouthamrsome problems:17:53
gouthamr- heavy etherpad usage to track review priorities - these aren't easily findable unless they're linked prominently from docs/wiki17:53
gouthamr- review priority label isn't being used, even by project teams that have enabled them17:53
gouthamrbauzas is suggesting that we direct projects to update their CONTRIBUTING.rst file at the root of the projects17:54
gouthamrbauzas is saying maintainers are humans, with human flaws - contributors must be talking to PTLs and finding "sponsors" to review their code.. its hard, but the only way things can improve.. 17:59
gouthamrcardoe says its hard for seasoned contributors to find review help in nova - they attempted chatting with folks during nova meetings, IRC etc18:00
clarkbnote anyone should be able to unabandon their own changes. Not sure if they would immediately get reabandoned by tooling through18:00
clarkb*though18:00
clarkb(and opendev actually suggests against auto abandoning anything)18:01
gouthamrcardoe says that -1s would be more helpful to the contributor than long silence from maintainers.. 18:02
gouthamr~~~ time check ~~~~18:02
gouthamrbauzas says that we need to ensure we have cross project discussions prioritized at the Oct PTG to address issues like the one that cardoe brought up18:04
gouthamr(cardoe's example of a patch that got stuck was around a nova/neutron feature)18:04
cardoeclarkb: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/941355 is one of them. I believe Vasyl wasn't able.18:04
cardoegtema: there's 2 changes for the openstack-ansible which have +1's from folks and pass tests. I think we can merge those 2 and make a release?18:05
gouthamrwe wrapped up the video meeting18:05
fungitc-members: point i was saving for open-discussion relatd to the foundation joining lf...18:05
cardoeFor context, the spec change is this... https://review.opendev.org/c/openstack/nova-specs/+/47181518:05
gtemaack cardoe, I am past my working hours, try to look tomorrow at those18:05
gouthamrwe will continue this topic during the next week's meeting18:05
gouthamrnoonedeadpunk: will be running next week's meeting.. thank you noonedeadpunk! 18:06
cardoegtema: absolutely. I just returned from PTO so just working through my backlog and wanted to mention it.18:06
gouthamri'll follow up with the meeting summary/AIs as usual.. 18:06
cardoefungi: we can discuss it async?18:06
gouthamrthank you all for joining today, and for bringing all these insights to the discussion! 18:06
gouthamrsee you here next week!18:06
gouthamr#endmeeting18:06
opendevmeetMeeting ended Tue Jun  3 18:06:49 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-06-03-17.00.html18:06
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-03-17.00.txt18:06
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-03-17.00.log.html18:06
gouthamrfungi: oops18:07
fungilf prefers and has unlimited google meet, though zoom is available and the foundation can pay for that still if desired, but the room url would change to a new account in that case. keep in mind that opendev's meetpad is always available as a free alternative too of course18:07
gouthamrlets do meetpad, really18:07
cardoeI'm a +1 on meetpad18:08
fungimainly i wanted to point it out as early as possible so you have time to start a conversation around it, there's no urgency, just a heads-up18:08
fungii don't know any spcific timeline for closing out the old zoom accoubnt this meeting has been using18:09
clarkbcardoe: I'm digging for where we set that in configuration and we only seem to explicitly set it on stable branches (due to the exclusive group perms on those branches). I wonder if Gerrit changed a default at some point in time and we didn't notice18:10
cardoeI'll poke Vasyl to try again.18:11
clarkbcardoe: https://gerrit-review.googlesource.com/Documentation/access-control.html#category_abandon that says it should be doable as change uploader18:11
clarkbbut it could be the docs are stale and gerrit changes something. Definitely let us know what you find out18:11
cardoeThis is one of those things that its combining the efforts of people from 3 different companies across multiple repos for two different projects. So it's truly a collaborative effort. But it's very async and gotta figure out how to contact each other.18:13
cardoeI'm trying to get everyone to stop having it as down stream patches.18:13
fungicardoe: mmaybe the new #openstack-ops:opendev.org matrix channel would be appropriate for downstream ops patch upstreaming coordination efforts?18:15
cardoemaybe. just regular #openstack-ops on IRC?18:16
fungiwhen you have a matrix hammer, every conversation looks like a nail! ;)18:16
fungiif they're all on irc then sure, yep18:16
cardoeWell I am on IRC and not on matrix.18:17
clarkbas the operator of the code review tool I Think that projects should avoid abandoning things that people say they are working on. Ask them to mark them WIP until ready for review sure. but to say you can't use the collaboration system to sollaborate is silly18:17
clarkbbut thats really a question for neutron and the tc probably. I'm not going to ban hammer anyone for using gerrit wrong18:17
noonedeadpunkand on IRC this channel seems non-existing18:18
cardoeWell one of the things I advocated when running for the TC was to try and get operators to upstream stuff they're running in prod if/when it makes sense.18:18
* noonedeadpunk live by that principle against all odds18:19
spotz[m]It used to be there weird18:19
cardoeIt's just an exercise of seeing who is more stubborn. Me as the squeaky wheel or the project or upstream.18:20
cardoeer... s/upstream/downstream/18:20
clarkbnoonedeadpunk: if your client shows you channel modes you'll see the channel is +s. That was done to mimimize spam18:21
clarkbit was done almost immediately after moving to oftc so has been that way for some time18:21
clarkbhttps://oftc.net/ChannelModes/18:21
noonedeadpunkyeah, it shows "*** Channel modes: no messages from outside, topic protection"18:25
clarkbmine says (+nstc)18:25
fricklerthe channel is #openstack-operators18:26
clarkboh I'm looking at this channel. Sorry I misunderstood18:26
frickleron OFTC. (so maybe unlucky choice for the matrix channel name)18:26
clarkbno the names should be able to overlap just fine18:27
noonedeadpunkok, this one I have :)18:27
clarkbpretty sure the zuul irc channel was left up with people pointing stragglers in the right direction for a while18:27
fungi#openstack-ops:opendev.org is a matrix room, not an irc channel reachable from matrix through a bridge18:29
fungi#openstack-operators is a channel on the oftc irc network18:30
fungi(which would be reachable from matrix through the oftc bridge)18:31
noonedeadpunkwell, then pretty much cut out from joining it ;(18:34
noonedeadpunkor need to finally move to matrix...18:35
clarkbcan you expand on that more? Is that a personal preference thing are are their hard requirements that can't be met using matrix?18:35
clarkbthey were talking about using slack or discord and then discussing how long free tiers of each of those retain scrollback so we suggested maybe they try matrix first18:36
clarkband they agreed that was worth a short18:36
noonedeadpunkIt's too many ram-consuming apps... Already running Slack, Mattermost, Zulip, IRC and now need to add Element to the list18:36
clarkbI just run it in a web browser tab which isn't too bad18:36
clarkbthe desktop client is heavy I agree18:36
noonedeadpunkYou actually helped me to sort out visuals there, so it is at least usable now...18:37
noonedeadpunkI kinda tried to fix NeoChat, but it really does not want to pass auth for some reason...18:37
noonedeadpunkbrowser can be a way ofc...18:38
clarkbthe only feature the browser doesn't have that desktop does is searching history in encrypted rooms18:38
clarkbbut these public discussion rooms are not encrypted so shouldn't impact that specific use case18:38
noonedeadpunkwas just trying to reduce amount of things I need to keep track of, but the list keeps growing spomehow18:40
clarkbfyi https://openinfra.org/blog/openinfra-joins-linux-foundation was posted today20:40
gouthamrnice20:57
fungithe latest update on the zoom account is that the foundation staff ned to know something by june 1 if they'll be providing a new zoom room for the tc meetings21:03
gouthamrday before yesterday? :) 21:03
fungier, no, JULY 1, sorry!21:04
clarkbwhich is before the next video meeting right?21:04
fungii don't even know what month i'm in any more21:04
gouthamrtc-members: i propose to begin using meetpad.opendev.org for our next meeting on July 1st 2025; if this fails us, we'll try to work with the foundation to use Google Meet or whatever tool suggested.. so there may be a short term pain (i doubt it) where we figure things out21:05
gouthamrif there are any objections, let me know.. 21:05
* gouthamr is excited about setting a deterministic meeting URL :D 21:06
gouthamrfungi: our use of Zoom was pretty rudimentary; i had an host code, and i accidentally used "record to the cloud" thingy one time which clarkb and aprice helped me almost immediately with.. so there's nothing to retrieve/relinquish before the account goes away21:07
gouthamrgmaan: JayF: does that sound right to you? ^21:08
JayFyes21:08
JayFI did the record to cloud once too lol21:08
JayFrite of passage for new tc'ers21:08
JayF**Tc chairs21:08
gouthamrhaha21:08
gmaanyeah, as those are published on youtube, it is all fine.21:12
fungithe previously-announced hashtag change is implemented, now all gerrit users can use the hashtag feature similarly to the change topic feature21:23
gouthamr\o/ 21:25
gouthamrsuper useful to tie governance proposals and multi-repo topic based patches 21:25
gouthamrlike this: https://review.opendev.org/q/hashtag:%22dco-signed-off-by%22+OR+topic:%22dco-signed-off-by%2221:26
clarkbnow you can update all the changes and remove topic from your query21:27
fungiyes21:29
fungithat's the reason i had originally done the query like that, because there was one change i wasn't the author on that i couldn't add the hashtag to because it was for openstack/requirements21:29
fungifixed now!21:30
gouthamrthere's a limit to this, right?21:30
gouthamrto prevent abuse? :D 21:30
fungiyes, it's called we disable accounts if they abuse gerrit features or otherwise become a nuisance21:31
fungisame as for being able to set/change the topic21:31
gouthamrhaha, wfm21:31
fungianyway, https://review.opendev.org/q/hashtag:dco-signed-off-by includes elod's release change now (it was release not requirements)21:32
clarkbI think there is a notedb limit to total updates per chagne as well21:32
clarkbso you'd eventually hit that then the change would effectively self archive itself21:32
clarkbwe've yet to hit that on any chagne I am aware of21:32
spotz[m]gouthamr: I'm fine with meetpad, it's come a long way since we tried to use it for the first virtual PTG:)21:33
gouthamr++ ty spotz[m] 21:35
gouthamrclarkb: oh, good to know.. 21:36
fungii mean, there are similar limits on change comments too21:40

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