#meeting-1:fedoraproject.org log

<@tdawson:fedora.im>

18:00:24

!startmeeting EPEL (2024-03-13)

<@meetbot:fedora.im>

18:00:25

Meeting started at 2024-03-13 18:00:24 UTC

<@meetbot:fedora.im>

18:00:25

The Meeting name is 'EPEL (2024-03-13)'

<@tdawson:fedora.im>

18:00:32

!meetingname epel

<@tdawson:fedora.im>

18:00:38

!topic aloha

<@rcallicotte:fedora.im>

18:00:38

!hi

<@zodbot:fedora.im>

18:00:40

Robby Callicotte (rcallicotte) - he / him / his

<@pgreco:fedora.im>

18:00:46

!hi

<@zodbot:fedora.im>

18:00:47

Pablo Sebastian Greco (pgreco)

<@tdawson:fedora.im>

18:00:48

Hi Robby Callicotte

<@jrichardson:matrix.org>

18:00:53

!hi

<@rcallicotte:fedora.im>

18:00:54

I'm fighting fires, but I'm here

<@zodbot:fedora.im>

18:00:55

James Richardson (jrichardson)

<@dherrera:fedora.im>

18:01:20

!hi

<@zodbot:fedora.im>

18:01:21

Diego Herrera (dherrera) - he / him / his

<@tdawson:fedora.im>

18:01:31

Hi James Richardson and Diego Herrera

<@nhanlon:beeper.com>

18:01:52

!hi

<@zodbot:fedora.im>

18:01:54

Neil Hanlon (neil) - he / him / his

<@nhanlon:beeper.com>

18:02:02

good afternoon folks

<@nirik:matrix.scrye.com>

18:02:09

morning

<@dherrera:fedora.im>

18:02:11

some of the regulars should be at SCALE today

<@tdawson:fedora.im>

18:02:12

Hi Neil Hanlon

<@tdawson:fedora.im>

18:02:20

Morning nirik

<@tdawson:fedora.im>

18:03:32

Ah ... it's SCALE week

<@carlwgeorge:matrix.org>

18:04:28

!hi

<@zodbot:fedora.im>

18:04:30

Carl George (carlwgeorge) - he / him / his

<@tdawson:fedora.im>

18:04:50

Hi Carl George

<@tdawson:fedora.im>

18:05:06

I thought you were going to SCALE this week.

<@carlwgeorge:matrix.org>

18:05:16

i am on my way to scale, but attending from the airport. was hoping to already be through security, but was running a bit behind

<@carlwgeorge:matrix.org>

18:05:48

so this meeting, then security, then a meal before my flight. still plenty of time.

<@carlwgeorge:matrix.org>

18:06:01

my flight is in 2.5 hrs

<@tdawson:fedora.im>

18:06:05

If you say so :) ... always good to have you here.

<@tdawson:fedora.im>

18:06:23

!topic End Of Life (EOL)

<@tdawson:fedora.im>

18:06:29

RHEL 7 / epel-7 will go EOL on 2024-06-30 https://endoflife.date/rhel CentOS Stream 8 / epel-8-next goes EOL in 2024-05-31 CentOS Stream 9 / epel-9-next goes EOL in 2027-05-31 https://endoflife.date/centos-stream

<@tdawson:fedora.im>

18:07:15

I don't have any witty comments this week ... so moving on.

<@tdawson:fedora.im>

18:07:23

!topic EPEL Issues https://pagure.io/epel/issues

<@tdawson:fedora.im>

18:07:29

https://pagure.io/epel/issues?tags=meeting&status=Open

<@tdawson:fedora.im>

18:08:02

We do have one issue marked for the meeting

<@tdawson:fedora.im>

18:08:14

https://pagure.io/epel/issue/267

<@tdawson:fedora.im>

18:08:49

For those that haven't read it, this is Neil Hanlon request to joint the epel-packagers-sig

<@tdawson:fedora.im>

18:09:26

I had a bit of a concern about him being a fairly new EPEL packager, so I went to look at our requirements .... and grew much more concerned.

<@tdawson:fedora.im>

18:09:31

Because, there aren't any.

<@nhanlon:beeper.com>

18:09:52

As I said in the ticket, valid concerns that I also have about myself.

<@carlwgeorge:matrix.org>

18:09:55

i had similar thoughts when i saw the issue, thus tagging it for the meeting

<@tdawson:fedora.im>

