15:01:02 <tmazur> #startmeeting horizon
15:01:02 <opendevmeet> Meeting started Wed Aug 13 15:01:02 2025 UTC and is due to finish in 60 minutes.  The chair is tmazur. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:02 <opendevmeet> The meeting name has been set to 'horizon'
15:01:15 <tmazur> Hello everyone and welcome to the weekly meeting!
15:01:40 <jjasek> Hello
15:01:49 <chubinidzedr> Hi)
15:02:33 <rdopiera> o/
15:03:04 <tmazur> I think we have everyone who is not on PTO, so let's start
15:03:32 <anfimovir> hello
15:03:41 <tmazur> Agenda for today: https://etherpad.opendev.org/p/horizon-release-priorities#L42
15:03:57 <tmazur> #topic Notices
15:04:43 <tmazur> Schedule reminder: this week is R-7. Flamingo Schedule: https://releases.openstack.org/flamingo/schedule.html
15:05:37 <tmazur> Feature freeze is 2025-08-28
15:07:05 <tmazur> PTL nomination period is still open, 1 week left
15:09:22 <tmazur> I have proposed my candidacy, and anfimovir proposed his
15:09:54 <tmazur> So I guess for the first time in quite a while we will have voting :)
15:10:08 <fungi> congrats!
15:10:29 <fungi> i wish more teams had multiple candidates these days
15:10:57 <tmazur> The last time I was voting for Horizon PTL was in 2013 :D
15:11:03 <rdopiera> or any candidates, in some cases
15:11:06 <anfimovir> =)))
15:13:53 <tmazur> Ok, next topic
15:13:56 <tmazur> #topic Release priorities
15:14:36 <tmazur> The SDK patch was merged, thanks to all reviewers
15:14:46 <tmazur> We still have WIP: 953302: WIP: remove remaining neutronclient calls | https://review.opendev.org/c/openstack/horizon/+/953302
15:15:45 <tmazur> I keep tagging it along to not forget about it. Hopefully the owner will have time to proceed on it.
15:20:09 <tmazur> #topic Bug deputy report
15:20:50 <opendevreview> Ivan Anfimov proposed openstack/horizon master: wip  https://review.opendev.org/c/openstack/horizon/+/957233
15:20:54 <tmazur> There's a recent bug which has a patch already: https://bugs.launchpad.net/horizon/+bug/2115353
15:21:39 <tmazur> So would be nice to take a look: https://review.opendev.org/c/openstack/horizon/+/953413
15:22:54 <anfimovir> It would be nice to receive release notes along with such changes.
15:23:11 <anfimovir> I already touched Pavlo about it few days ago.
15:24:36 <anfimovir> Radomir hello, please look new bug https://bugs.launchpad.net/horizon/+bug/2120195
15:24:56 <anfimovir> I think we can use old MR for sort this https://review.opendev.org/c/openstack/horizon/+/574310
15:25:54 <rdopiera> anfimovir: I'm afraid I can't really help much with Django serializers
15:26:46 <anfimovir> No problem, I test it.
15:30:12 <tmazur> Thanks
15:30:27 <tmazur> #topic Open reviews
15:30:38 <tmazur> https://review.opendev.org/q/project:openstack/horizon+status:open
15:30:50 <tmazur> https://etherpad.opendev.org/p/horizon-release-priorities#L60
15:31:20 <fungi> (i also added something to the on-demand agenda in case there are a few minutes at the end to circle back, sorry!)
15:31:47 <tmazur> Sure, I'll return to it after this topic
15:32:44 <tmazur> We did a good job last week on reviews. Thanks everyone! Let's keep it like this ;)
15:33:11 <opendevreview> Ivan Anfimov proposed openstack/horizon master: wip  https://review.opendev.org/c/openstack/horizon/+/957233
15:33:44 <opendevreview> Ivan Anfimov proposed openstack/horizon master: wip  https://review.opendev.org/c/openstack/horizon/+/957233
15:34:44 <anfimovir> Please review this MR - https://review.opendev.org/c/openstack/horizon/+/956996 - I think, this help another users receive more details about our changes.
15:35:00 <anfimovir> This MR not touch code, only release notes.
15:36:33 <tmazur> Thanks anfimovir
15:38:51 <tmazur> #topic On-Demand Agenda
15:38:59 <tmazur> fungi please go ahead
15:39:05 <fungi> i'll try to be quick, but there's a lot we dug into... for some background on openstack-wide metrics analysis see ildikov's most recent ml post from a month or so back:
15:39:14 <fungi> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/NTBNI7YIDCWBR6BTPEKVZIODWTVUIOXO/ BtG metrics analysis
15:39:20 <fungi> also could be worthwhile to revisit her previous post in that thread going over the contributor and maintainer survey results (and anyone who hasn't filled those out for epoxy, please see if you can find a few minutes to do that!)
15:39:27 <fungi> as a follow-up activity, we've started doing some team-specific analyses, focusing on teams that had multiple contributor and maintainer survey responses (already did nova, cinder, ironic, octavia, kolla and neutron in recent weeks)
15:39:33 <fungi> we're early in the process of analyzing these stats with a focus on improving the experience for maintainers and contributors, so for now this is probably a lot of stuff you already know, or at least confirming what you expected
15:39:49 <fungi> a big part of this is establishing a baseline so that we can better gauge whether future attempts at improving have any observable impact, but we aren't at the point where we have much in the way of guidance or recommendations yet
15:39:55 <fungi> we have plans to continue with this sort of surveying and metrics analysis over coming release cycles; as for the initial results...
15:40:01 <fungi> the contributor survey had 4 responses for horizon and all respondents had contributed for at least one year though not all were contributors to other open source projects
15:40:11 <fungi> feedback was positive (averages of 2.5-4.75 out of 5) with the highest score on "You receive actionable feedback from other reviewers" and lowest for "Changes you propose are reviewed in a timely manner"
15:40:18 <fungi> the top challenge reported by all respondents was "I have trouble getting the attention of reviewers for my change" (this tends to be a pretty common problem across much of openstack, fwiw)
15:40:28 <fungi> the maintainer survey had only 1 response so far, ranking 4 on almost everything except for a 5 on "You receive actionable feedback from other reviewers"
15:40:42 <fungi> contributing challenge reported by that maintainer was similar to those from the contributor survey (review attention)
15:40:50 <fungi> top challenges with reviewing were contributors not addressing review feedback or test failures in a timely manner, and occasionally being blocked by ongoing test problems
15:41:01 <fungi> looking at metrics we gathered from gerrit for the past 5 development cycles, review activity has been hovering around merging/closing as many changes as are being opened, so mostly keeping up with the volume
15:41:11 <fungi> the revision average is also around 1-3 but usually just 1, so changes being proposed are most often approved without needing adjustment but occasional ones seem to need a lot more revisions
15:41:24 <fungi> the active maintainer count dropped by 1 in the last cycle, which seems to coincide with review durations roughly doubling (still pretty good, but further maintainer shrinkage could have more severe impact on sustainability)
15:41:35 <fungi> it's also worth noting that the number of incidental non-maintainer reviewers has remained fairly steady over recent cycles, which could point to opportunities to onboard some as new maintainers
15:41:46 <fungi> sorry, i know that's a pretty big info dump (i tried to pare it down as much as possible), and i'm happy to answer questions or take feedback either here in the meeting or any time after
15:43:28 <fungi> and if there are no questions, that's all i had on the topic for now, thanks for reading!
15:48:08 <tmazur> Thanks fungi! I am looking into the statistics now. We will definitely use this information
15:48:16 <fungi> seems like nobody has questions? i guess i covered it well enough (or it's just overwhelming)
15:48:39 <fungi> i can pull more detailed stats if you know what you want to see, i was mainly trying to give a high-level summary of what we found
15:49:22 <fungi> feel free to hit me up with questions any time, i lurk in this channel anyway
15:49:30 <tmazur> I am playing with it right now. How do you tell maintainers contributions from non-maintainers?
15:50:23 <fungi> that's tricky, i can get you the custom query we used for that, but basically we count anyone that did code-review +2/-2 or workflow +1 in any of your team's repositories during that cycle as an active maintainer
15:50:48 <tmazur> So, pretty much same as stackalytics
15:50:59 <tmazur> I was hoping we have any special tag
15:51:21 <fungi> how maintainers get applied to projects varies enough across teams that it's hard to come up with a generalization
15:51:33 <tmazur> Right
15:51:35 <fungi> other than going on observed behaviors
15:53:54 <fungi> i will say that horizon saw a lot less shrinkage of active maintainer count than many teams in openstack, but it was a pretty small number to start with (5 up until last cycle when it dropped to 4)
15:54:41 <fungi> still not the smallest active maintainer account, by far
15:55:25 <fungi> so it looks pretty healthy, but this seems to be ain inflection point where things could become unhealthy quickly if you don't try to pull in some new help
15:56:35 <fungi> the reviewer and maintainer counts we've been looking at for now are also linear vectors, it's in our plans to start doing multidimensional analyses for some of this stuff in the future
15:57:08 <tmazur> Oh that's interesting
15:57:47 <fungi> like looking at 80/20 split curves for how many active maintainers handle what volume of the load, that kind of stuff
15:58:23 <tmazur> That would get us a better picture, cool
15:59:02 <opendevreview> Ivan Anfimov proposed openstack/horizon master: wip  https://review.opendev.org/c/openstack/horizon/+/957233
15:59:15 <tmazur> Anyway, I have to start wrapping up the meeting. Thanks a lot fungi! I will bug you about the statistics filters when I play a bit more, if you don't mind
15:59:25 <fungi> thanks for your interest!
15:59:26 <opendevreview> Ivan Anfimov proposed openstack/horizon master: wip  https://review.opendev.org/c/openstack/horizon/+/957233
15:59:35 <fungi> and yeah, any time you like
15:59:41 <tmazur> #topic Open discussion
15:59:53 <tmazur> Team, do we have anything for the open discussion?
16:00:12 <jjasek> Nothing from my side, thank you :-).
16:00:32 <anfimovir> No, thanks you
16:01:05 <tmazur> I have to cancel the next upstream meeting since most of the team has downstream activities conflicting with this time slot
16:01:37 <anfimovir> See all 27.08
16:01:38 <tmazur> So see you all in two weeks!
16:01:48 <tmazur> Thanks for joining!
16:01:58 <tmazur> #endmeeting