| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: OSSN-0102: Neutron sub-resource parent ownership https://review.opendev.org/c/openstack/security-doc/+/996209 | 06:37 |
|---|---|---|
| opendevreview | Goutham Pacha Ravi proposed openstack/security-doc master: WIP: OSSN-0103: Glance legacy Tasks import SSRF https://review.opendev.org/c/openstack/security-doc/+/996210 | 06:47 |
| gouthamr | tc-members: a gentle reminder that the weekly meeting will be hosted here in ~50 minutes | 16:10 |
| gouthamr | the agenda is here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting | 16:10 |
| *** opendevstatus_ is now known as opendevstatus__ | 16:38 | |
| *** opendevstatus__ is now known as opendevstatus | 16:38 | |
| *** opendevstatus is now known as Guest12850 | 16:38 | |
| gouthamr | #startmeeting tc | 17:01 |
| opendevmeet | Meeting started Tue Jul 7 17:01:39 2026 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:01 |
| opendevmeet | The meeting name has been set to 'tc' | 17:01 |
| gouthamr | 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 |
| gouthamr | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda | 17:01 |
| gouthamr | #topic Roll Call | 17:01 |
| spotz[m] | o/ | 17:02 |
| gouthamr | courtesy-ping: cardoe, bauzas, noonedeadpunk, frickler, mnasiadka | 17:03 |
| frickler | \o | 17:03 |
| gouthamr | noted absence: d a n s m i t h | 17:03 |
| mnasiadka | o/ | 17:03 |
| cardoe | o/ | 17:04 |
| cardoe | dual wielding as 7th grade math tutor sorry | 17:04 |
| gouthamr | :) | 17:05 |
| gouthamr | let's get started.. | 17:05 |
| gouthamr | #topic Last Week's Action Items | 17:05 |
| gouthamr | we discussed x/cursive's move into the openstack/ namespace | 17:06 |
| noonedeadpunk | o/ | 17:06 |
| gouthamr | the move itself is scheduled in a couple of days (July 9th), but, we wanted to inform/get consent from existing core reviewers or original maintainers | 17:06 |
| gouthamr | i dug into this a little bit and shared context on the openstack-discuss list | 17:07 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YBU4IAB3EEMXG6H6JCZH4DRYCV2FK3O3/ ([oslo][barbican][nova][glance][cinder][tc] Bringing cursive under Oslo governance) | 17:07 |
| gouthamr | before doing this, I tried to track down the original maintainers from JHU | 17:08 |
| gouthamr | but folks have either left JHU or have switched roles internally.. so, this seemed like a futile attempt | 17:08 |
| fungi | the project-config change still needs fixing | 17:09 |
| gouthamr | i do think their goodbye email to the openstack-discuss list which has been brought up a couple of times is sufficient to indicate their consent to this: https://lists.openstack.org/pipermail/openstack-dev/2018-July/131978.html | 17:09 |
| fungi | i can try to fix it up if nobody from the project side has time | 17:10 |
| gouthamr | ack, ty for offering; if they seem non-controversial - it definitely makes sense | 17:10 |
| fungi | also we may be unexpectedly short some coverage on the opendev sysadmins team now at the planned time, we'll discuss at the opendev meeting in a couple of hours but may proceed regardless | 17:11 |
| gouthamr | ah ack | 17:11 |
| gouthamr | anything else to discuss regarding cursive? | 17:12 |
| gouthamr | tkajinam: ty for your response on the ML thread | 17:12 |
| cardoe | I think we just do it | 17:12 |
| gouthamr | +1, lazy consensus will work here.. and i've seen the pattern across our community that we're willing to add past reviewers back to core reviewer groups in case they resume their activity | 17:14 |
| fungi | note that barbican folks also have maintainer access to the repo, were they some of the ones you tried to contact? | 17:15 |
| gouthamr | no those folks are on the openstack-discuss list | 17:15 |
| fungi | cool, wfm | 17:15 |
| gouthamr | the "castellan" ownership comparison was made by them originally.. oslo+barbican co-maintain that repo | 17:16 |
| gouthamr | mharley[m]: ^ hope the team's still aligned with decisions from 2020/2021 | 17:17 |
| gouthamr | next action item was around PyPI archival for retired projects | 17:17 |
| gouthamr | noonedeadpunk: did you explore this for venus? any insights to share? | 17:18 |
| gouthamr | related: launchpad tracker cleanup.. | 17:19 |
| gouthamr | this is all onerous stuff.. but, great for hygiene | 17:19 |
| gouthamr | we can add cleanups to the tracker etherpad and do it slowly over time too, but, it'd be nice to get the project-team-guide language added when we align on the process | 17:21 |
| noonedeadpunk | unfortunatelly I didn't made any progress there, as got quite tackled with internal issues | 17:22 |
| noonedeadpunk | I am hoping to close that topic this week 100% | 17:23 |
| gouthamr | ack no problem; can check on it again next week.. | 17:23 |
| gouthamr | ty for tackling it! | 17:23 |
| noonedeadpunk | sorry :( | 17:23 |
| spotz[m] | Doug was around Barbican during 2020/2021 and still is FYI | 17:23 |
| gouthamr | i suppose the vitrage cleanup is progressing fine | 17:24 |
| gouthamr | let us know if you need any reviews/assistance for it | 17:24 |
| gouthamr | the next action item was around the Contributor Experience Working Group. I owe the ML a post - didn't work on this last week - however, i was trying to recruit some folks and discussing ideas | 17:25 |
| gouthamr | the ML post can be a good way to seed that discussion publicly and organize better.. | 17:26 |
| gouthamr | now that i'm over a loong weekend, i'll get to this soon-ly | 17:26 |
| gouthamr | the final action item i see is the one around formalizing what counts as activity in the TC and seeding some process on inactivity.. this will be good to throw some proposals about so we can gain some consensus on the rare occasions that this happens | 17:30 |
| gouthamr | i don't expect to work on it myself, but the consensus here seemed to be allowing the impending elections to tackle the existing issue | 17:31 |
| fungi | i have an outstanding todo for adding active core reviewer querying to the election tooling some time this year. if that's meant to go into effect for the indri cycle elections i can prioritize work on it | 17:31 |
| gouthamr | way to name drop the lemur | 17:31 |
| fungi | oh, sorry, activity in the tc, not review activity for electorate, i misread | 17:32 |
| gouthamr | but great/timely question :D | 17:32 |
| * fungi was on a completely different topic | 17:32 | |
| mnasiadka | Although somewhat related | 17:32 |
| gouthamr | as you may be aware, election officials and spotz[m] have been doing some election prep.. i mentioned that early nominations are encouraged in case of holidays - same stuff as usual | 17:33 |
| gouthamr | on this week's TC post to the ML | 17:33 |
| gouthamr | please, do especially encourage folks to consider being a part of the TC | 17:33 |
| gouthamr | i will ask folks to get in touch with existing TC members if they want to learn more about the role and if they'd like mentorship/shadow you :) | 17:34 |
| spotz[m] | Land we can always use more officials | 17:34 |
| gouthamr | we are doing a _lot_ of work, and many times, we end up backfilling some work and helping out the community - this might all be exciting for someone you know in the community | 17:35 |
| gouthamr | spotz[m]: +1 | 17:35 |
| gouthamr | alright, about the AC changes | 17:37 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/995535 (Add reviewers as Active Contributors) | 17:37 |
| gouthamr | this is a charter change proposal ^ | 17:37 |
| gouthamr | and it needs 2/3rds of the TC to vote positively | 17:37 |
| gouthamr | it might take time to review/iterate on this, and so i want to know if there are any hard objections to this proposal | 17:38 |
| fungi | from an election tooling perspective, the main thing i need to know is whether it's expected to take effect for the 2027.1/indri cycle electorate or 2027.2/j cycle | 17:40 |
| gouthamr | knowing that might help fungi land these changes in the election tooling prior to the "email deadline": https://releases.openstack.org/hibiscus/schedule.html#i-election-email-deadline | 17:40 |
| fungi | yes | 17:40 |
| gouthamr | the deadline is August 19th, 2026 at 00:00 UTC | 17:40 |
| spotz[m] | I do want to do a grammar change in the sentence before it after it merged | 17:41 |
| fungi | so roughly 6 weeks to decide and develop the implementation | 17:41 |
| gouthamr | yes, hopefully we can all look and comment this week | 17:42 |
| gouthamr | anything else about ongoing action items? | 17:42 |
| gouthamr | we've been quite busy :P where tracking action items week on week is taking up most of our meeting | 17:45 |
| gouthamr | i'll table the TC visioning kick-off again, and probably seed it async | 17:45 |
| gouthamr | my goal is to begin the scatter-gather on ideas with you, and the community could weigh in as well | 17:46 |
| gouthamr | let me see how much progress i can make async about this.. | 17:47 |
| gouthamr | if you would like to work on it with me, please ping me here after the meeting | 17:47 |
| gouthamr | #topic Barbican UI situation | 17:48 |
| gouthamr | noonedeadpunk: the floor is yours | 17:48 |
| gouthamr | *crickets* | 17:50 |
| spotz[m] | Hehe | 17:50 |
| fungi | apropos | 17:50 |
| gouthamr | haha, okay, i think the situation is that a bunch of contributors have been working on barbican-ui | 17:51 |
| spotz[m] | He could be typing a wall of text….. | 17:51 |
| gouthamr | oh, if that's the case, i'd stop trying to fill that in | 17:51 |
| spotz[m] | I was giving him the benefit of the doubt:) | 17:53 |
| dmendiza[m] | 🙋♂️ | 17:53 |
| gouthamr | dmendiza[m], ty for joining | 17:54 |
| gouthamr | are you still involved with barbican development/maintenance? and can you help address this situation | 17:54 |
| gouthamr | noonedeadpunk said this about barbican-ui on the TC meeting wiki: "new contributors are volunteering to revive the project, but are denied by current project leadership, because project considered as unmaintained by them" | 17:55 |
| dmendiza[m] | Right, so | 17:55 |
| dmendiza[m] | barbican-ui never really got off the ground. | 17:56 |
| dmendiza[m] | There was interest to make it happen a long time ago, but the issue that the core team had -- and we still have -- is that we are not front end developers | 17:56 |
| dmendiza[m] | So there is no one in the core reviewer team that is confident enough to review front end code | 17:57 |
| gouthamr | ah i see, i totally sympathize with that.. we have a number of horizon plugins which share that issue... and we keep trying to gather help from the horizon team that's stretched thin.. | 17:58 |
| fungi | do the core reviewers for other services typically review changes to their horizon plugins, or do they have separate groups of reviewers on those repositories? | 17:58 |
| gouthamr | fungi: manila-core does its own, poorly.. and relies a lot on borrowed help from horizon-core (tmazur/rdopiera/jjasek/others) | 17:59 |
| mnasiadka | Gerrit groups are separate, but I don’t think any service team has a dedicated UI reviewer | 17:59 |
| mnasiadka | gouthamr: Manila is still in a better shape, because it has some functional tests (I think watcher also has them or has them in progress) - majority of the *-ui/*-dashboard projects are in far worse shape testing wise | 18:00 |
| gouthamr | so this could spiral into a bigger "we need UI (and also specific domain) expertise" question.. | 18:01 |
| noonedeadpunk | afaik horizon team has access to the most of plugins | 18:01 |
| gouthamr | yes | 18:01 |
| noonedeadpunk | can't say they actively maintain them | 18:01 |
| fungi | maybe ask the prospective maintainers for barbican-ui to start by improving its test coverage? | 18:01 |
| noonedeadpunk | but | 18:01 |
| noonedeadpunk | there're folks who decided to step in and refactor and make a barbican-ui a proper one | 18:02 |
| spotz[m] | Well I think they would need to write the tests and the code to start with? | 18:02 |
| noonedeadpunk | I am not really sure about how continious their maintenance should be | 18:02 |
| noonedeadpunk | but we either need to be clear that project is dead | 18:02 |
| noonedeadpunk | or allow other parties to step in | 18:02 |
| noonedeadpunk | spotz[m]: they already did I thnk | 18:03 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/barbican-ui/+/986690 | 18:03 |
| fungi | when it comes tounfamiliar parts of projects i'm a maintainer for, solid existing test coverage makes me a lot more confident that things i approve aren't going to break intended functionality at least, and makes me more willing to review | 18:03 |
| noonedeadpunk | but I think they've accidentally dropped zuul.yaml | 18:03 |
| dmendiza[m] | I think we would not be opposed to barbican-ui being maintained by other folks. Maybe x/barbican-ui or a separate barbican-ui-core team. | 18:03 |
| gouthamr | i think the latter is a better course of action | 18:04 |
| spotz[m] | I also have possibly a radical thought and definitely don’t want to throw more work on the horizon team, but what if ui repos fell under them vs the service as it should be front end dev and API calls? Or atleast it is in my head without looking | 18:04 |
| noonedeadpunk | I'd say that barbican-ui-core team makes total sense for me | 18:04 |
| fungi | and people implementing good testing gives me better confidence in their capability to review changes to the software as well | 18:05 |
| gouthamr | ++ | 18:05 |
| gouthamr | we're five minutes over, this can be a discussion that we can have on openstack-discuss and draw in the horizon team as well | 18:05 |
| noonedeadpunk | sure, and they did some testing. I think the effort was a bit dead due to response in line with - don't try to contribute here, it's dead anyway | 18:05 |
| noonedeadpunk | and then I realized it's not marked as dead and we have no tracktion on it at all.... | 18:06 |
| noonedeadpunk | anyway | 18:06 |
| gouthamr | my knee-jerk reaction is that's weird, and we should be having an open discussion about it and steering interested parties towards a feasible solution to the problem | 18:07 |
| noonedeadpunk | I'd vote for a separate core team for it, and then we can add horizon people or these folks if they're interested in continious mintenance | 18:07 |
| noonedeadpunk | or just kill it off properly if there's nobody to step in for future as well | 18:08 |
| gouthamr | this does have governance/release implications though - for one, we're past the membership deadline for hibiscus | 18:08 |
| noonedeadpunk | as vibe code ui is not same as provide continious maintenance... | 18:08 |
| gouthamr | do you mind seeding this discussion on the ML? or if it can wait until next week's meeting, that's fine too | 18:08 |
| noonedeadpunk | I can try to :) | 18:09 |
| gouthamr | thanks noonedeadpunk | 18:09 |
| gouthamr | we're ~10 minutes past | 18:09 |
| noonedeadpunk | sorry | 18:09 |
| gouthamr | thank you all for participating, let's wrap it up here | 18:09 |
| gouthamr | a couple of late breaking minutes items.. | 18:10 |
| gouthamr | all hail Indri, our new animal overlord.. | 18:10 |
| gouthamr | OpenInfra Days NA is being planned, talk to spotz[m] if you need more info, CFP is open already, details will be coming to your favorite mailing list soon | 18:10 |
| gouthamr | #endmeeting | 18:10 |
| opendevmeet | Meeting ended Tue Jul 7 18:10:45 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:10 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2026/tc.2026-07-07-17.01.html | 18:10 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-07-07-17.01.txt | 18:10 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-07-07-17.01.log.html | 18:10 |
| fungi | noonedeadpunk: maybe encourage the prospective new contributors/maintainers for barbican-ui to engage on the ml thread when you start it. that also helps set expectations for community involvement rather than quitely working in isolation | 18:10 |
| gouthamr | yes, kpdev, ivan anfimov, dmitri chubinidze et al aren't here.. and i'd nudge them all to air their concerns out in the open, on the ML | 18:13 |
| noonedeadpunk | ++ | 18:13 |
| noonedeadpunk | I will | 18:13 |
| noonedeadpunk | just got an email from Ivan with excuses not being able to participate in TC meeting today | 18:14 |
| gouthamr | ah, np.. this is a good forum for visibility, but not as good as openstack-discuss imo for this topic :) | 18:32 |
| fungi | also folks from zte are reaching out to the foundation again about the risc-v sig proposal. i once again pointed them to the motion voting rules, noted that the proposer had just addressed prior review comments in a revision yesterday, and that the current state is short one roll-call vote but also needs 6 more calendar days before it's eligible for approval | 18:45 |
| fungi | they seemed disheartened that the only reply to their ml post introducing the idea for the sig was someone asking for test resources for another community | 18:47 |
| gouthamr | ah, makes sense.. I can reiterate the review rules on the patch if they're unfamiliar with it.. and good to whip votes too | 18:51 |
| fungi | the opendev sysadmins are planning to move forward with the cursive project rehoming on thursday as previously scheduled, i intend to run the maintenance | 19:31 |
| gouthamr | neat, ty for handling that fungi! | 20:13 |
| gouthamr | fungi: quick question on https://review.opendev.org/c/openstack/project-config/+/990122/1/zuul.d/projects.yaml | 20:28 |
| gouthamr | fungi: do i need to set up the "official-openstack-repo-jobs" here? | 20:28 |
| gouthamr | stephenfin was just dropping the existing publish-to-pypi job, i don't know if he meant to do that stuff in another change, and if it'll matter | 20:29 |
| fungi | i would add it, yes | 20:34 |
| fungi | that way things like automated github mirroring will get set up | 20:35 |
| gouthamr | ++ | 20:35 |
| opendevreview | Merged openstack/governance master: Retire cinderlib https://review.opendev.org/c/openstack/governance/+/994004 | 20:44 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!