20:00:03 #startmeeting EPEL (2023-08-30) 20:00:03 Meeting started Wed Aug 30 20:00:03 2023 UTC. 20:00:03 This meeting is logged and archived in a public location. 20:00:03 The chair is tdawson. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 20:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:03 The meeting name has been set to 'epel_(2023-08-30)' 20:00:05 #meetingname epel 20:00:05 The meeting name has been set to 'epel' 20:00:06 #chair nirik tdawson pgreco carlwgeorge salimma dcavalca dherrera gotmax23 smooge 20:00:06 Current chairs: carlwgeorge dcavalca dherrera gotmax23 nirik pgreco salimma smooge tdawson 20:00:08 #topic aloha 20:00:22 .hi 20:00:23 rcallicotte: rcallicotte 'Robby Callicotte' 20:00:38 morning 20:00:39 Hi rcallicotte 20:00:43 .hello salimma 20:00:44 Morning nirik 20:00:44 michel-slm: salimma 'Michel Lind' 20:00:49 Hello michel-slm 20:00:51 .hi 20:00:52 dherrera: dherrera 'Diego Herrera' 20:00:56 Hi dherrera 20:01:07 .hi 20:01:07 Neal is on a call next to me :P 20:01:07 carlwgeorge: carlwgeorge 'Carl George' 20:01:28 michel-slm: I thought he was at the doctor 20:01:31 Hi carlwgeorge 20:01:34 that's neil, not neal 20:01:41 #AllLookSame :P 20:01:58 lol 20:01:59 Ahh ... sorry . Hi Neal 20:02:07 it's a ne{ai}l invasion! 20:02:32 tdawson: can you chair me ? the salimma nick is on the Matrix side so it's sadly unusable now 20:02:36 .hi 20:02:37 dcavalca: dcavalca 'Davide Cavalca' 20:02:46 #chair michel-slm 20:02:46 Current chairs: carlwgeorge dcavalca dherrera gotmax23 michel-slm nirik pgreco salimma smooge tdawson 20:02:55 Hi dcavalca 20:03:07 hello 20:03:14 Hello smooge 20:04:37 hey! 20:04:40 .hello ngompa 20:04:41 Son_Goku: ngompa 'Neal Gompa' 20:04:51 Hey Son_Goku 20:05:05 #topic End Of Life (EOL) 20:05:06 RHEL 7 / epel-7 will go EOL on 2024-06-30 20:05:08 CentOS Stream 8 / epel-8-next goes EOL in 2024-05-31 20:05:09 CentOS Stream 9 / epel-9-next goes EOL in 2027-05-31 20:05:30 .hi 20:05:31 jonathanspw: jonathanspw 'Jonathan Wright' 20:05:36 Hi jonathanspw 20:05:44 howdy! 20:05:45 #topic EPEL Issues https://pagure.io/epel/issues 20:05:46 https://pagure.io/epel/issues?tags=meeting&status=Open 20:05:55 Need to update that with a 'There are only 2XX installation days until EL7 goes EOL' 20:06:26 smooge: That would mean I'd have to update it each time ... hmmm ... or write a script ... 20:06:30 do we need a website with a counter? 20:06:46 IsItDeadYet.org 20:07:03 nice 20:07:19 deadbeef.com 20:07:25 276 days until CentOS Stream 8 EOL and 307 days until EL7 EOL 20:07:33 https://endoflife.date/rhel 20:08:01 https://endoflife.date/centos-stream 20:08:30 ooh nice 20:09:12 Cool. I'll add those to the agenda. 20:10:31 I marked the formalizing committee member process as a meeting item .... it doesn't mean we have to decide today, but I figured it's and issue .. anyway 20:10:39 .epel 240 20:10:40 tdawson: Issue #240: Formalizing the EPEL Steering Committee member process - epel - Pagure.io - https://pagure.io/epel/issue/240 20:11:40 Here are my list of pros and cons on "lifelong" vs "Set Time" - https://pagure.io/epel/issue/240#comment-870587 20:12:13 After writting those down, I started leaning towards the "Set Time" 20:12:14 Yeah I read through those and felt they covered them 20:12:31 Going from my time of lifelong.. I would not do it again 20:12:54 I put a +1 in the issue for set time. 20:12:57 question; how big a pool of interested people do we think there are? 20:13:15 * jonathanspw raises hand 20:13:34 nirik: I think the pool is larger than 7 ... at the present time I'm betting 9 or 10. 20:14:19 ok. just curious... since we could run into problems if people step down and there's no interested people to replace them. 20:14:29 (at least unless we had a flexable membership number) 20:14:45 could mirror what fesco does which cites basically that people don't *have* to be replaced 20:14:56 but also guides when and how replacements should happen 20:14:59 That's a possiblity. Maybe say that 7 is the maximum. 20:15:26 * carlwgeorge nods in agreement 20:16:58 in the unlikely scenario we end up with a split vote due to an even number of members, we can defer the vote until we elect or appoint another person to get to an odd number of votes 20:17:22 Ohh ... I like that wording ... I'm writting that down. 20:17:33 i think i read something about fesco having a temporary appointment process in the case of someone stepping down mid-cycle 20:17:58 carlwgeorge: yep there is one 20:18:13 https://docs.fedoraproject.org/en-US/fesco/FESCo_election_policy/#filling_vacant_seats 20:18:23 yeah, fesco uses elections, but if there's not enough people standing for election then there is a fallback appointment process. 20:18:29 I think it was used once 20:19:04 watch out, i'll appoint my dog, and proxy his votes since he can't type 20:19:10 With me going over to the "set time" ... is there anyone other than nirik that is wanting to keep it "lifelong" ? 20:19:13 *laughs* 20:19:13 and in that case I am pretty sure the person appointed was the person who got the next most votes in the last election 20:19:44 well, I am not sure I do... still pondering on it... but I will of course defer to everyone else. 20:20:23 i think just having elections will make more people be interested in running 20:20:34 We don't have to have a vote this week. I'm ok waiting another week. I just don' t want to drag the conversation out if everyone is on the same side. 20:21:10 if we consistently don't have enough people running, we could consider dropping the 7 down to 5 20:21:13 carlwgeorge: it could yeah... dunno. I guess there's always the thought of just trying and seeing and changing it if it doesn't work 20:21:39 Something that will have to be agreed upon is which current seats are the first up for election. If it's to be offset then some seats will be up for election first, other seats remaining appointed for a time. 20:22:02 well... if we have 9 people showing up to meetings and providing good input, I think it's a bit weird to only allow a smaller subset to vote on things... 20:22:03 draw straws 20:22:10 we can consistently drop down to 1 person which is an odd number and hopefully not deadlocked 20:22:16 OR if there was to be an "immediate" vote the top X in the first election could be longer term seats, with the bottom ones being a shorter initial term. 20:22:51 smooge: A committee of 1 ... always get's things done 20:23:14 jonathanspw: that's a neat idea, top 3 or 4 do a full term, bottom 3 or 4 do a half term 20:23:23 Yeah, just for the first election to start the offset. 20:23:29 as long as the number is odd to avoid deadlocks, I don't think the exact number matters much 20:23:50 well since troy is the lifetime chair he could always be the tie breaker :D 20:23:53 yeah, and i don't think we'll have issues sticking with 7 20:24:15 Here's the question about voting for committee member (as opposed to votes during out meeting) ... who get's to vote? 20:24:17 I kinda like 9 like fesco... but perhaps I am just being contrary. ;) 20:24:51 7 until EPEL7 is retired, then 9 20:25:06 we elect the last two when 7 is dead :D 20:25:39 lol 20:25:41 +1 20:25:42 tdawson: that brings us to https://pagure.io/epel/issue/242 20:25:54 jonathanspw: Aha .... someone finally brought it up. :) ... after we get the committee stuff settled, I was going to open a new issue on how long the chair stays chair. 20:25:56 ha 20:26:21 tdawson: I think after each election the newly-elected steering co. should decide on a chair amongst themselves. 20:26:37 that makes sense to me 20:26:39 thus making a chair's term (as chair) half that of a member term. 20:26:46 carlwgeorge: It might, but it might not. I think a vote for committee members is (can be) different than a vote on policy. 20:27:19 I like rotating chair, it helps spread out things, but sure... 20:27:26 does being the chair confer any practical powers/responsibilities? 20:27:39 the power of running the meeting 20:27:39 jonathanspw: I'm not against that ... I just didn't want to muddy the waters while we talked about committee members. 20:27:45 dcavalca: I don't think so, which is why letting it rotate more frequently is helpful. 20:27:56 as far as who can vote, for fesco it's fedora contributors (ie, at least one group) 20:28:06 the power of being pinged on why is XYZ broken and how can you get it fixed by yesterday 20:28:22 tdawson: oh good point. we could tack it on to fedora's elections so all fedorans can vote on the committee members. 20:28:31 I'd support mirroring who can vote in fedora elections - contributors 20:28:33 dcavalca: Two power ... 1 - like carlwgeorge said, the power to run the meeting 2 - in the event of a split vote, can give the final vote. 20:28:52 which is kinda the idea of the committee being representatives of the whole community 20:29:41 carlwgeorge: And ... that's what I'm not sure about ... how many Fedoran's care about EPEL? What if we're getting just random votes because 20:30:06 how many fedorans care about mindshare? or council? or fesco? same deal 20:30:16 * nirik nods. 20:30:32 Good point. 20:30:39 The only other thing that would make any sense would be epel-packager-sig members... but that seems pretty narrow. 20:30:52 Ya ... I think that's too narrow. 20:31:45 One good thing about piggy-backing on Fedora's elections is they already have it setup and run it. Less work for us. 20:32:06 Piggybacking on Fedora seems perfect 20:32:10 yeah, I think having the same rules as FESCo, council etc makes sense 20:32:31 dry run in case any of us want to run for other committees too ;) 20:33:42 I just saw the time, are we ok with me time-boxing this for now, and I'll write up what we discussed on the issue. 20:34:02 well, we did have it all set to run... if we had a PM to do so. ;( 20:34:23 do most people in Fedora care / have context on EPEL enough to meaningfully vote on this? 20:34:53 I think this is the crux of why we don't do elections in the first place 20:35:05 conversely, do we think there are people that care about EPEL and should have input but for whatever reason aren't involved in Fedora enough to vote? 20:35:14 dcavalca: probably a somewhat small subset. I thinka message to people to not vote if they don't have an interest in epel might be good. 20:35:38 currently not a large amount of people vote in Fedora period anymore. 20:35:53 there may be epel users/consumers that aren't in any groups in fedora that might want to vote... hard to tell 20:36:02 smooge Doesn't mean we shouldn't embrace elections as a way for community to have a say in what's going on 20:36:07 but it doesn't mean that having no elections 20:36:28 yeah jonathanspw trying to type on the phone is failing 20:36:36 :) 20:36:53 if we announce it in the epel-devel list, is that sufficient? 20:37:05 And epel-annouce 20:37:06 if you don't subscribe to that list you're likely not interested 20:37:11 ah yes, and announce 20:37:17 smooge: this was always kind of the case... though we had a nice spike during the pandemic 20:37:19 i would tie it into the fedora elections, and just do epel-devel, announce and fedora-announce 20:37:28 +1 20:37:50 based on countme metrics, i think the pool of epel consumers that don't participate in fedora is pretty big, and an election for epsco could be a good incentive for them to get more involved 20:38:17 good point 20:38:18 after that it doesn't really matter. The main goal of elections is to give ownership of decisions to the community 20:38:37 we know epel usage is huge, but epel contributors are low 20:38:58 epel users have always been... less involved than fedora ones... 20:38:59 carlwgeorge: that is a good point, and I would love to see more involvement from EPEL users 20:39:22 and this could also lead to those epel users getting more involved in other areas of fedora 20:39:49 I'm going to timebox this so we can move onto the next subject. I will put what we talked about into the issue. If someone feels I missed something, feel free to add it. 20:39:50 maybe i'm being too optimistic, but at least in my case epel is what brought me into fedora 20:40:24 Oddly enough, the next subject is about.... voting :) 20:40:30 epel also brought me here :) 20:40:56 carlwgeorge: Although, I did notice that you didn't mark yours with "meeting" ... are you ok talking about it today? 20:41:24 .epel 242 20:41:25 tdawson: Issue #242: Formalizing the EPEL Steering Committee voting process - epel - Pagure.io - https://pagure.io/epel/issue/242 20:41:36 oh i forget to tag it. but considering the time i'm fine punting it to next week if needed. 20:41:57 OK, I'm fine punting until next week as well. 20:41:57 well tag it 20:42:06 so you don't forget next week 20:42:13 of course if people have feedback to share we can talk about it, i don't have anything more to say other than what's in the issue (so far) 20:42:30 I'm going to punt to next week. 20:42:35 #topic Old Business 20:43:12 Is there any Old Business that needs to be brought up? 20:43:15 speaking of punting...college football starts up this weekend. #offtopic 20:43:15 is this where we talk about EL6 packages (and yes that is an old joke i am reusing) 20:43:29 *laughs* 20:43:38 But ... no 20:43:41 i logged into a el6 machine earlier today... 20:43:44 yelled at that customer to upgrade 20:43:55 * nirik will be starfielding this weekend. 20:44:14 nirik: roll tide 20:45:01 OK, moving onto Open Floor 20:45:12 #topic General Issues / Open Floor 20:45:27 If nobody else has anything, I have one thing for Open Floor. 20:45:42 I have some things but I can go after tdawson 20:46:08 michel-slm: I'll let you go, mine is possibly short 20:47:01 I also seem to have lost my link that I was going to point people to. 20:47:41 Oh, I found it - https://almalinux.org/blog/new-repositories-for-almalinux-os-synergy-and-testing/ 20:48:22 Oh....so about that 20:48:31 * carlwgeorge laughs 20:48:56 I think Alma's synergy repo is rather cool. It's sorta like an EPEL for EPEL. 20:49:11 I'm pushing really really really hard for us to be EPEL-first - ie avoiding the whole "if it gets in EPEL then we'll remove it from synergy" thing. I think I've about got everyone on board with this...had a quick runthrough of fedora/epel packaging processes last week showing everyone how easy it is 20:49:24 tdawson can go first - sorry, was distracted tracking some bugs 20:49:31 So the net result *should* be EPEL gets a lot more contributors/packagers directly. The "removed it if gets in EPEL" part should be kind of rare I hope. 20:49:42 awesome 20:49:47 neato!! 20:49:50 I have one person that should be submitting a package for review this week that I'll sponsor, with a few more in the works for sponsorship. 20:50:21 i'm with jonathanspw, almost everything in synergy should be in epel 20:50:47 from what i'm seeing Synergy depends on EPEL too 20:50:59 It does. installing synergy will automatically install/enable epel and crb 20:51:07 i've checked quite a few packages in there, and what bothers me is the vast majority are just fedora rebuilds with no bug filed to request an epel branch. meaning they probably didn't even try. 20:51:21 carlwgeorge: I'm working on it man :p 20:51:40 jonathanspw: I tried out the Paledron desktop they had in there ... there was a bug (some missing packages) and it was a little fuzzy on how to get that feedback to the developers. 20:52:02 i found one that had a request that the fedora maintainer declined for epel8, but said he was open to co-maintainers that could maintain an epel8 branch 20:52:13 tdawson: yep that's a problem too. We're still working on getting things re-aligned since the RH source changes. Our position is now much different than before when it was basically "complain to RHEL". 20:52:18 bugs.almalinux.org is the place though 20:52:40 Ah, thanks. 20:52:49 also if it's gonna be a short term "try something out" repo in the course of getting something into epel proper, i'm not sure why copr wasn't a better choice 20:53:07 So I guess it's worth noting, anyone that has feedback about this repo please please please bring it to me if you don't know where to send it/etc. The goal is not to compete with EPEL at all. 20:53:23 carlwgeorge: preaching to the choir 20:53:46 jonathanspw: Sure thing. Well, I'll file a bug for those packages, but I'll bring things to you then. 20:53:47 i suspected as much 20:53:55 > The Synergy repository is designed for any possible package that is not present in RHEL or EPEL yet, but has been requested by a member of the AlmaLinux community, for the community. While we do encourage and welcome contributions, as soon as the package appears to be in EPEL it will be removed from the Synergy repository. 20:54:23 * michel-slm needs to bring up his items since they need votes 20:54:30 tdawson: thanks. we're still working on a lot of structuring. Soon we should be starting up "ALESCo" inspired by FESCo to help steer the direction of what we do from a non-RH perspective and it will be overseeing what goes into synergy 20:54:35 michel-slm: Oh, OK. Go for it. 20:54:42 i even had to let them know on that last part that there was a duplicate to get it removed from synergy 20:55:01 jonathanspw: my feedback here would to have some kind of policy on the Alma side to strive to keep Synergy as small as possible and actively get packages into EPEL/CentOS/whatever is the best upstream as soon as possible 20:55:02 so last week we talked about incompatible upgrades for zeek and also retiring the old django from EPEL 20:55:05 any objections? 20:55:13 none from me 20:55:15 the mailing list seems quiet 20:55:16 none here 20:55:25 dewit.gif 20:55:26 michel-slm: Oh, that's right. No objections from me. 20:55:38 +1 20:55:44 +1 to both 20:55:52 neat. and the other thing is a quick announcement that Son_Goku and I are doing a push to finalize getting mailman3 in EPEL 9 20:55:54 sure :) 20:56:05 nice :D 20:56:14 Ya!! 20:56:14 +1 20:56:15 looking ok apart from some single-person dependencies 20:56:30 yeah... :/ 20:56:53 https://bugzilla.redhat.com/show_bug.cgi?id=2236249 20:57:09 we'll get nirik to help ping that so we don't have to wait for the full process :) 20:57:12 hurray! 20:57:48 yeah, happy to help... then comes the fun part... standing up a staging instance, moving our stuff into it and then prod... 20:58:54 let's dew it 20:58:55 right, then we find out if any of the packages are buggy :P 20:59:03 :) 20:59:07 I sent nirik the list we can try to expedite 20:59:10 then after this I can get back to the _other_ infra apps that need to be packaged for epel9 20:59:21 many many thanks on working on this. I know it's been a long road 20:59:27 and carlwgeorge already independently pushed out one of the package we need, so thanks :) 20:59:32 Son_Goku: pagure. ;) 20:59:39 which one was that 20:59:39 yes! 21:00:10 carlwgeorge: we need falcon, it needs mujson which you just built, and also two packages we're stuck on but I've filed requests 21:00:22 stuck on aiofiles and cbor2 21:00:22 yeah i'm still working on falcon, it's messy 21:00:30 oh I can build aiofiles 21:00:41 i filed epel9 requests for aiofiles and cbor2 21:00:53 drats, I'll merge my requests 21:01:52 longer term I am going to propose we make Python packages comaintained by python sig, because this is painful :) 21:01:56 anyway... we're out of time 21:02:02 It looks like our time is up. Thank you all for the good discussions today. This re-working the committee process is being alot less painful than I was expecting. And thank you all for all the work you do for EPEL and it's community. 21:02:14 Talk to ya'll next week, if not sooner. 21:02:27 I know its late but I just wanted to say thanks to tdawson for helping me with my rubygem issue on monday. 21:02:33 bye all 21:02:35 u 21:02:37 thanks tdawson and everyone. 21:02:38 y'all have a good one 21:02:38 in the past python sig had 0 interest in maintaining/touching/looking at EPEL packages 21:02:39 rcallicotte: You are very welcome. 21:02:39 thx tdawson :) 21:02:42 #endmeeting