18:10:21

So, I haven't opened an issue yet, but I'm in the process of writting a seperate issue about requirements.

<@tdawson:fedora.im>

18:10:53

https://docs.fedoraproject.org/en-US/epel/epel-packagers-sig/#_join_the_epel_packagers_sig

<@tdawson:fedora.im>

18:11:11

Unless someone else is writting an issue about that.

<@nirik:matrix.scrye.com>

18:11:36

I think having at least some suggested requirements would be a good idea.

<@carlwgeorge:matrix.org>

18:11:49

we both said and documented that this sig would be like proven packagers for epel. the requirement for that is the sponsors vote on it. i think our rule should be the same to keep it simple.

<@rcallicotte:fedora.im>

18:11:50

What would be valid requirement? Number of Fedora pkgs already maintained? Requestor must be a fedora packager for some lenght of time etc?

<@carlwgeorge:matrix.org>

18:12:43

for provenpackager, i don't think there is an exact number of packages or length of time, although those can certainly factor into it

<@nhanlon:beeper.com>

18:13:09

🤞 it's "cumulative hours of time derailing meetings"

<@tdawson:fedora.im>

18:13:14

Well, if you read the paragraph before, for the proven packagers it says "They are a group of skilled package maintainers who are experienced in a wide variety of package types and who are familiar with the packaging guidelines and package maintainer policies, as well as acutely aware of release schedule and freeze policies."

<@carlwgeorge:matrix.org>

18:13:21

most pp requests i see hinge more on "i have a specific task i'm trying to accomplish that is impeded by not being a pp"

<@carlwgeorge:matrix.org>

18:14:01

so just being around a long time and doing lots of packages is not, in itself, enough justification

<@tdawson:fedora.im>

18:14:42

So, while that is not really "sepecific" and bit vague, it is still ... something you can point to.

<@tdawson:fedora.im>

18:14:59

So, while that is not really "specific" and bit vague, it is still ... something you can point to.

<@nhanlon:beeper.com>

18:15:25

I think also, the documentation page seems to indicate that joining the EPEL packagers sig is a prerequisite for the next heading: "Get to work" which lists things to do.

<@tdawson:fedora.im>

18:15:37

True ... but you know ... cut-n-paste. :)

<@nhanlon:beeper.com>

18:15:41

I don't believe that's the intent, of course

<@tdawson:fedora.im>

18:16:17

That is a good point. Because many of those things can be done by anyone that is a packager. Not all of them, but many.

<@nhanlon:beeper.com>

18:16:52

and also speaking for myself, I think anything that I would do with a "EPEL packagers sig" label would be the same as I'd do anyways: i.e., open pull requests and ask questions because I am not yet fully confident in myself and my groking of our policies.

<@nirik:matrix.scrye.com>

18:17:09

Things seem to have gotten more strict for fedora provenpackager requests in recent years... usually they are asked what they would do that they can't do now... so, some kind of justification/need

<@carlwgeorge:matrix.org>

18:17:57

yes, work happens after joining the sig, but there is also work before joining the sig, which as troy noted is a bit lacking. nothing personal of course, but i would certainly like to see more epel activity before granting access to all packages that have epel-packagers-sig on them

<@carlwgeorge:matrix.org>

18:19:34

the other aspect to look at, if we just stick to sponsor voting (which i think we should), is if our current number of sponsors is sufficient

<@carlwgeorge:matrix.org>

18:19:56

!link https://accounts.fedoraproject.org/group/epel-packagers-sig/

<@carlwgeorge:matrix.org>

18:21:36

so with what me and nirik were pointing out about highlighting a need, is there something you're trying to do now that you feel you are blocked/slowed down on by not having that access?

<@tdawson:fedora.im>

18:22:18

So, I'm thinking ... how about a re-write of the page.

<@nhanlon:beeper.com>

18:23:11

Truthfully? Feeling as though I'm part of EPEL. I *am* an EPEL Packager, and I have a Special Interest in it. Perhaps the name of the group should be amended.

<@tdawson:fedora.im>

18:24:07

I have to agree, the name of the SIG is ... well ... odd. Because yes, you Neil Hanlon are a contributing member of the EPEL SIG.

<@nirik:matrix.scrye.com>

18:24:12

docs could definitely be better

<@nhanlon:beeper.com>

18:24:40

and to be clear: you all have been and continue to be very welcoming, that's not an issue at all.

