17:00:47 #startmeeting tc 17:00:47 Meeting 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:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:47 The meeting name has been set to 'tc' 17:01:18 #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:23 o/ 17:01:24 #link https://www.youtube.com/@openstack-tc 17:01:33 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:01:37 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 17:01:41 #topic Roll Call 17:01:43 o/ 17:01:45 o/ 17:01:50 o/ 17:01:51 o/ 17:02:06 (joining Zoom in a sec, once my laptop is fully rejuvenated) 17:02:16 Zoom is installing an update... sorry... 17:03:35 I’m waiting on the wiki for link 17:03:58 courtesy-ping: mnasiadka 17:04:41 Sorry - got a company wide meeting today - will not be very talkative 17:04:45 o/ 17:05:29 #topic Last Week's AIs 17:06:10 the main one was around the DCO 17:06:30 at this point most folks here have opined on the proposal: 17:06:43 #link https://review.opendev.org/c/openstack/governance/+/950463 ([resolution] Replace CLA with DCO for all contributions) 17:07:07 gmaan says that the translations sign off question raised on the patch can be treated separately 17:08:17 there's no ICLA/CLA enforcement on Zanata 17:08:25 sorry folks, I have a headset issue 17:08:35 I can just hear from you now 17:09:01 and ianychoi noted that he didn't enforce ICLA for translators 17:12:51 we can't onboard any new contributors to Zanata 17:13:08 weblate could enforce a CLA/DCO 17:13:26 but right now, a translator can't signup on OpenStack weblate either 17:13:38 things are in-flight to productize weblate as we know 17:14:22 we have 4 interns from CMU Pittsburgh and Qatar working over the next ~12 weeks to port scripts working with Zanata today to Weblate 17:15:08 Wondering if we can break up the DCO change into steps instead of the big pivot that it is right now. 17:15:19 so, we can't block the DCO enforcement for code/doc contributions on the issue of enforcing it for translators 17:16:01 clarkb says weblate will allow the enforcement that zanata lacked 17:16:29 zanata is abandoned upstream, and we may have security bugs - and there's an urgency to finish our migration off of it 17:16:57 +1 to gmaan's suggestion 17:16:58 gmaan agrees that we should separate the concerns and the TC resolution is a blocker for the whole DCO effort 17:17:47 noonedeadpunk is concerned that we'll be tacking on more tech-debt 17:18:03 clarkb says that we need a stop gap for translators that we can work out 17:18:43 maybe a translator can send a note to the openstack-discuss with the DCO sign off 17:18:50 fwiw I'm not sure we need one, just suggesting that that might be an option 17:19:02 +1 17:21:12 #agreed on the zoom call to separate the translation CLA concern into a separate resolution and proceed with merging the existing resolution 17:22:15 that was the major AI we had 17:22:30 the other one was around gate failures in out-of-tree ML2 plugins 17:22:48 JayF: did you happen to report a bug against devstack or neutron for the issue you mentioned last week 17:23:14 was anyone else tracking anything else? 17:23:18 gouthamr: 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:18 in terms of AIs 17:23:25 ah ack JayF 17:23:37 frustrating and time consuming but kinda unavoidable unless devstack wants to gate against ironic 17:23:42 i see 17:23:44 and I'm not sure I want that :) 17:24:06 ack, sounds good .. good to see that ironic fixed the issue in the plugin 17:24:13 there's a question on Zoom 17:24:23 Just please folks keep in mind that Ironic often has to reconfigure things in our plugin, so be kind to that use case 17:24:27 about the tooling patches to add "signed-off-by" to automated bot changes 17:24:34 JayF++ 17:24:35 (the UWSGI config pattern makes that extremely difficult) 17:25:01 fungi says there's no blocker, we can approve all the open tooling changes 17:25:29 ttx is checking with legal if there are any implications if bots add this sign off 17:26:39 bauzas is seeking clarifications regarding Gerrit Web UI patch updates post the DCO enforcement dates 17:27:59 he's concerned that the formatting of the sign off will not be properly enforced 17:28:15 fungi says that we'll have this pain temporarily 17:28:37 he says we need to mention this in the contributor documentation for this 17:29:23 #action: gouthamr will update https://review.opendev.org/c/openstack/contributor-guide/+/950839 to address this concern 17:29:35 ++ 17:30:33 I think Sylvain is talking about the corner case I talked about last week 17:33:44 alright, we might have some teething pains regarding this 17:33:58 the sooner we do this the better, that's been the thought 17:34:18 #topic Pending governance proposals and review timelines 17:34:18 17:34:39 #link https://review.opendev.org/q/project:openstack/governance+status:open 17:35:27 Another one that could get some eyes is https://review.opendev.org/c/openstack/project-team-guide/+/948484 17:35:28 any concerns with any open changes that we need to chat about right now 17:36:16 bauzas is requesting a summary of our course of action on the governance proposal 17:37:15 cardoe: thank you for pointing it out.. 17:37:24 we can workflow it after two core reviewers have approved 17:37:40 #topic Changing OpenInfra User Survey Questions 17:37:40 17:38:26 we won't be changing any questions for the 2025 user survey 17:38:34 we could be prepared in advance for the next one though 17:38:49 please feel free to edit the topic on the tc tracker etherpad 17:38:56 #topic Improving Contributor experience, contd. 17:39:43 #link https://etherpad.opendev.org/p/tc-2025.2-tracker (the summary of the Contributor/Maintainer surveys for Epoxy) 17:40:43 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3YCEOEVDZRG5UU3FMPEP4F6EZIXDAVGU/ (summary posted by ildikov on the ML) 17:41:32 the survey responses indicated that maintainers have trouble getting review attention 17:41:33 :( 17:41:44 that's 73% of their issue 17:43:30 the same question was posed to contributors, and 68% of the time that "Trouble getting reviews" was the reason/challenge indicated 17:44:09 bauzas says the root of this is a communiciation problem 17:44:36 Sounds like a good Forum session? It's a more advanced version of a talk I've submitted for summit 17:44:51 it's good for live feedback 17:44:57 Merged openstack/project-team-guide master: Add notes on reviving projects/deliverables https://review.opendev.org/c/openstack/project-team-guide/+/948484 17:46:05 as PTL bauzas had talked to contributors/operators multiple times over the years to show them how the Nova team prioritizes reviews.. 17:48:20 spotz[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 enough 17:48:50 ops meetups in person (like the one alongside the Summit in Berlin, 2022) worked better 17:49:34 lets 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 contributors 17:50:23 noonedeadpunk says that it is problematic to understand how each project team prioritizes things 17:50:35 (as a contributor to multiple projects) 17:51:19 he thinks we should be reinforcing guidelines to project teams 17:53:20 some problems: 17:53:20 - heavy etherpad usage to track review priorities - these aren't easily findable unless they're linked prominently from docs/wiki 17:53:20 - review priority label isn't being used, even by project teams that have enabled them 17:54:45 bauzas is suggesting that we direct projects to update their CONTRIBUTING.rst file at the root of the projects 17:59:31 bauzas 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.. 18:00:24 cardoe says its hard for seasoned contributors to find review help in nova - they attempted chatting with folks during nova meetings, IRC etc 18:00:43 note anyone should be able to unabandon their own changes. Not sure if they would immediately get reabandoned by tooling through 18:00:46 *though 18:01:01 (and opendev actually suggests against auto abandoning anything) 18:02:13 cardoe says that -1s would be more helpful to the contributor than long silence from maintainers.. 18:02:32 ~~~ time check ~~~~ 18:04:19 bauzas 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 up 18:04:41 (cardoe's example of a patch that got stuck was around a nova/neutron feature) 18:04:45 clarkb: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/941355 is one of them. I believe Vasyl wasn't able. 18:05:16 gtema: 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:42 we wrapped up the video meeting 18:05:45 tc-members: point i was saving for open-discussion relatd to the foundation joining lf... 18:05:50 For context, the spec change is this... https://review.opendev.org/c/openstack/nova-specs/+/471815 18:05:52 ack cardoe, I am past my working hours, try to look tomorrow at those 18:05:56 we will continue this topic during the next week's meeting 18:06:15 noonedeadpunk: will be running next week's meeting.. thank you noonedeadpunk! 18:06:19 gtema: absolutely. I just returned from PTO so just working through my backlog and wanted to mention it. 18:06:26 i'll follow up with the meeting summary/AIs as usual.. 18:06:30 fungi: we can discuss it async? 18:06:41 thank you all for joining today, and for bringing all these insights to the discussion! 18:06:46 see you here next week! 18:06:49 #endmeeting