20:00:11 #startmeeting EPEL (2022-08-10) 20:00:11 Meeting started Wed Aug 10 20:00:11 2022 UTC. 20:00:11 This meeting is logged and archived in a public location. 20:00:11 The chair is tdawson. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 20:00:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:11 The meeting name has been set to 'epel_(2022-08-10)' 20:00:24 .hi 20:00:25 rcallicotte: rcallicotte 'Robby Callicotte' 20:00:26 #meetingname epel 20:00:26 The meeting name has been set to 'epel' 20:00:26 .hi 20:00:26 #chair nirik tdawson pgreco carlwgeorge salimma dcavalca dherrera 20:00:26 Current chairs: carlwgeorge dcavalca dherrera nirik pgreco salimma tdawson 20:00:26 #topic aloha 20:00:28 jonathanspw: jonathanspw 'Jonathan Wright' 20:00:34 Hi rcallicotte 20:00:37 .hi 20:00:38 pgreco: pgreco 'Pablo Sebastian Greco' 20:00:39 Hi jonathanspw 20:00:45 Hi pgreco 20:01:00 .hi 20:01:01 orionp: Sorry, but user 'orionp' does not exist 20:01:08 Hi orionp 20:01:11 .hi 20:01:12 salimma: salimma 'Michel Alexandre Salim' 20:01:13 morning everyone 20:01:19 Hi salimma 20:01:23 Good morning nirik 20:01:26 .hi orion 20:01:27 orionp: Sorry, but user 'orionp' does not exist 20:01:46 orionp: do ".hi orionp: I bet you really do exist ... but you can be here even if you don't 20:01:55 .hi 20:01:56 dherrera: dherrera 'Diego Herrera' 20:02:00 zodbot acting up? 20:02:08 Hi dherrera 20:02:08 irc nick != fas name 20:02:20 yeah just pass your fas name as an arg 20:02:24 isn't that for .hello? 20:02:34 .hi 20:02:34 one of them lol 20:02:34 carlwgeorge: carlwgeorge 'Carl George' 20:02:42 .hello orion 20:02:42 Hi carlwgeorge 20:02:42 orionp: orion 'Orion Poplawski' 20:04:43 .hellomynameis gotmax23 20:04:44 gotmax[m]: gotmax23 'Maxwell G' 20:05:06 #topic EPEL Issues https://pagure.io/epel/issues 20:05:08 https://pagure.io/epel/issues?tags=meeting&status=Open 20:05:32 We still have the retiring packages issue there 20:05:41 .epel 39 20:05:43 tdawson: Issue #39: Retiring EPEL Packages (End of lifing CEPH in EL7 and process improvement) - epel - Pagure.io - https://pagure.io/epel/issue/39 20:06:04 Thanks to gotmax[m] for sending the email. 20:06:42 Last week our discussion basically ended with needing something similar to Fedora's Orphaning 20:06:46 #link https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/FUAG6FG7DLSIGP2IUN7YAMEMIODE6AKR/ 20:07:02 Which is why he sent the email. 20:07:34 nirik was the only one who chimed in. Does anybody else have thoughts here? 20:07:45 I've read and thought about that several times, and I don't have any ideas other than nirik's ... which involves releng doing a bunch of work. 20:08:21 I guess the one thing that we have to keep in mind is that making it harder to orphan or retire packages incentivizes people to keep unmaintained packages. 20:08:22 yeah, dunno. was hoping someone else would come up with something. ;) 20:08:43 What does releng have to do here? 20:09:01 sure, but also there's likely a lot of nonresponsive people maintaining packages, so not sure it changes much there. 20:09:35 releng could (in theory) create something similar to Fedora's Orphan system. 20:10:15 My point was that creating an issue tracker and retiring packages doesn't require releng 20:10:29 That's true. 20:10:29 Anybody can do the former and any provenpackager can do the latter 20:10:40 * nirik nods. 20:10:48 less on releng the better probibly 20:10:51 until we can easily change the EPEL bz assignee (or even better, have it per branch) to match reality, it's hard to even know who is the actual epel maintainer 20:10:58 I think there are a lot of folks that fire off a few epel builds, then disappear for a couple years. 20:10:58 short of just basing it on who makes bodhi updates 20:11:29 I opened https://pagure.io/pagure-dist-git/issue/153 20:11:42 and yeah, there's that too, people who just build EPEL then run 20:11:44 To allow any admin or admin group member to set the bugzilla assignee 20:12:04 salimma: bodhi would be a really good place to base the activity on 20:12:20 gotmax[m]: Ya!! ... cuz that's frustrating when I'm the only active admin, but I can't set the bugzilla to myself. 20:13:00 gotmax[m]: thanks for that. 20:13:05 pagure development is a bit dead these days, but it's only a couple lines that would need to be written/changed 20:13:14 (although I am unsure who or when that might get worked on) 20:13:26 the migration from pkgdb to pagure kinda wiped out the idea of per-branch maintainers 20:13:40 gotmax, add me to the chorus of thanks for stepping up to file that bug 20:13:52 well, really the 'stream branches' that added about then did. 20:13:56 Well, filing the bug is the easy part... 20:14:32 if someone can do a PR it would be even nicer. ;) 20:14:55 what's our minimum viable policy here? write down that if a maintainer isn't interested in epel bug reports, they can reassign the bug to a specific assign for people to browse and help where they can? 20:15:16 Hi! Late again, sorry :-( 20:15:27 Hi rsc 20:15:35 somehow I feel like piling on more EPEL specific policies will just annoy Fedora maintainers even more 20:15:52 (by Fedora I mean Fedora maintainers not interested in EPEL) 20:16:12 in this case it would be an escape hatch for those that don't want to deal with epel bugs for whatever reason 20:16:34 I somewhat agree in generall, but the EPEL policies regarding retirement are actually more lax than Fedora. 20:16:40 sometimes maintainers don't remember who volunteered to handle the epel branch, or the maintainer that volunteered later removed themselves 20:17:28 in some cases the fedora maintainer might want to take it back... in others they don't want it at all 20:18:24 how hard is it to undo retired epel branches? 20:18:41 So ... let's say we do gotmax[m]'s idea, a bugzilla tracker that people put a bug on that they want to "orphan" a package. If we set that up ... we could look at it once a month / week and give a summary. 20:19:25 I was thinking a Pagure repository, but I guess Bugzilla is fine 20:19:29 carlwgeorge: It's as simple as creating a releng ticket requesting it be un-retired .... oh ... you mean for releng. :) 20:19:57 https://docs.pagure.org/releng/sop_unretire.html 20:20:32 gotmax[m]: So they would be pagure issues? ... that might work. probrubly easier once it's setup. 20:21:17 gotmax[m]: You could also have a nice README at the beginning of the pagure repo ... so ya ... that does sound good. 20:23:26 gotmax[m]: Now that I understand what is going on in your head ... should we continue the conversation here, or move it back to the email? 20:23:28 * nirik nods 20:24:31 Unless anyone has anything else, I'm going to move this back to the email ... and I'll even participate this time. :) 20:24:52 +1 20:25:02 OK, moving on. 20:25:09 #topic Old Business 20:25:30 Sorry, I got pulled away for a minute 20:26:11 gotmax[m]: Not a problem. Are you ok with us moving it back to email, and I'll actually participate this time. 20:26:25 Sure 20:26:45 Michel Alexandre Salim 🎩: Can you give me privs to create a repo under the epel namespace? 20:26:54 gotmax (He/Him): let me see 20:27:30 For old business, I've only got being able to add epel-packaging-sig as the bugzilla default ... which I know we finished that up last week. 20:27:44 trying to figure out how to edit it. because there's only one repo inside it, trying to go to epel... just take me back to that repo 20:27:45 Do we really not have any other old business, or did I miss something. 20:28:03 I don't think so 20:28:04 if we brought up the epel survey last week, i guess it's old business that it's open now 20:28:18 if we haven't brought it up yet i can save it for open floor 20:28:19 Off in the distance ... I can hear smooge say " .... epel 5 .... it's really old business ..." 20:28:45 Are you still collecting responses? 20:28:50 gotmax (He/Him): want to just try and see what breaks? 20:28:54 Oh, I think we did talk about it. carlwgeorge go for it. 20:29:37 fedora is running a survey of epel users and contributors. it launched at nest and will be open till the end of the month. https://tinyurl.com/epelsurvey2022 20:30:01 #info fedora is running a survey of epel users and contributors. it launched at nest and will be open till the end of the month. https://tinyurl.com/epelsurvey2022 20:30:15 :) 20:30:22 good call 20:30:40 Michel Alexandre Salim 🎩: Try adding me under https://pagure.io/group/epel 20:31:21 gotmax (He/Him): aha, thanks. it's so not obvious how to get there 20:31:22 5 minute break to complete the survey... 20:31:27 :D 20:31:36 :) 20:31:47 #info fedora is running a survey of epel users and contributors. it launched at nest and will be open till the end of the month. https://tinyurl.com/epelsurvey2022 20:32:14 Did you mean to #info it a second time? 20:32:14 gotmax (He/Him): added 20:32:23 Hm ... I thought zotbot told you if something got set to info ... I guess we'll assume it's there ... and now double. 20:32:40 You want me to undo it? 20:32:47 gotmax[m]: No ... it's fine. 20:33:13 Anyway ... after everyone's done with the survey ... did we have any other old business? 20:34:20 #topic EPEL-7 20:34:22 CentOS 7 will go EOL on 2024-06-30 20:35:30 The only epel7 thing I have is that I fixed a epel7 package with a CVE ... but that's not really anything for the meeting ... just the only epel7 thing I've seen this past week. 20:36:07 Anything else for epel7? Or did I not give enough time for the survey. 20:37:01 #topic EPEL-8 20:37:02 CentOS Stream 8 goes EOL in 2024-05-31 20:37:06 remember the survey is open till the end of the month, no one has to do it this second :D 20:37:26 Yep 20:37:35 Anything for epel8? 20:38:03 There was some discussion about the default modules issue on centos-devel 20:38:08 Turns out they are aware about it 20:38:32 But that doesn't change the fact that we're still blocked on issues in MBS 20:38:40 Yep ... sorta drives me nuts 20:39:12 I don't want to go down that rabbit hole, but modularity did not turn out the way it was originally planned. 20:39:31 * gotmax[m] has to walk out, but I should be able to pick up on my phone 20:39:39 Anyway ... anything non-modular for epel8? 20:40:10 #topic EPEL-9 20:40:11 CentOS Stream 9 goes EOL in 2027-05-31 20:40:29 oh that reminds me, the overlapping nginx modules got retired from epel8-modular 20:40:45 carlwgeorge: Ah ... cool. 20:41:01 but one came back I think... 20:41:09 also most of the uninstallable nextcloud modules, but a new one got added so i reopened that releng issue to get to removed as well. still not sure how it got built because i disabled the epel8 stream expansion for it. 20:41:22 oh no, that was nextcloud 20:41:29 yeah 20:41:44 yeah nginx and nextcloud, two n packages had open issues at the same time 20:42:07 for epel9, i did a rebuild this morning of bloaty due to an unannounced re2 soname bump 20:42:22 Those blasted packages that start with n 20:42:24 dherrera noticed it and i used my proven packager to do the build 20:43:14 Talking of packages ... all the updated kde packages for epel8-next and epel9-next are in stable, including all the bugfixes ... so if you are having bugs on those, let me know. 20:43:25 I should actually put that in an email instead of hear. 20:43:37 looks like lcts did the nextcloud 21 build... 20:43:56 It doesn't sound like we have any epel9 stuff ... and there are some open-floor stuff ... so I'll move to there. 20:44:04 #topic General Issues / Open Floor 20:44:38 Next week, carlwgeorge and I will not be available for the meeting due to the CentOS Dojo 20:44:57 Does someone want to run the meeting? Or do people want to cancel for a week? 20:44:58 I may also not be around 20:45:37 I'm ok with canceling one week 20:45:44 I created https://pagure.io/epel/package-orphan-requests. I guess I will create an issue template and README later. 20:45:51 yeah, seems like the right thing to do 20:45:56 Note sure if there's anything else we want to discuss 20:46:01 about thatt 20:46:07 though I'd like to join you guys for the dojo 20:46:19 will there be a live-stream? 20:46:36 I think it will be live streamed ... but it definatly wil also be live. 20:47:21 pgreco: Will you be there in Boston? 20:48:27 tdawson: wanted to be, was planning on doing, not sure if I'll be able to 20:48:33 *going 20:48:56 So, different subject, and this comes from Matt's "State of Fedora" talk at Nest. What do we think about moving various things to the Fedora Discord? 20:49:00 seeing people in person again... crazy concept. ;) 20:49:13 pgreco: If you do make it, it would be great to physically see you. 20:49:30 tdawson: yeah!, I'll ping you if I end up going 20:49:35 Cool 20:49:39 depends on the thing i guess, but generally i'm in favor (the discord idea) 20:49:48 tdawson: if there is an IRC bridge... 20:49:56 I'm not saying I want to move to Discord ... I just don't know how others feel about it. 20:50:01 oh wait i think i'm confusing discord and discourse 20:50:19 Fedora has a discord? 20:50:22 oh lol 20:50:25 *laughs* ... is there a Discord / IRC bridge? 20:50:34 matterbridge can do it 20:50:36 tdawson: do you mean discord or discourse? 20:50:51 tdawson: the bridge can be done, don't know if it is for fedora 20:51:28 Pine64 bridges Discord, Telegram, and Matrix... tbh it just makes it a mess, the messages end up being tagged by where they come from 20:51:36 I am pretty sure mattdm was talking about discourse... ie, discussion.fedoraproject.org 20:52:24 https://discussion.fedoraproject.org/ 20:52:41 Ha ... well ... you can see how much I use it. :) 20:53:06 I'm happy to try, but I'm not sure how well it will work... 20:53:15 carlwgeorge: so I guess you and Troy cancel each other :) 20:53:16 does the chatbot post meeting info there? 20:53:43 I've been trying to go there and read things frequently, but it's just a lot harder than email thats pushed to me and in with all the other things. 20:54:00 Looks like the docs folks drop their meeting info there 20:54:27 fun fact, it looks like this channel is already bridged to fedora's discord 20:54:29 there's a way to get discourse to email you, and treat it as a mailing list, but from what I hear it's like using IRC when most people in the room are on Matrix -- you end up missing some features 20:54:49 hmm 20:54:51 discord is the non free thingie... it's not official. ;) 20:55:00 I quite like Discourse except I'm apparently a graybeard who likes email threading, and Discourse doesn't do that 20:55:13 salimma: yeah. I use that too... it's... ok. 20:55:17 yeah I don't like that aspect of discord 20:55:33 the non-free** 20:56:04 I also prefer email threads in my fancy kmail client 20:56:14 carlwgeorge: there is a mirror, but you can't chat from there 20:56:46 all the old folks have built up email filtering and client setups they like, so they prefer email. People who haven't setup all that probibly prefer discourse... 20:57:16 So ... it's sounding like most of us prefer email ... though several are on Fedora Discussion 20:58:24 I was mainly curious ... it sounds like there's no rush for us to move anything / everything over there. 20:59:01 Anything else before we close the meeting? 20:59:27 nothing from me 20:59:39 see you guys in 2 weeks! 20:59:54 Thank you all for coming and for the good discussion. 21:00:04 thanks everyone. 21:00:05 And thank you all for all your work for the EPEL community. 21:00:19 thanks! 21:00:20 Talk to ya'll in two weeks, unless I physically see you ... then I'll talk to you then. 21:00:28 #endmeeting