<@tdawson:fedora.im>

18:24:42

But when people see epel-packagers-sig, they think they need to join that to become a part of the EPEL SIG, which they don't.

<@carlwgeorge:matrix.org>

18:25:18

yeah the naming is not great

<@carlwgeorge:matrix.org>

18:25:44

you're 100% part of epel, no one should feel they need to be in that sig to be

<@carlwgeorge:matrix.org>

18:26:16

anyone who has every submitted an epel update is part of epel in my mind. epel-packagers-sig is an elevated permission.

<@conan_kudo:matrix.org>

18:29:17

!hi

<@tdawson:fedora.im>

18:29:20

So, I'm going to timebox this so we can move on. I'll open a new issue detailing changes to the current docs, with what we have talked about today, and then we can discuss that next week. Or if I'm really lucky, I'll get PR done that we can talk about.

<@zodbot:fedora.im>

18:29:25

Neal Gompa (ngompa) - he / him / his

<@nhanlon:beeper.com>

18:29:33

I have some thoughts, but, they're all a bit messy right now. In short, my request is not for any specific reason (i.e., to solve an immediate need). I'm happy to work with y'all on documentation and such. Thank you for the comments and discussion.

<@tdawson:fedora.im>

18:29:34

Hi Conan Kudo

<@tdawson:fedora.im>

18:30:23

That was the only issue marked with meeting, moving on.

<@tdawson:fedora.im>

18:30:30

!topic Old Business

<@tdawson:fedora.im>

18:31:00

One quick old business. Thank you all (especially Carl) for filling in while I was away.

<@tdawson:fedora.im>

18:31:42

Do we have any other Old Business that we want to bring up?

<@tdawson:fedora.im>

18:32:40

I'm going to bring up one other thing that's old ... epel-10 (or is that new)

<@nhanlon:beeper.com>

18:33:12

impending :)

<@tdawson:fedora.im>

18:33:33

We currently have CentOS Stream 10 production composes ... They are so new they aren't even alpha's ... BUT ... the paths and URL's are there if we wanted to start building our scripts.

<@conan_kudo:matrix.org>

18:33:53

are they signed yet?

<@conan_kudo:matrix.org>

18:34:02

and has the content stripping been completed?

<@tdawson:fedora.im>

18:34:08

No, so new they aren't even signed ...

<@tdawson:fedora.im>

18:34:18

And no, the content stripping hasn't been completed.

<@carlwgeorge:matrix.org>

18:34:26

i believe James Richardson wanted to poke nirik about this

<@carlwgeorge:matrix.org>

18:34:44

!link https://pagure.io/releng/issue/11999

<@nirik:matrix.scrye.com>

18:34:48

there's a ticket filed a while ago...

<@jrichardson:matrix.org>

18:34:56

Carl George: beat me to it

<@conan_kudo:matrix.org>

18:34:56

I am wary of setting EPEL 10 up yet while packages that are intended to be excluded for RHEL 10... haven't yet

<@nirik:matrix.scrye.com>

18:34:58

but to my understanding there were no compsoes yet. \

<@nirik:matrix.scrye.com>

18:35:31

yeah, seems pretty early. ;)

<@conan_kudo:matrix.org>

18:35:31

nirik: composes exist: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/

<@tdawson:fedora.im>

18:35:33

I had to test my scripts, and got them to work ... so there are production paths.

<@carlwgeorge:matrix.org>

18:35:38

for epel9, are we syncing directly from composes, or from the mirror content?

<@tdawson:fedora.im>

18:36:25

I thought we were syncing from composes ... if we are syncing from mirror content ... well ... that is still a ways away.

<@carlwgeorge:matrix.org>

18:36:35

the rsync module that https://pagure.io/fedora-infra/ansible/blob/main/f/roles/batcave/files/centos-9s-sync syncs from isn't publicly accessible to check

<@nirik:matrix.scrye.com>

18:36:36

no, we are syncing from mirror content I am pretty sure.

<@tdawson:fedora.im>

18:37:03

ah ... then if we are syncing from the mirrors ... then I'll be quiet until we get there.

<@carlwgeorge:matrix.org>

18:37:19

i think it would be worthwhile to get the sync set up initially directly from the production compose link, and then switch it to mirror content later

<@pgreco:fedora.im>

18:38:08

I think that's what was done for 9

<@nirik:matrix.scrye.com>

18:38:15

