13:30:06 #startmeeting rpm_packaging 13:30:07 Meeting started Thu May 14 13:30:06 2020 UTC and is due to finish in 60 minutes. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:30:10 ping toabctl, dirk, apevec, jpena, number80, kaslcrof, cmurphy, rha 13:30:11 The meeting name has been set to 'rpm_packaging' 13:30:14 #chair evrardjp dirk 13:30:15 Current chairs: dirk evrardjp jpena 13:30:23 #topic roll call 13:30:30 o/ 13:30:34 o/ 13:30:37 we have a pretty short agenda, please feel free to extend it at https://etherpad.opendev.org/p/openstack-rpm-packaging 13:30:40 #chair cmurphy 13:30:41 Current chairs: cmurphy dirk evrardjp jpena 13:31:17 o/ 13:31:40 seems there are a few people around 13:31:44 that's good :) 13:34:02 let's start with the agenda 13:34:07 #topic PTL situatio 13:34:09 #undo 13:34:10 Removing item from minutes: #topic PTL situatio 13:34:11 #topic PTL situation 13:34:24 evrardjp: the stage is yours 13:34:27 thank you 13:34:57 I would like to close that topic: Currently the state of rpm-packaging, in terms of governance, is "Appointment needed" 13:35:21 Who have discussed the multiple possibilities in the past 13:35:28 I would like us to come to a conclusion 13:36:19 For me, the simplest is to have a PTL. So my question is ... "Who can become the next PTL, even if not confident about being able to hold the position for the next 6 months?" 13:36:50 I nominate evrardjp as PTL 13:36:58 is the PTL-less option feasible? I mean, I've seen discussions about it for quite some time, but it's never been clear to me 13:37:08 we could be a good team to experiment with that 13:38:03 some TC/ex-TC members think it might _not be_ a good team to experiment with that, but it's something we could try to figure out 13:38:15 The problem is that we'll need to add some folks into liaisons anyway 13:38:35 which I think might be easier that committing to be PTL 13:38:36 so let's say we go for it, who is ready to be the liaisons for security/events? 13:38:42 does it? 13:38:50 dunno, it's just a feeling 13:39:43 dirk: nice maneuver :) 13:39:44 which liasons do we need? Security/events, release... 13:39:48 correct 13:40:07 It could be more, but these are the ones I foresee in the short future. 13:41:10 So I assume that nobody is willing to be PTL? 13:41:49 What's holding people up to be the PTL? 13:41:58 I'm happy to be liason... and might be a PTL for another cycle as a last resort, but we'd only be pushing the ball forward for 6 more months 13:42:15 I think that's what we are looking for. 13:42:23 evrardjp: I'm happy to be the liason for whatever 13:42:39 evrardjp: I just can't be the benevolent PTL 13:42:41 jpena: what about the TC appoints you for PTL, and we start the process of PTL-less ing 13:43:01 evrardjp: ok, let's give that a try 13:43:06 jpena: thank you! 13:43:17 thank you jpena :) 13:43:18 within 6 months we should have clearance how things will move forward. and if not we end it there 13:43:30 evrardjp: I can help with liasons etc whatever. 13:43:45 dirk: I think if you hadn't renderspec and pymod2pkg it would change things, tbh 13:43:51 to be honest we've been pretty lightweight on the openstack foundation 13:43:56 yes 13:43:58 totally 13:44:06 and that makes it a very special case 13:44:24 so its not like we're not there, we are there 13:44:29 and we're not asking for much 13:44:31 What I don't like is the fact that community has been balanced around 13:44:41 so I understand that if openstack wants to reduce scope, then I'm not in the way of that 13:44:41 exactly 13:44:47 well 13:44:50 it's not only that 13:44:53 but I think just changing for the sake of changing makes no sense imho 13:45:11 we just chose the thing where _nothing_ changes :) 13:45:22 yep 13:45:24 great!! 13:45:27 next 13:45:29 :-) 13:45:35 but you're right. 13:45:38 yeah, I am done! 13:45:50 thanks all. 13:46:16 #agreed jpena to run PTL for 6 months to figure out how PTL less works 13:46:38 nice, moving on with the agenda then 13:46:42 #topic ussuri branch 13:47:05 yesterday (?) we created stable/ussuri 13:47:18 I have started putting the plumbing in place for SUSE ci 13:47:39 Its not quite there yet, will fix this over the next few days 13:47:42 which reminds me I need to create the CI job for DO 13:47:59 any help as usual is appreciated 13:48:09 the base repos are already created 13:52:00 #info stable/ussuri branch created 13:52:17 #info SUSE and RDO CIs for stable/ussuri coming soon 13:54:42 I think that's it for this topic, let's move on 13:54:44 #topic open floor 13:56:07 nothing from my side 13:57:02 pretty silent, so I suppose nothing from the side of others:p 13:57:17 thank you everyone 13:57:29 thanks 13:57:41 let's close the meeting and run to the next one :) 13:57:46 #endmeeting