| opendevreview | Nuutti Hakala proposed openstack/ironic master: Add more JSON schema validation to API https://review.opendev.org/c/openstack/ironic/+/990440 | 10:33 |
|---|---|---|
| opendevreview | Esther Domfeh proposed openstack/ironic master: feat: populate node_history state fields https://review.opendev.org/c/openstack/ironic/+/994288 | 12:54 |
| TheJulia | good morning everyone | 13:08 |
| opendevreview | Will Szumski proposed openstack/tenks master: Add openstack.cloud collection to requirements https://review.opendev.org/c/openstack/tenks/+/993060 | 13:16 |
| opendevreview | Esther Domfeh proposed openstack/ironic master: feat: populate node_history state fields https://review.opendev.org/c/openstack/ironic/+/993208 | 13:38 |
| * TheJulia wonders if everyone went on vacation | 13:47 | |
| jssfr | everyone in europe is melting at least. | 13:47 |
| opendevreview | Will Szumski proposed openstack/tenks master: Add openstack.cloud collection to requirements https://review.opendev.org/c/openstack/tenks/+/993060 | 13:48 |
| opendevreview | Will Szumski proposed openstack/tenks master: DNM: testing collection install with Kayobe https://review.opendev.org/c/openstack/tenks/+/994295 | 13:48 |
| TheJulia | ... Heat wave? | 13:52 |
| Sandzwerg[m] | Yes 🫠| 13:56 |
| TheJulia | heh | 14:00 |
| rpittau | melting is an euphemism | 14:00 |
| jssfr | rpittau, already in the spontaneous combustion stage? | 14:01 |
| rpittau | almost there, yeah | 14:02 |
| * TheJulia wonders what is considered combustion stage | 14:04 | |
| opendevreview | Will Szumski proposed openstack/tenks master: Add openstack.cloud collection to requirements https://review.opendev.org/c/openstack/tenks/+/993060 | 14:07 |
| opendevreview | Will Szumski proposed openstack/tenks master: DNM: testing collection install with Kayobe https://review.opendev.org/c/openstack/tenks/+/994295 | 14:07 |
| iurygregory | o/ | 14:42 |
| * iurygregory forgot to open irc =X | 14:42 | |
| TheJulia | So who was going to run this week's meeting? | 14:57 |
| iurygregory | me =) | 14:57 |
| TheJulia | cool cool | 14:57 |
| TheJulia | I failed to record it last week due to launchpad being generally unhappy | 14:57 |
| iurygregory | no worries o/ | 14:57 |
| iurygregory | #startmeeting ironic | 15:00 |
| opendevmeet | Meeting started Mon Jun 22 15:00:01 2026 UTC and is due to finish in 60 minutes. The chair is iurygregory. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'ironic' | 15:00 |
| TheJulia | o/ | 15:00 |
| rpittau | o/ | 15:00 |
| TheJulia | Hmm, my clock is slow, how fun! | 15:00 |
| iurygregory | Hello everyone o/ welcome to the ironic weekly meeting! | 15:00 |
| Mahnoor | o/ | 15:01 |
| * fungi is around for his topic again | 15:01 | |
| kubajj | o/ | 15:01 |
| iurygregory | You can find the Agenda for this meeting in our wiki | 15:01 |
| iurygregory | #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting | 15:01 |
| iurygregory | #topic Announcements / Reminders | 15:02 |
| cid | o/ | 15:02 |
| iurygregory | #info Standing reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio | 15:02 |
| iurygregory | #link https://tinyurl.com/ironic-weekly-prio-dash | 15:02 |
| iurygregory | Does anyone have something to add to Announcements / Reminders ? | 15:02 |
| iurygregory | #topic Working Group Updates | 15:03 |
| iurygregory | The first one is Async IO, so it's on me | 15:04 |
| iurygregory | #info no updates, waiting for reviews/feedback in the spec | 15:04 |
| iurygregory | #link https://review.opendev.org/c/openstack/ironic-specs/+/972754 | 15:04 |
| iurygregory | any updates from the Security Coresec team? | 15:04 |
| TheJulia | I have no update at this time | 15:05 |
| JayF | Nothing public+notable since last week | 15:05 |
| iurygregory | thanks TheJulia and JayF | 15:05 |
| iurygregory | #topic Discussion topics | 15:05 |
| iurygregory | We have one topic from fungi | 15:06 |
| iurygregory | #info Bridging the Gap Gazpacho Cycle Survey and Metrics Analysis (fungi) | 15:06 |
| fungi | ildiko posted openstack-wide 2026.1 (gazpacho) cycle retrospective contributor/maintainer survey results and metrics to openstack-discuss recently: | 15:06 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3POML6PYPDWQNYM5IFB54O4ASXEPK4Z5/ Bridging the Gap Gazpacho Cycle Retrospective Survey Results | 15:06 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/CVLQIFEVNNJJ7BJSFZJ4RNZZA7ELQKDS/ Bridging the Gap Gazpacho Cycle Retrospective Metrics Analysis | 15:06 |
| fungi | i and the other community managers on the openinfra foundation staff have also been digging into team-specific details and i'm doing a round of outreach similar to past cycles, to go over how things may have changed | 15:06 |
| fungi | ironic had more survey responses than most teams in openstack (4 contributors and 1 maintainer), so this is great though additional participants for the next round would, as always, help us draw even more accurate conclusions | 15:06 |
| fungi | half the contributors indicated spending 2 or more years in the project with the other half only involved for a cycle or two, but all respondents had experience contributing to at least 2 other open source projects as well | 15:07 |
| fungi | average ratings on the contributor survey questions were encouragingly positive overall, with actionable reviewer feedback averaging highest at 5 out of 5 while usefulness of test results ranked lowest at 3.75 average out of 5 | 15:07 |
| fungi | the most common contribution challenge selected was getting reviewer attention, followed by struggles with unstable testing and shifting reviewer consensus or expectations over the lifetime of a change | 15:07 |
| fungi | the new survey questions about ai tools indicate most respondents used ai assistance in their contributions (mostly claude code, some cursor), though they declined to indicate how it helped them | 15:07 |
| fungi | the rankings on the one maintainer survey response were slightly lower, ranging from 5 (usefulness of automated test failures and job logs) down to 3 (timeliness of reviews on their, comprehensiveness of contributor docs) | 15:07 |
| fungi | the one contributing challenge selected by the maintainer was trouble getting review attention from other maintainers, while their biggest reviewing challenge was incomplete changes from contributors (missing tests, docs, release notes) | 15:07 |
| fungi | this maintainer indicated using claude code both for reviewing changes and assisting with their own contributions, noting that its use overall results in more comprehensive but larger changes, and that it hasn't improved review bandwidth | 15:08 |
| fungi | for review priority tracking, contributors indicated following mostly irc/mailing lists, then gerrit change topics and hashtags along with blueprints and specs, which mostly matched the maintainer response (minus the blueprints) | 15:08 |
| fungi | however, a minority of contributors said they didn't know where or even if the team tracked priorities, so maybe there's still some room for making that more apparent (e.g. in initial review comments?) | 15:08 |
| fungi | as for metrics, active maintainer count held steady at the same level as flamingo (still down slightly from epoxy) while reviewer count fell by 8% (flamingo was anomalously high though, so now back to the same level as other recent cycles) | 15:08 |
| fungi | interestingly, even though change volume increased 29% the team not only managed to keep up but burned down some backlog, closing 7% more than were opened! | 15:08 |
| fungi | review response times improved too: time to review was halved overall in comparison to flamingo (so twice as fast at responding to contributors), almost back to pre-flamingo median speeds but better on average/mean | 15:09 |
| fungi | an important note about metrics this time: since flamingo we've switched from bitergia to lfx insights as our data source, and while the numbers between them are similar there are some slight differences in how activities are counted | 15:09 |
| fungi | because of this, we re-ran metrics analyses for previous cycles against the new system in order to make sure we weren't trending numbers from different backends and drawing misleading conclusions due to changing measurement methods | 15:09 |
| fungi | anyway, that was a quick dump, i know it's a lot to take in but i didn't want to eat up too much of your meeting, so i'll put this on the agenda again in a few weeks to give everyone time to digest and come up with questions or ideas | 15:09 |
| fungi | (i'd do it sooner but am travelling the next two mondays) | 15:09 |
| fungi | one thing we're interested in finding out is whether the team implemented any new contributor or reviewer practices over the course of the last cycle, for example techniques that were discussed in the previous round of analyses | 15:09 |
| fungi | though i'm happy to answer any immediate feedback now too if there's time | 15:09 |
| iurygregory | thanks for sharing this fungi ! | 15:09 |
| TheJulia | Are there any more lines so I can finish reading? | 15:10 |
| fungi | i didn't have more prepared, no | 15:10 |
| JayF | is it ... wrong of me to think of this as clearing the "good enough" bar? | 15:10 |
| JayF | I am uncertain that specific focus in this area, for Ironic, is a valuable use of time given our success already in this space? idk | 15:11 |
| fungi | depends on your definitions of "good" and "enough" but on balance yes i'd say ironic is quite healthy | 15:11 |
| TheJulia | JayF: I don't disagree, I think there is a whole perfection is the enemy of good aspect, even trying to frontload all context on to any new contirbutor we identify, then shifts all interaciton burden to teaching outright which is just going to tax the reviewers even more than the crispy charred state they are in | 15:11 |
| fungi | keep in mind that making the experience better *for maintainers* was half of the goal of this effort, so looking at it from the perspective of "are maintainers doing enough" is missing a lot of the point | 15:12 |
| iurygregory | regarding "a minority of contributors said they didn't know where or even if the team tracked priorities, so maybe there's still some room for making that more apparent (e.g. in initial review comments?)" I can check if we have the information about adding hash-tag in all our guides | 15:12 |
| TheJulia | We're all human, easiest thing is to have channels clearly documented. The thing that really hurts is the AI-ification of search engines like google where a search is now functionally useless because it tries to answer | 15:12 |
| TheJulia | iurygregory: I'm pretty much going to -1 any attempt for us to add more reviwer workload to tracking "how experienced the contributor is with the project unless there is an obvious disconnect which can be spotted | 15:13 |
| TheJulia | or at a minimum, let it slip because I simply can't take on the additional context | 15:14 |
| fungi | we only had one maintainer fill out the survey, so there was limited feedback to on on in determining if the experience is good for ironic maintainers in general. the metrics indicate maintainers are doing a great job, of course, but not how satisfied they are with how things are going | 15:14 |
| JayF | fungi: to be blunt, I'm thinking of it from the shallower point of "does this look like it's worthy of my attention with how little of it I have to give" | 15:14 |
| fungi | i don't think anyone is expected to pay attention to this if they have more important things going on, from their perspective | 15:15 |
| iurygregory | TheJulia, yeah, I do think we have the information but maybe is not "easy to find", not sure, I will ask someone who haven't contributed to see how it goes =) | 15:16 |
| TheJulia | I think we're going to have to frame the next survey as the "maintainer burnout survey" | 15:16 |
| TheJulia | because I think burnout is reaching a very high level at this point | 15:16 |
| fungi | yes, while the surveys try to have a positive focus, part of what we try to glean from it is "how burned out are you now, or at risk of becoming?? | 15:16 |
| JayF | the ironic thing is (pun intended) | 15:17 |
| JayF | if someone is that burned out, they aren't filling out a survey | 15:17 |
| JayF | (speaking in broad strokes, obviously) | 15:18 |
| fungi | yes, i'm not sure how to close the measurement gap on silence | 15:18 |
| fungi | anyway, i didn't have anything else, but want to revisit this in a few weeks if it seems useful and there's room on the meeting agenda | 15:19 |
| iurygregory | thanks fungi! | 15:20 |
| fungi | always a pleasure! | 15:20 |
| iurygregory | ok, moving on o/ | 15:21 |
| iurygregory | #topic Bug Deputy Updates | 15:21 |
| iurygregory | Our bug deputy was Mahnoor o/ | 15:22 |
| Mahnoor | There was one new bug filed on Monday | 15:22 |
| Mahnoor | I've pasted the link in the agenda. Triaged and set importance to medium (best estimate of mine) | 15:23 |
| iurygregory | #link https://bugs.launchpad.net/ironic/+bug/2156955 | 15:23 |
| Mahnoor | Other than that, there were no RFEs or new bugs in other projects | 15:23 |
| iurygregory | from the description I think I'm having a deja vu | 15:24 |
| iurygregory | =X | 15:24 |
| Mahnoor | (Sorry, it was not filed on Monday, my bad) :D | 15:25 |
| iurygregory | seems like at least now SuperMicro follows the normal behavior lol | 15:25 |
| iurygregory | :D | 15:26 |
| Mahnoor | Yes | 15:26 |
| iurygregory | thank you for being the bug deput Mahnoor o/ | 15:26 |
| Mahnoor | :) | 15:26 |
| iurygregory | Who is the next bug deputy? :D | 15:26 |
| TheJulia | I can't, I'll be on vacation next week | 15:27 |
| cid | I can | 15:27 |
| iurygregory | thanks cid | 15:27 |
| iurygregory | #info cid is the bug deputy | 15:27 |
| iurygregory | since we don't have RFE's I'm skipping the next topic | 15:28 |
| iurygregory | #topic Open discussion | 15:28 |
| iurygregory | Anything else we should discuss today? | 15:28 |
| TheJulia | As an FYI, I'll be out next week | 15:28 |
| iurygregory | ack o/ | 15:29 |
| iurygregory | Who can chair the next meeting? | 15:30 |
| iurygregory | I have doc appointment, so I can't promise | 15:31 |
| TheJulia | You know, it wouldn't be an awful idea to declare it "spoon recovery week" ;) | 15:32 |
| rpittau | heat wave recovery week? | 15:32 |
| Mahnoor | ++ | 15:32 |
| iurygregory | ack o/ | 15:33 |
| iurygregory | I will send an email to the ML | 15:33 |
| iurygregory | thanks everyone! | 15:33 |
| iurygregory | #endmeeting | 15:33 |
| opendevmeet | Meeting ended Mon Jun 22 15:33:32 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:33 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-06-22-15.00.html | 15:33 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-06-22-15.00.txt | 15:33 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-06-22-15.00.log.html | 15:33 |
| Sandzwerg[m] | Hello Ironic o/ What is needed to get some review for https://review.opendev.org/c/openstack/ironic/+/989431 ? We now run it for two weeks or so and it fixes our issues and we haven't noticed any new ones. So from our point of view it should be fine to merge | 15:56 |
| TheJulia | Sandzwerg[m]: I just added the "ironic-week-prio" hashtag | 16:10 |
| TheJulia | I'm *super* surprised that none of the unit tests fail with that kwarg addition | 16:10 |
| Sandzwerg[m] | Thank you | 16:10 |
| opendevreview | Doug Szumski proposed openstack/ironic master: Fix autodetect ramdisk deploy with vmedia via Nova https://review.opendev.org/c/openstack/ironic/+/994340 | 16:39 |
| TheJulia | reviews on I10c88426d5838820ecf6853dca5b3878dc29bdf4 would be appreicated | 19:21 |
| TheJulia | https://review.opendev.org/q/I10c88426d5838820ecf6853dca5b3878dc29bdf4 | 19:21 |
| opendevreview | Merged openstack/ironic-python-agent unmaintained/2024.1: Add a flag to disable installing bootloaders https://review.opendev.org/c/openstack/ironic-python-agent/+/993025 | 21:36 |
| opendevreview | Merged openstack/ironic-python-agent stable/2025.1: Add a flag to disable installing bootloaders https://review.opendev.org/c/openstack/ironic-python-agent/+/993024 | 21:36 |
| opendevreview | Merged openstack/ironic-python-agent unmaintained/2023.1: Add a flag to disable installing bootloaders https://review.opendev.org/c/openstack/ironic-python-agent/+/993026 | 23:20 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!