Monday, 2026-09-28

opendevreviewRajiv Mucheli proposed openstack/barbican master: p11_crypto: implement asymmetric RSA key generation on the HSM  https://review.opendev.org/c/openstack/barbican/+/99619702:22
vakwetuo/14:57
dmendiza[m]🙋‍♂️15:00
mharley[m]#startmeeting barbican15:00
opendevmeetMeeting started Mon Sep 28 15:00:49 2026 UTC and is due to finish in 60 minutes.  The chair is mharley[m]. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'barbican'15:00
anfimovirHello. 15:00
noonedeadpunko/15:00
chubinidzedrHi15:01
mharley[m]Courtesy ping for dmendiza[m] ade_lee d34dh0r53 Luzi tosky tobias-urdin jjung mharley Freeman Boss lpiwowar xek tkajinam LinuZZ fprzewozn toabctl15:01
mharley[m]Hello, everyone.  Good to see some folks here.15:01
xeko/15:01
mharley[m]You can find the meeting's agenda at the following link:15:01
mharley[m]#link https://etherpad.openstack.org/p/barbican-weekly-meeting15:02
mharley[m]Guys, unfortunately I can't stay after 03:30 PM UTC since I'll have an appointment.  15:02
tkajinamo/15:03
mharley[m]You can keep on discussing, but I'll have to ask dmendiza do end the meeting.15:03
mharley[m]#topic Review Past Meeting Action Items15:03
mharley[m]#link http://eavesdrop.openstack.org/meetings/barbican/202615:03
dmendiza[m]mharley: sure, just do a #chair dmendiza[m]15:04
mharley[m]Ack, dmendiza .15:04
mharley[m]So, on last meeting, tkajinam mentioned they have a few patches to be reviewed.15:05
mharley[m]And I mentioned we have the reviewathons during the Fridays.15:05
dmendiza[m]Yeah, we had a Reviewathon, but I'm not sure if we got to those patches? 🤔15:07
tkajinamyeah, but these are still pending on reviews15:07
mharley[m]And some by anfimovir as well.15:07
tkajinamhttps://meetings.opendev.org/meetings/barbican/2026/barbican.2026-09-14-15.01.html15:07
mharley[m]The patches by anfimovir and the whole subject is meant to be discussed during the open discussion area of the meetign.15:07
mharley[m]I missed last week's reviewathon since I was on PTO.15:08
mharley[m]s/the/this/, s/meetign/meeting/15:08
tkajinamthe backports I mentioned ( 987264 and 987267 ) are easy for review, I think15:08
tkajinamthese are clean backports15:08
tkajinamso appreciate your time probably during the next reviewathon (or any earlier time this week)15:09
mharley[m]Yep, those patches should be reviewed.15:09
mharley[m]#topic Liaison Updates15:10
mharley[m]We are in the Hibiscus 2026.2 release week.15:10
mharley[m]#link https://releases.openstack.org/hibiscus/schedule.html15:10
vakwetu987264 done :)15:10
vakwetu(and ditto for 98726715:11
mharley[m]We've finally got a PQC patch merged for Barbican:15:12
mharley[m]#link https://review.opendev.org/c/openstack/barbican/+/98508015:12
mharley[m]Others to come.15:13
mharley[m]There are currently no more news.15:13
mharley[m]#topic Bug Review15:13
dmendiza[m]Yo!15:14
dmendiza[m]You skipped my topic :(15:14
dmendiza[m]Oh I guess we do those after the bugs now? ... sorry, I'm used to Bugs being the last topic of the meeting 😅15:15
mharley[m]Bugs is the current topic.  Open Discussion is the last one.15:15
mharley[m]There were at least two new bugs they are already being addressed.15:17
mharley[m]#link https://bugs.launchpad.net/barbican/+bugs?orderby=-id&start=015:17
mharley[m]* new bugs for Barbican, but they are15:17
mharley[m]One new bug for the python-barbicanclient, but with the corresponding fix proposted:15:18
mharley[m]#link https://bugs.launchpad.net/python-barbicanclient/+bugs?orderby=-id&start=015:19
mharley[m]This should be also reviewed during this week's reviewathon.15:19
mharley[m]No new bugs for Castellan.15:20
mharley[m]#link https://bugs.launchpad.net/castellan/+bugs?orderby=-id&start=015:20
mharley[m]And likewise, no new bugs for Cursive.15:21
mharley[m]#link https://bugs.launchpad.net/cursive/+bugs?orderby=-id&start=015:21
mharley[m]#topic Open Discussion15:21
mharley[m]So, we do have two new topics to discuss during today's meeting.15:22
mharley[m]I saw yours, dmendiza .  Would you like to elaborate?15:22
dmendiza[m]#topic Update guidelines for Gerrit reviews15:22
dmendiza[m]Yeah, we were discussing this with alee_ and Grzegorz Grasza .  It's a proposal to try to speed up reviews15:23
dmendiza[m]Currently, our guidelines are 2x +2 from core reviewers before we merge15:23
dmendiza[m]usually the second +2 also does the +W15:24
dmendiza[m]The proposal is for core reviewers to consider 2x +1 from non-core reviewers as a +215:24
dmendiza[m]And to lower to just 1x +2 for automated patches, like translations15:25
dmendiza[m]and possibly just 1x +2 for backports to stable branches15:25
mharley[m]Seems reasonable to me, but what about specs?15:25
mharley[m]And even if we change that mechanism, only core reviewers can provide W+1, right?15:26
dmendiza[m]I think 2x +2 on specs would still be required, but I'm open to suggestions15:26
dmendiza[m]Right, only core reviewers can +@15:26
vakwetuwe've always had a policy of just 1 x +2 on trivial patches - so that includes translations15:26
dmendiza[m]err +W15:26
mharley[m]I don't think we should change the way for specs.15:26
vakwetuI think specs definitely need 2 x +2 15:27
dmendiza[m]vakwetu: not sure that's documented anywhere... 🤔15:27
vakwetuprobably should be :)15:27
mharley[m]I don't remember either, dmendiza.  Besides, what's the definition of a "trivial patch"?15:28
dmendiza[m]trivial patch = translations, typos15:28
mharley[m]#chair dmendiza 15:29
opendevmeetWarning: Nick not in channel: dmendiza15:29
opendevmeetCurrent chairs: dmendiza mharley[m]15:29
dmendiza[m]It's dmendiza[m]15:29
mharley[m]Guys, I'm leaving now.  Enjoy the rest of the meeting.  I'll check the notes afterwards.15:29
dmendiza[m]on IRC side15:29
xekI propose we have a document specifying all this, that should be gated behind this review process15:29
vakwetubut yeah - specs are we decide where things are going and what features we want to add, and if a feature is defined enough - definitely need 2 x +215:29
vakwetuxek++15:29
dmendiza[m]heh, I guess I'll have to log in to hexchat as dmendiza to end this 😅15:30
xekideally it should be in a repo governed by tc, but idk15:30
dmendiza[m]No, review rules are at the discretion of the team, not the TC15:30
tkajinamyeah15:30
xekso we should have something like a barbican-governance repo15:30
dmendiza[m]Just a page on the wiki seems fine to me15:31
xekbut I'm ok with whatever repository, so that it's a kind of a documentation under a link that we can refer to15:31
tkajinammaybe add CONTRIBUTING.rst to barbican repo ?15:31
xekdo we then vote on it during meetings to change it?15:32
xekoh, yeah, contributing would be nice /me thinks15:32
vakwetu+1 for Contributiing ..15:33
tkajinamor add something to existing contributir guide. that might be a better places than CONTRIBUTING.rst at top level15:34
dmendiza[m]-1 for CONTRIBUTING.rst just because we'd have to copy/paste it into every single repo we own15:34
tkajinambut doc/source/contributor/contributing.rst in barbican already covers all repos under barbican's governance it seems15:34
tkajinamhttps://docs.openstack.org/barbican/latest/contributor/contributing.html15:35
dmendiza[m]Ah yes, was looking for that ... the Wiki link is broken it seems15:35
xekit actually has the "getting your patch merged" section about +2s15:35
tkajinamyeah15:36
opendevreviewMerged openstack/barbican stable/2026.1: Add note about enforce_new_defaults runtime override  https://review.opendev.org/c/openstack/barbican/+/98726415:36
opendevreviewMerged openstack/barbican stable/2025.2: Add note about enforce_new_defaults runtime override  https://review.opendev.org/c/openstack/barbican/+/98726715:36
dmendiza[m]Cool, seems like we're pretty much all in agreement15:36
mharley[m]My appointment was just cancelled.  Back to the meeting. :-) 15:36
dmendiza[m]I'll propose a patch to update the contributing doc 15:37
dmendiza[m]mharley: yay?15:37
tkajinamit'd be nice if the old meeting slot mentioned in the doc is also updated :-)15:37
mharley[m]I'm OK with this approach, dmendiza .15:38
xekyep, lets draft a patch for that file and have a discussion and vote on it in gerrit15:38
dmendiza[m]Wiki needs some update TLC as well15:38
dmendiza[m]#link https://wiki.openstack.org/wiki/Barbican15:38
tkajinam+115:38
dmendiza[m]Cool, we can move on to the next topic15:39
dmendiza#topic barbican-ui-core group15:42
mharley[m]Yes, so this topic has been discussed a few times between anfimovir and me through email.15:43
mharley[m]chubinidzedr: are you around?15:44
chubinidzedrmharley: yep15:45
mharley[m]Cool, your name is there among the interested folks.  anfimovir is here as well?15:45
anfimovirYes yes.15:45
mharley[m]So the proposal is to have a dedicated/separated group of reviewers for all patches related to the barbican-ui project.15:46
mharley[m]What are the community's stances on that?15:46
mharley[m]As I already noted in the meeting's Etherpad, I have no objections.  I believe this can unblock further progress on the project as it can walk independently of the Barbican core code.15:47
xekno objections from me15:47
vakwetume neither15:48
mharley[m]dmendiza: any considerations?15:48
mharley[m]* dmendiza: any considerations?15:49
dmendiza[m]No concerns on my end.  It'll be nice to see barbican-ui make some progress15:49
mharley[m]Great, folks.  So we have a consensus.15:49
mharley[m]There are a few points to cover yet.  First one is the membership.  Anyone else besides chubinidzedr and anfimovir to be part of it?  I can't find the nickname of Kiran Pawar.15:50
anfimovirI talked with him few weeks ago, He will try to ask for time off work for this—just to get some help.15:52
dmendiza[m]mharley: that can be figured out later ... I think the PTL (i.e. you) should be a part15:52
dmendiza[m]mostly for management reasons15:52
anfimovir++15:53
dmendiza[m]Next steps would be to create the gerrit group.  Membership can be figured out later once the group is created.15:53
tkajinamI think general recommendation is to have primary core ( I mean barbican-core) part of the subgroup specific to one of its repositories15:53
dmendiza[m]yeah that would make sense also15:53
tkajinamso create barbican-core-ui and add barbican-core there along with additional people working on barbican-ui specifically15:53
mharley[m]Creation of the group is exactly one of the other bullet points. :-) 15:53
tkajinams/barbican-core-ui/barbican-ui-core/15:53
tkajinamcf https://review.opendev.org/c/openstack/project-config/+/83431815:54
mharley[m]I can go on and provide the governance and project-config patch, but would like to ask the promoters what are the expectations towards testing.15:54
tkajinamonce you get the new group created, ask someone from infra to add barbican-core to that group15:54
tkajinamI think you don't really need a governance patch for that update15:55
dmendiza[m]Also see15:56
dmendiza[m]#link https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/castellan.config15:56
dmendiza[m]for another example15:56
anfimovirTests are gradually being added in the new version—I hope to achieve full coverage—though the functionality is currently minimal.15:56
dmendiza[m]Yeah, you probably just need the project-config patch15:56
mharley[m]OK, anfimovir, provide more details on that as the project progresses.15:58
mharley[m]Anything else, guys?15:58
anfimovirYes, no problem. 15:58
noonedeadpunkyes, there's one patch to define rules for the group.15:58
mharley[m]Do you have any example to share noonedeadpunk ?15:59
noonedeadpunkUm< I think so, give me a min15:59
noonedeadpunk#link https://review.opendev.org/c/openstack/project-config/+/98192416:00
noonedeadpunkbasically added a group that would have access to specific labels16:00
noonedeadpunkin your case it should be applicable to specific project16:00
noonedeadpunkI can help out with such patch if needed16:01
tkajinambarbican-ui shares the same acl config with barbican so you should change that also16:01
mharley[m]Thanks, noonedeadpunk.  Appreciate that.16:01
noonedeadpunkok, I then will add you as a reviewer and ping here?16:01
mharley[m]I might be part of it as a PTL, but I'm not a reviewer.16:02
noonedeadpunkwell, infra folks would want a PTL approval)16:03
noonedeadpunkfor changes like that16:03
mharley[m]I understand we need at least three people besides me as members of such a group.16:03
mharley[m]For the sake of having two reviewers for each patch.16:03
dmendiza[m]mharley: the change to project-config will need PTL approval16:03
noonedeadpunkthe group is populated manually though from the gerrit ui16:03
mharley[m]dmendiza: when I mentioned I'm not a reviewer, I was referring to the barbican-ui patches.16:04
noonedeadpunkI think infra root would add a ptl as a member manually16:04
dmendiza[m]If this is set up as a superset of barbican-core then PTL will already be there16:04
mharley[m]We are over time, guys.  Thank you all for the presence and participation.  It was great to see folks joining the meeting after several weeks.16:05
mharley[m]See you in two weeks! :-)16:05
mharley[m]#endmeeting16:05
opendevmeetMeeting ended Mon Sep 28 16:05:50 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:05
opendevmeetMinutes:        https://meetings.opendev.org/meetings/barbican/2026/barbican.2026-09-28-15.00.html16:05
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/barbican/2026/barbican.2026-09-28-15.00.txt16:05
opendevmeetLog:            https://meetings.opendev.org/meetings/barbican/2026/barbican.2026-09-28-15.00.log.html16:05
noonedeadpunkdmendiza[m]: I think it will be a plain group with ptl as only member, and then any member of the group is able to add existing barbican-core to "included" groups16:06
noonedeadpunkLike you are able to do in https://review.opendev.org/admin/groups/f8b3206a8e63ab4c37f81a1a9470dc1d893af068,members16:06
dmendiza[m]Yeah, sure, I don't have any strong opinions on how it is structured...16:07
noonedeadpunkwhat I meant that group when created is super simple, there's nothing in project-config to actually configure or populate it16:08
noonedeadpunkit all is done manually by group members after ACLs are set16:08
-opendevstatus- NOTICE: Zuul is reporting inconsistent results showing failures in Gerrit comments and in progress status in the Zuul UI. This is due to Zuul database issues that we are working to correct.19:02

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