I see COMPOSE_ID of CentOS-Stream-9-20240311.0 there.

<@pgreco:fedora.im>

18:38:46

first sync from stream until Carl gave the heads up for 9.1 content and then we froze it

<@pgreco:fedora.im>

18:38:52

until release

<@nirik:matrix.scrye.com>

18:38:56

so is the intent to setup all the epel10 koji stuff? whats the goal to syncing now?

<@yselkowitz:fedora.im>

18:39:31

to make sure it all works early?

<@carlwgeorge:matrix.org>

18:39:50

yes, i would like to start the koji setup. on a related note, is it possible to create a koji build target that isn't wide open for anyone to build against?

<@nirik:matrix.scrye.com>

18:39:57

I guess I was wondering what 'it' was?

<@tdawson:fedora.im>

18:39:58

If we want to wait for things to be more stable (signed and more packages trimmed out) I'm fine waiting.

<@nirik:matrix.scrye.com>

18:40:17

I am pretty worried people will start using it/depending on it if it's available in koji.

<@conan_kudo:matrix.org>

18:41:06

for the purposes of Koji, signed doesn't really matter since no signature validation works there anyway, but packages being trimmed out is important because we could wind up in some strange situations right now

<@carlwgeorge:matrix.org>

18:41:07

that's what happened with epel9-next, people started building for it before we announced

<@tdawson:fedora.im>

18:41:18

nirik: COMPOSE_ID of CentOS-Stream-9-20240311.0 is a production compose. Yes, it was synced out to the mirrors. But it's also the latest CS9 compose.

<@nirik:matrix.scrye.com>

18:41:21

no, there's no way to restrict a target. You can set policy to prevent tagging tho

<@carlwgeorge:matrix.org>

18:41:54

we could also just do the koji setup in staging, not prod, which would still benefit from c10 being synced to batcave for the external repo

<@yselkowitz:fedora.im>

18:42:03

mind you there isn't a whole lot left to trim, but even after beta there are no guarantees

<@nirik:matrix.scrye.com>

18:42:21

yeah, setting up things in stg first is a very good idea IMHO.

<@tdawson:fedora.im>

18:43:05

I'm good with stg

<@nirik:matrix.scrye.com>

18:43:18

I don't think people look at stg as much (and realize it gets repaved from time to time anyhow), and having everything set right will make rolling to prod easy

<@nirik:matrix.scrye.com>

18:43:46

especially since we are going to be using a new tag / branch setup.

<@nirik:matrix.scrye.com>

18:44:29

anyhow, sure, we can sync if there's composes now to sync and use them to setup stg.

<@tdawson:fedora.im>

18:44:48

Sounds good.

<@tdawson:fedora.im>

18:45:18

Not a rush, but I wanted to let you know the paths were there if someone needed them.

<@tdawson:fedora.im>

18:45:28

Any other Old Business?

<@tdawson:fedora.im>

18:46:02

!topic General Issues / Open Floor

<@tdawson:fedora.im>

18:46:21

Does anyone have anything for Open Floor?

<@carlwgeorge:matrix.org>

18:47:59

if you're going to scale, i'll be talking a bit about epel during the "centos classroom" session

<@tdawson:fedora.im>

18:48:36

Cool. I won't be there, but I didn't know there was a "CentOS Classroom"

<@carlwgeorge:matrix.org>

18:49:06

!link https://www.socallinuxexpo.org/scale/21x/presentations/centos-classroom-and-packaging-workshop

<@tdawson:fedora.im>

18:51:09

Very nice.

<@tdawson:fedora.im>

18:51:15

Anything else before we close the meeting?

<@tdawson:fedora.im>

18:52:04

Then let's close early. Let Carl get through airport security with a bit of extra time.

<@nirik:matrix.scrye.com>

18:52:36

safe travels Carl George! (and all heading to scale)

<@tdawson:fedora.im>

18:52:52

Thank you all for coming. And thank you all for all the work you do for EPEL and it's community.

<@tdawson:fedora.im>

18:52:59

Talk to you next week, if not sooner.

<@pgreco:fedora.im>

18:53:02

bye guys, thanks!

<@carlwgeorge:matrix.org>

18:53:11

first flight was delayed, so i'm in no rush

<@nhanlon:beeper.com>

18:53:13

thanks folks! safe travels Carl

<@tdawson:fedora.im>

18:53:18

!endmeeting