20:15:15 #startmeeting EPEL (2021-03-17) 20:15:15 Meeting started Wed Mar 17 20:15:15 2021 UTC. 20:15:15 This meeting is logged and archived in a public location. 20:15:15 The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:15:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:15:15 The meeting name has been set to 'epel_(2021-03-17)' 20:15:16 #meetingname epel 20:15:16 The meeting name has been set to 'epel' 20:15:17 #chair nirik tdawson bstinson pgreco carlwgeorge michel_slm 20:15:17 Current chairs: bstinson carlwgeorge michel_slm nirik pgreco tdawson 20:15:19 #topic aloha 20:15:26 o/ 20:15:30 hello 20:15:31 Hi cyberpear 20:15:36 Hi dcavalca 20:15:43 ohh, that's today ;) 20:16:11 pgreco: Yep ... and I'm 15 minutes late too 20:16:19 But thanks to dcavalca, I'm not 60 minutes late. 20:16:47 my previous meeting was 15 minutes over, so it worked out! 20:16:48 I've been having server problems all day, so if I drop, you'll know why 20:17:49 .hello robert 20:17:50 rsc: robert 'Robert Scheck' 20:18:06 Hi rsc 20:18:07 morning 20:18:12 Hi nirik 20:19:11 * carlwgeorge waves 20:19:19 Hi carlwgeorge 20:19:49 * carlwgeorge needs to fix his calendar 20:19:53 #topic Old Business 20:20:08 Yep, I'm fixing my calendar right now. 20:20:16 * nirik also 20:20:20 Old business of the new time. 20:20:24 got the link handy for the fedocal thing? 20:20:41 I just want to double check. This time (meaning starting 20 minutes ago) is what we agreed to. Correct? 20:20:51 oh, I did, but cleverly it only starts next week 20:21:01 hello 20:21:03 tdawson: yep. thats my understanding 20:21:06 tdawson: yeah, that was my understanding 20:21:09 Hi smooge 20:21:55 OK, then we're good. Sorry for starting late. Even though I was the one that created the email and changed things, my mind was thinking it started next hour. 20:22:37 Then lets move to the EPEL-Packaging-SIG 20:23:01 The code is in, and we were waiting for a release of the tool. Has that happened yet? 20:23:21 Meaning the "collaborator requesting branches patch" 20:23:48 not sure, but I think not yet 20:24:16 I filed a few more tickets to get packages branched in the meantime 20:24:25 python-neovim: https://bugzilla.redhat.com/show_bug.cgi?id=1940120 20:24:33 swtpm: https://bugzilla.redhat.com/show_bug.cgi?id=1939674 20:24:41 libtpms: https://bugzilla.redhat.com/show_bug.cgi?id=1939670 20:25:59 OK, sounds good. I guess we can wait till next week to see if the patch gets deployed. 20:26:06 Anything else before we move on? 20:27:02 epel8-next - carlwgeorge, it's only been a few days, but has there been any progress? 20:27:43 got a meeting scheduled with mboddu tomorrow to catch up and hopefully merge my prs to fedpkg and fedscm-admin 20:27:53 cool 20:28:21 if anyone wants to attend let me know and i'll add you to the invite (thinking of nirik probably) 20:28:38 sure, feel free to add me. Not sure if I can make it, but can try 20:28:46 that's what optional is for :D 20:29:19 no make it mandatory for nirik 20:29:32 mandatory for smooge, got it 20:29:56 sure 20:30:02 but yeah no actual progress, we can move on, unless we want to bikeshed about epel-next vs epel-stream 20:30:10 the meetings will continue until morale improves 20:30:39 Moving on ... documentation changes 20:31:55 I sent an email to Peter Bokoc. He said the easiest way to move everything from the wiki to Fedora Docs would be to let him do the conversion. 20:32:04 yay 20:32:23 He also apologized, cuz evidently smooge had asked him before and he got sidetracked. 20:32:45 cool 20:33:17 that's good news 20:33:27 He won't be able to start until sometime in April, due to F34 and Stream documentation. So I'll have to remind him, and give him some pointers. 20:34:03 It's another month out but ... that's ok, we've already had this on our agenda for over a month. :) 20:35:26 I think that's it for documentation, unless anyone has anything else. 20:36:29 Last week we talked about "epel for eln", and I think most of you saw my email and proposal for "eln extra" .... does anyone want to discuss that more here, or are we ok putting that all on the ELN SIG? 20:37:26 I like your proposal the best so far... but still we need to make sure not to sign people up for work they don't want to do. ;) (and let them do work they do want to do) 20:37:36 Oddly enough, that doesn't really change too many of the people who will work on it, but it shifts it to a different meeting. :) 20:37:52 I like your proposal as well 20:38:19 nirik: I agree with you ... oh, and I just realized I didn't reply to the email. But I think the "eln extra" packages do not have to translate to EPEL. 20:38:38 It can of course, but it shouldn't be assumed that it does. 20:38:54 tdawson: yeah, I think leaving that up to the package maintainer is the right call 20:39:06 though we should document how to leverage them for that, if one wants to 20:39:19 good idea. 20:39:25 docs are good. 20:39:32 which list was this email on 20:39:50 carlwgeorge: devel 20:39:55 I thought it was fedora-devel ... but the subject is something like "First ELN Meeting" 20:39:59 tdawson: one question I'd had is how we'd record who is maintaining a specific package in "eln extra" 20:40:01 ah, i was looking on epel-devel 20:40:12 like, sometimes that'll be the epel maintainer, but not always 20:40:39 How does eln do it? 20:41:00 nirik: that's a very good question, I actually don't know 20:41:03 ELN has a bot that does it. It also doesn't branch, it does it straight from rawhide. 20:41:19 so, perhaps the bot could be extended. ;) 20:41:32 one of the things I liked about this proposal was no branches. :) 20:41:58 yeah I like a lot that it encourages fixing things in rawhide 20:42:04 which is going to be beneficial in general 20:42:10 I don't think the bot has to be extended much, just give it another list to look at. 20:43:25 * nirik nods 20:43:36 I don't want to spend all the meeting time eplaining the details of how it works, but we currently generate a list of "these are ELN packages", and it takes care of them. 20:43:46 Sorry, getting side tracked by ... myself. :) 20:43:47 just make sure the ELN extras can't see the "unpublished -devel packages" to match the future RHEL release :P 20:43:56 Ha! 20:44:04 :) 20:44:08 lol 20:44:21 sick burn :P 20:44:33 nirik: tdawson: have a link to the bot? 20:45:07 cyberpear: i don't think i can say much, but i expect that situation to be "better" in 9, for some definition of better 20:45:12 * nirik has no idea where it is or who maintains it. ;) 20:45:15 cyberpear: yeah, hiding -devel already in ELN would make sense, so that I can stress GSS/CEE even much more earlier than "now for 9" 20:45:51 https://osci-jenkins-1.ci.fedoraproject.org/ 20:46:10 The various things that start with "eln" 20:46:16 the hidden -devel packages are the main topic of conversation everywhere.... 20:46:51 thanks tdawson 20:47:11 * smooge goes to treat his liver for missing -devel packages 20:47:17 dcavalca: I could send you the github stuff, but I think going that far in is more for the ELN meeting. 20:47:36 yeah, I was mostly curious, we can follow up in the ELN meeting next week 20:47:43 Yep 20:48:17 OK, I'm going to move on 20:48:29 #topic EPEL-7 20:48:44 How is EPEL7 doing? I haven't seen any issues. 20:49:29 I'll assume the silence to be a Unix silence, meaning all is good. 20:49:37 #topic EPEL-8 20:50:11 * smooge salutes 20:50:19 Anything for EPEL-8? 20:50:51 Is that a "I'm walking past you" salute? and I should move on? 20:51:20 walking past 20:51:31 #topic General Issues / Open Floor / EPEL9 20:51:34 watches the parade move on 20:52:21 Anything for open floor? 20:52:36 Maybe I'm cutting those other subjects off too quick ... we still have 8 minutes left. 20:54:57 OK, sounds like everyone wants another five minutes back. 20:55:16 Thank you everyone for coming this week, and for all the work you do for EPEL. 20:55:22 I'll talk to you next week. 20:55:34 #endmeeting