20:00:12 <tdawson> #startmeeting EPEL (2021-06-02)
20:00:12 <zodbot> Meeting started Wed Jun  9 20:00:12 2021 UTC.
20:00:12 <zodbot> This meeting is logged and archived in a public location.
20:00:12 <zodbot> The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:12 <zodbot> The meeting name has been set to 'epel_(2021-06-02)'
20:00:13 <tdawson> #meetingname epel
20:00:13 <zodbot> The meeting name has been set to 'epel'
20:00:15 <tdawson> #chair nirik tdawson bstinson pgreco carlwgeorge michel_slm
20:00:15 <zodbot> Current chairs: bstinson carlwgeorge michel_slm nirik pgreco tdawson
20:00:16 <tdawson> #topic aloha
20:00:30 <carlwgeorge> howdy yall
20:00:33 <nirik> morning
20:00:38 <michel> .hello salimma
20:00:39 <zodbot> michel: salimma 'Michel Alexandre Salim' <michel@michel-slm.name>
20:00:43 <michel> hello!
20:00:49 <pgreco> hello!
20:01:17 <tdawson> Hi carlwgeorge
20:01:21 <tdawson> Hi nirik
20:01:25 <tdawson> Hi michel
20:01:28 <tdawson> Hi pgreco
20:02:07 <tdawson> Looks like we have a few more than last week.  That's always good. :)
20:02:10 <nirik> Hi tdawson
20:04:31 <tdawson> Looking like this is all for this week.
20:04:47 <tdawson> #topic Old Business
20:05:03 <tdawson> Let's start with EPEL Packaging SIG
20:05:33 <tdawson> Any news, or anything to report?
20:06:42 <tdawson> michel: Anything for the packaging SIG?
20:07:27 <michel> one minor thing
20:07:41 <michel> wait, trying to find the bu
20:08:22 <michel> https://bugzilla.redhat.com/show_bug.cgi?id=1968069 -- I'm trialing the sort of language we want to use in this branch request for bloaty, not getting anywhere yet after 5 days
20:08:50 <michel> so perhaps it's time to dogfood the FESCo escalation. Did we ... have some other packages from last week that's already aged enough?
20:09:32 <michel> sorry, rel-eng
20:09:46 <tdawson> michel: Oh, you missed a week.  Yep, it worked.
20:09:59 <carlwgeorge> yup, i used the process for gthumb
20:10:08 <carlwgeorge> https://bugzilla.redhat.com/show_bug.cgi?id=1944831
20:10:22 <nirik> needs 2 weeks of stall tho I think
20:10:23 <michel> so, wait a week, ping again with needinfo, then after two weeks, file rel-eng?
20:10:33 <tdawson> Yep
20:10:36 <nirik> https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Stalled_EPEL_Requests
20:10:50 <carlwgeorge> is it 2wks after the second ping, or 2wks total?
20:10:58 <michel> I think 2 total right?
20:11:03 <tdawson> Correct
20:11:10 <michel> wait a week, ping, then file rel-eng
20:11:11 <carlwgeorge> ok just making sure
20:11:29 <michel> ok, I'll go check the ones in EPELPackagersSIG tracker and ping the ones that are still open today
20:11:39 <tdawson> bz, wait a week, ping, wait a week, rel-eng
20:11:52 <michel> related to that... has anyone had time to look at docs?
20:12:15 <tdawson> I pinged Petr, who hasn't responded.
20:12:29 <tdawson> I know he's busy on an internal doc process.
20:13:47 <tdawson> But I also need to go though them and mark different things, so I still have some work to do.
20:15:26 <michel> our EPEL docs will be based off the pagure EPEL repo though, right?
20:15:38 <michel> so we can start creating files now?
20:15:47 <tdawson> Yes, we can start creating files now.
20:16:04 <tdawson> But he's going to take all the wiki pages and import them in there.
20:16:19 <tdawson> I'll just tell him to leave, or incorporate, the pages that are currently there.
20:17:01 <tdawson> Anything else for SIG and/or documentation?
20:17:51 <tdawson> Let's move on to epel-next
20:17:57 <tdawson> carlwgeorge: Any news for epel-next ?
20:18:28 <carlwgeorge> the epel-release update that adds epel-next-release is currently available in the testing repo
20:18:46 <tdawson> Ya!!
20:19:00 <michel> oh nice. I have some dogfooders who are using C8 with KDE from EPEL
20:19:11 <carlwgeorge> i've already triple checked the upgrade we discussed.  when epel-release is updated on rhel8, nothing else happens.  when it's updated on cs8, it pulls in epel-next-release.
20:19:19 <michel> so they got hit by the Qt version mismatch. should I ask them to start testing epel-next-release?
20:19:37 <carlwgeorge> michel: yes, in fact qt is the only incompat i currently know about
20:19:58 <tdawson> Well, give it some time.   I'm having branching problems.
20:20:16 <michel> so:
20:20:16 <michel> - dnf --enablerepo=epel-testing --refresh upgrade
20:20:16 <michel> - dnf --refresh upgrade
20:20:19 <carlwgeorge> qt5-qtwebkit was my guinea pig, and is in already in stable
20:20:23 <michel> should that be enough?
20:20:43 <tdawson> When I branched KDE for epel8 I managed to get everything branched, without actually owning any of them.
20:20:47 <carlwgeorge> michel: yes, unless your local mirror is lagging
20:21:10 <carlwgeorge> tdawson: yes i disable auto-push so we can leave it as long as we want
20:21:28 <carlwgeorge> ideally wait until it's documented, and then announce when we push it
20:21:52 <tdawson> Now that we change to make sure you have some type of rights on the package, I've found that I don't have access to about 40% of the packages, so have to request branching for them.
20:23:49 <carlwgeorge> man of the things that need to be rebuilt have the kde sig on them
20:23:50 <tdawson> In short, it's going to take longer than I planned for KDE/Qt to be ready for epel8-next.
20:24:18 <carlwgeorge> and i have no problem (ab)using the stalled process for this
20:24:45 <carlwgeorge> but i think the first step is to have documentation to point maintainers at
20:24:46 <tdawson> Well, we're talking about 350 packages.   I'm bringing it up with the KDE-SIG
20:25:08 <carlwgeorge> i can throw that up in the wiki, or should we put it in docs.fp.o?
20:25:22 <tdawson> Because we're going to hit the same problem when we do epel9-next and then epel9.
20:25:59 <tdawson> Anyway, in short, it's going to take me a while to get KDE in shape for epel8-next.
20:26:11 <michel> do we have anyone in KDE SIG we should loop in on this?
20:26:25 <carlwgeorge> perhaps Eighth_Doctor
20:26:32 <michel> either they should be there or we should encourage them to add epel-packagers-sig so we can do it :)
20:26:44 <Eighth_Doctor> hm?
20:26:44 <tdawson> They know.  And it's Rex.  The problem is that he's very busy with qt6 and updates, and alot of stuff.
20:27:05 <tdawson> michel: No, just kde-sig permissions.
20:27:05 <carlwgeorge> Eighth_Doctor: involving the kde sig with epel8-next rebuilds
20:27:41 <Eighth_Doctor> if tdawson is a KDE user and wants to help maintain it in EPEL, we can add him to KDE SIG group
20:27:52 <tdawson> I am on the kde-sig group
20:28:01 <Eighth_Doctor> ah okay then
20:28:06 <michel> oh yeah, qt6 is going to be major
20:28:21 <tdawson> The problem is that now all the packages, are owned, or have kde-sig commit right
20:28:29 <michel> s/is going to be/is ... Qt basically dropped all support for Qt5 IIRC?
20:28:47 <carlwgeorge> qt5 rebuilds for the qt 5.15 rebase in cs8 is the only thing i know of that epel8-next is needed for currently
20:28:55 <tdawson> /now all packages/not all packages/
20:29:53 <tdawson> carlwgeorge: It's a cascading effect, but we also are planning on updating the whole kde stack to go along with it.
20:30:10 <michel> sounds like, between KDE sig and EPEL Packagers sig... having a script that can batch-file permisison requests will be nice
20:30:32 <tdawson> That would be useful
20:31:25 * michel adding that to his ever-growing todo
20:31:30 <tdawson> :)
20:31:48 <carlwgeorge> did anyone have opinions on documenting epel-next in the wiki vs docs.fp.o?
20:31:52 <tdawson> carlwgeorge: I just tried your epel-release, worked as planned.  :)
20:32:31 <michel> if Petr is going to mass-migrate the wiki pages, then it does not matter either way right?
20:32:52 <tdawson> To me is seems easier to do it in docs.fp.o, but I don't know how long it will take Petr.
20:33:20 <nirik> probibly should either wait for docs, or just be done in wiki if it's not waiting
20:33:48 <tdawson> Ya, since we don't know, I'd say go for the wiki.
20:34:14 <carlwgeorge> yeah looking at it now, i'm not sure of what structure to use if i put it in docs.fp.o now.  i'll do it in the wiki.
20:34:48 <carlwgeorge> anyways, up next is a pull request to update mock-core-configs, then announce it, and we're done
20:35:24 <tdawson> Cool
20:35:54 <tdawson> Getting close, and actually usable already.
20:36:27 <tdawson> Moving on ... the Fails to Install
20:36:39 <tdawson> I haven't written an email and/or proposed policy yet.
20:37:13 <tdawson> I was expecting to have more time before CentOS Linux 8.4 came out, but now it is out ... so I'll have to get on that.
20:38:23 <tdawson> I don't think we had any other old business, but I'm feeling like I missed something from the open floor of last week.
20:38:49 <carlwgeorge> yeah we knocked out 8.4 pretty quick.  not as quick as alma, but in about half the time of 8.3.
20:38:57 <carlwgeorge> *our 8.3
20:39:27 <tdawson> Good job to everyone who helped with that.
20:39:48 <tdawson> #topic EPEL-7
20:40:05 <tdawson> Anything for EPEL 7?
20:41:15 <tdawson> I'll take the resounding silence as a no
20:41:20 <tdawson> #topic EPEL-8
20:41:25 <tdawson> How about 8?
20:42:39 <tdawson> #topic General Issues / Open Floor
20:42:57 * michel tempted to give his pesky Nvidia users the Alma kernel once C8 is no more
20:42:57 <tdawson> And now I remember, it was about badges and an epel logo
20:43:09 <michel> ooh. badges?
20:43:26 <tdawson> Committee member badges
20:43:39 <carlwgeorge> yes, i think i suggested that
20:43:57 <tdawson> Yep, and I got you a rough graphic.
20:43:58 <carlwgeorge> tdawson sent me an email with a great proof of concept artwork
20:44:21 <carlwgeorge> i need to start the badge ticket and do that process, and of course when it's done i'll be sure to assign it to all of us
20:45:28 <tdawson> Also, a new EPEL logo.  I was going to send out an email for a new EPEL Logo contest, or at least submisions.
20:45:34 <michel> more badges. yeah
20:45:37 <pgreco> michel: not the lts ones?
20:45:51 <michel> oh... related to that. who on the design team can help with this?
20:45:57 <michel> pgreco: I take LTS badges too
20:45:59 <michel> haha
20:46:24 * michel notes that Mo is probably out of the office with some urgent family matters
20:46:43 <tdawson> True, but this also isn't a rush
20:47:01 <tdawson> Nobody's asked for new badges and/or logo, other than us.
20:47:34 <nirik> the design team has a process... we could file a ticket asking...
20:47:42 <carlwgeorge> yeah that's what i'm gonna do
20:48:09 <carlwgeorge> tdawson sent me his artwork idea last week, i'm just behind on starting the ticket
20:48:24 * nirik nods
20:48:26 <tdawson> Would we also file a ticket asking about a new logo?
20:48:28 <michel> would the new EPEL logo be a mix of the new Fedora logo and the new CentOS logo? :)
20:48:31 <michel> (not that the CentOS one is live yet)
20:49:29 <tdawson> I'll be honest, usually I have good ideas for logo's, but for EPEL, nothing is really coming to mind.
20:49:30 <nirik> I'm not sure thats possible... but might be cool if it is
20:50:19 <nirik> a hatband with a bunch of feathers in it? (enhancing your hat :)
20:50:30 <tdawson> And it's not that I hate the old one, but it doesn't scale.  It needs to be in vector form ... and ... I'm not being honest, I'm not a fan of the current one.
20:51:23 <tdawson> I'm pretty sure anything involving a hat is off the table ... unless we went through legal.
20:51:28 <nirik> badge: panda with muscles in "EL" shirt, wearing a exoskeleton/mech thats EP
20:51:42 <tdawson> *laughs*
20:51:45 <nirik> but design folks are much better at this sort of thing than I. :)
20:52:23 <michel> panda with muscles wearing a top hat and a cape
20:52:45 <michel> ok, make that a beret then and maybe legal will be happy ;)
20:52:51 <tdawson> *laughs*
20:53:10 <misc> fedora + centos => centora, then you can just get inspiration from that
20:53:58 <michel> centaur? would that be OK
20:54:04 <carlwgeorge> the current themes in epel badges is ants and ties.  i think that's cute for the badges but not so much for the logo, but perhaps we can draw inspiration from it.
20:54:19 <michel> ants... of course, because we're corporate drones :p
20:54:33 <misc> ant is also gluster logo :/
20:54:37 <michel> a Borg cube
20:54:37 <carlwgeorge> yeah that's the joke (and even the title of one of the badges)
20:54:44 <michel> ok I'll stop now
20:54:52 <tdawson> I like the centaur idea.
20:55:54 <tdawson> So, carlwgeorge will contact about badges.   I'm going to do a quick touch with MMiller about EPEL logo.  We're technically under him, so I'd like his input.
20:56:31 <carlwgeorge> i bet his input is "as long as it's not a hat i don't care" :P
20:56:40 <tdawson> Could be
20:57:25 <michel> kind of sad the Top Hat distinguished engineer badge will never see the light of day
20:57:25 <tdawson> Our hour is ending, anything before we close the meeting?
20:57:43 <carlwgeorge> reminder that summit part 2 is next week
20:58:11 <carlwgeorge> tell your friends, and stop by the fedora/centos booth to say hi
20:58:49 <tdawson> I didn't know there was a booth ... I'll have to search for it this time.
20:59:00 * nirik didn't see it last time either
20:59:23 <tdawson> It must be hidden in the corner
20:59:42 <tdawson> Thank you everyone for coming this week and for the good discussion.
20:59:52 <carlwgeorge> there's a way to get to it, i'll probably tweet out the breadcrumb trail to find it next week when i'm in the platform
21:00:05 <nirik> in the basement behind the door marked 'beware of lepoard'
21:00:24 <tdawson> I'll talk to you next week, same time, same place.
21:00:34 <tdawson> *laughs*
21:00:46 <tdawson> #endmeeting