13:31:38 #startmeeting rpm_packaging 13:31:38 ping toabctl, dirk, apevec, jpena, number80, kaslcrof, rha, hberaud, sboyron 13:31:39 Meeting started Thu Jan 21 13:31:38 2021 UTC and is due to finish in 60 minutes. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:31:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:31:42 The meeting name has been set to 'rpm_packaging' 13:31:43 chair sboyron 13:31:46 #topic roll call 13:31:59 Remember to add any last-minute item to the agenda at https://etherpad.opendev.org/p/openstack-rpm-packaging 13:33:01 o/ 13:33:30 #chair sboyron hberaud 13:33:31 Current chairs: hberaud jpena sboyron 13:37:12 we have a short agenda today, let's go for it 13:37:15 #topic open floor 13:37:19 Do we have anything to discuss? 13:37:24 Yes 13:37:39 this one => http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019842.html 13:37:50 What do you think about this? 13:39:09 oh, I missed that one 13:39:12 * jpena reads 13:41:43 I would argue that the "independent" is the less disruptive choice 13:42:12 I think we should only remove our deliverables from wallaby on 13:42:34 previously we were an official project, so keeping it in the previous releases makes sense 13:42:56 so it would be option 2), with a caveat 13:43:08 the problem is between openstack/governance and openstack/release only remove them will not fix the issue 13:44:15 they will stay as inconsistent deliverables until they aren't ignored by release with openstack/governance keyword 13:45:01 Maybe the solution is to add more status to openstack/governance 13:45:27 But I wanted to discuss with you first 13:45:55 I think I'm missing something 13:46:55 so the issue is some coordination between the governance and release repos? 13:46:59 on openstack/release we periodically execute some checks to detect inconsistences between governance info and our deliverables on openstack/Release 13:47:43 and rpm-packaging projects appear as always leaded by the coordinated releases 13:48:10 ok, and the only way as of now to skip that check is to show up as "abandoned"? 13:48:21 however rpm-packaging by switching to the SIG governance model doesn't appear in the list of coordinated projects 13:49:46 unfortunatelly the SIG model lack of some details concerning this kind of scenario 13:50:24 and on the release side our checks fails 13:50:31 it's not a big deal 13:50:59 if we moved to independent for the time being, and removed the wallaby releases, would that be ok? 13:51:06 or would it complain about stable releases? 13:52:41 but if for the available solutions are 1) remove these project but the inconsistent will continue until the governance isn't up-to-date too and it will provide you a status "abandonned" that could mislead lot of people, in other words this is a grey area 2) move to independent to avoid to mislead user but you will appear as indpendent since a while 13:53:23 yes, moving to independent sounds better 13:53:26 I'm not fully sure but I think we could move only wallaby 13:53:41 it's just rpm-packaging, I guess 13:53:45 yes 13:54:01 TBH it could be worth to raise this point to the governance 13:54:08 to allow us to think about that 13:54:13 yes 13:54:42 I think so, this seems to be an issue on governance/release side 13:55:16 I don't expect we will stay the only ones to follow this scenario 13:55:20 This change seems not well thinked and we should discuss it with gouv 13:55:29 sure, that's the point 13:55:52 ok I'll add the TC to the discussion 13:55:59 (on the ML thread) 13:56:10 great 13:56:30 +1 13:56:40 I'll bring our current discussion to the next release meeting 13:56:48 #action hberaud to raise the governance/release topic to the TC 13:57:00 That's all for me 13:57:07 Thanks for your attention 13:58:32 hberaud, thanks for this point 13:59:26 thanks hberaud 13:59:34 anything else? 14:04:25 let's close then 14:04:27 #endmeeting