20:00:26 #startmeeting EPEL (2021-08-04) 20:00:26 Meeting started Wed Aug 4 20:00:26 2021 UTC. 20:00:26 This meeting is logged and archived in a public location. 20:00:26 The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:26 The meeting name has been set to 'epel_(2021-08-04)' 20:00:26 #meetingname epel 20:00:26 The meeting name has been set to 'epel' 20:00:26 #chair nirik tdawson bstinson pgreco carlwgeorge michel dcavalca 20:00:26 Current chairs: bstinson carlwgeorge dcavalca michel nirik pgreco tdawson 20:00:26 #topic aloha 20:00:33 hello! 20:00:36 morning 20:00:44 Hi pgreco 20:00:46 Hi nirik 20:00:56 hey tdawson 20:01:12 .hi 20:01:13 dcavalca: dcavalca 'Davide Cavalca' 20:01:18 Hi dcavalca 20:01:47 .hi 20:01:48 carlwgeorge: carlwgeorge 'Carl George' 20:01:55 Hi carlwgeorge 20:03:13 We've got most everyone already ... does anyone know if michel is going to make it? 20:04:02 he was at another meeting earlier today but he's still on parental leave 20:04:38 Ah, ok. Well, we'll see if he makes it. 20:05:12 That came out wrong ... I meant, we'll start and if he makes it, great, if not, that's ok too. 20:05:21 #topic Old Business 20:05:35 Let's start with the SIG 20:05:43 Any news that needs to come up? 20:06:25 I was wondering if the SIG is rolling along now, and do we need to keep bringing it up in the meeting each week? 20:07:01 Or maybe give it a Topic, similar to epel-7 and 8 20:07:22 a topic seems reasonable 20:07:46 fwiw my only update is that I've filed a few more tickets to get stuff branched 20:08:21 yeah, a topic for anything that has come up would be nice. 20:08:49 OK, starting next week I'll add it as a topic, so we can just address anything that comes up. 20:09:36 OK, I'm going to move on to -next, cuz I know there is news there. 20:09:50 Where are we at with epel-next (specifically 9) 20:10:27 c9s is mirrored into fedora infra 20:10:38 Ya!! 20:10:47 that will allow us to set up the build target in koji 20:11:02 awesome 20:11:03 Cool 20:11:07 * nirik nods 20:11:09 thanks to nirik 20:11:47 I know this week is flock/nest, so I don't expect things to be done this week, but how long do we think it will take to setup the targets? 20:12:03 Thank you nirik !! 20:12:14 no idea 20:12:27 probibly pretty easy to do next week... 20:12:38 here is my running doc of epel9-next tasks https://hackmd.io/@carlwgeorge/BJV_Rez6O 20:13:25 epel9 key setup is the big unknown i think, as we didn't have to do that for epel8-next 20:13:49 is epel9 signing depending on c9s signing? 20:13:51 Oh ya 20:14:00 dcavalca: nope, independent 20:14:03 it shouldn't be hard... 20:14:08 just needs creating. 20:15:05 that's all i got for epel-next 20:15:38 Great news. Thank you both carlwgeorge and nirik for your work on that. 20:16:15 So, last week we voted about the default bodhi time ... but I forgot to task anyone with actually changing it. 20:16:35 yeah, I wondered about that... but I never got around to asking. 20:17:00 Has anyone changed it yet? And if not, do we have a volunteer to change it? 20:17:14 no one has, and I can do it. it's just an ansible repo change 20:17:23 roles/bodhi2/base/templates/production.ini.j2:fedora_epel.mandatory_days_in_testing = 14 20:17:23 roles/bodhi2/base/templates/production.ini.j2:fedora_epel_modular.mandatory_days_in_testing = 14 20:17:38 nirik: Thank you. 20:18:48 moving on to documentation ... I haven't heard back from Petr, so next week I'm going to start following Adam's instructions and get things started. 20:19:50 Hopefully by the end of next week I'll have a sceleton setup, and instructions on how to do things, then we can all help as we have time. 20:19:51 i did it here for epel-next https://pagure.io/fedora-infra/ansible/pull-request/680, but it doesn't seem to have taken effect yet 20:21:37 Oh, speaking of bodhi times for epel-next, I was going to try to look at how much interaction / testing things were getting ... seems my script doesn't work anymore, so it will take me more time. 20:22:18 the most recent epel8-next update still did the 0 days thing, so i'm assuming that while merged that playbook hasn't been run in prod yet 20:23:37 I'm pushing the 14->7 days thing now, so re-running playbooks along with that 20:23:47 Cool 20:23:50 nice 20:24:14 I'll have some updates next week I believe, so we'll see how it does. 20:24:26 I think that's it for old business. 20:24:44 #topic EPEL-7 20:25:00 Did we have anything for EPEL 7 ? 20:26:06 #topic EPEL-8 20:26:16 Anything for epel8? 20:27:05 #topic EPEL-Packaging-SIG 20:27:21 Ha ... added to the agenda already :) 20:27:34 Actually, I remembered something that came up about the SIG 20:27:56 I believe it was nirik and Eighth_Doctor were asking about if certain packages should be maintained by the SIG 20:28:10 I think it was epel-release and/or epel-macros 20:28:19 yeah 20:28:27 I think that was nirik 20:28:42 who is the current responsible for those? 20:28:45 actually it was someone else... 20:28:58 asking if the sig should maintain it when I didn't merge their PR 20:29:00 Does that sound like a good idea? Or do we think too many fingers will make a mess of those? 20:29:06 but I was out on PTO and missed it. 20:29:37 if the responsible is clear, I'd rather leave it there, and maybe a "second in command" 20:29:49 and not too many people, like tdawson said 20:29:53 tdawson: case in point: I merged that PR for epel8, but purposefully didn't push a build because I was waiting for another PR... but then the person that made the PR did a build and update. ;( 20:30:13 not a big deal, but... 20:30:46 nirik So you think keeping it to a smaller group is how we should keep it? 20:30:47 so, perhaps it would be good to have the sig help review pr's and such, but we coordinate who does builds? 20:30:57 either way... 20:31:43 I'm all for more people doing reviews 20:32:18 I'm ok either way. Both of them have been updated when they need to be, so I don't know if we need to change things, but more eyes reviewing isn't bad either. 20:32:37 we could also discuss on list and see if anyone has stronger thoughts on it. 20:32:46 or just keep it as is for now and change later. 20:33:25 I'm ok leaving it as things are, unless someone feels strongly about it. 20:34:02 Currently anyone can signup to watch the packages, and do reviews. 20:34:37 sure, true. 20:35:20 So, let's leave it as it is. If you want to watch and review - https://src.fedoraproject.org/rpms/epel-release/ 20:36:08 That was the only SIG thing I had. 20:36:15 #topic General Issues / Open Floor 20:36:59 Looks like we have at least 3 EPEL talks happening in Flock/Nest 20:37:48 That should be good ... although all of them are on Saterday 20:38:35 Anything else for Open Floor? 20:38:48 looks like we have a short one today 20:39:01 I'm good with that. :) 20:39:15 yeap 20:39:34 i poked the epel steering committee badge ticket, as i don't know what is supposed to happen next 20:39:40 https://pagure.io/fedora-badges/issue/829 20:40:40 I don't know either, I've never created a badge. 20:41:37 I don't know how they'll change the badge, but out of the two prototypes, I like the ant head one best. :) 20:42:10 yeah the ant heads are good 20:42:46 Well, I'm going to give you 15 minutes back. Thanks to everyone for coming, as well as thanks for all the work ya'll put in. 20:42:57 thanks tdawson \ 20:43:02 Talk to you next week, or at Flock/Next. 20:43:10 #endmeeting