Meeting started at 2024-03-13 16:34:16 UTC

The Meeting name is 'fedora_coreos_meeting'

.hi

!hi

None (jlebon)

!hi aaradhak

Aashish Radhakrishnan (aaradhak)

!hi gursewak

Gursewak Singh (gursewak)

.hello jmarrero

!hi

Adam Piasecki (c4rt0) - he / him / his

!hello jmarrero

Joseph Marrero (jmarrero)

!hi

Michael Armijo (marmijo)

!hello

Timothée Ravier (siosm) - he / him / his

.hi

!hi

No Fedora Accounts users have the @jbtrystram:matrix.org Matrix Account defined

!hi jbtrystram

Jean-Baptiste Trystram (jbtrystram) - he / him / his

Looking for the previous meeting notes

fifofonix to bring up a 1.28 cluster with zswap

fifofonix: Any updates on that item?

ok, let's re-action it and we'll see later

From https://github.com/coreos/fcos-meeting-action/issues/75, we have a lot of topics today. Which ones are most important?

ahh nice. lots of choices :)

maybe the test week one first since that one has a timeline to it?

We have to make a change in the Fedora test week after a discussion last week. The test week is now scheduled to happen in the week of March 25

The podman test week is scheduled to happen around the week of March 18. FCOS will overlap on Podman5 and Podman desktop. To avoid any regression related issue, we decided to move the test week to March 25.

Do we already have podman 5 in next?

We have decided to make a change in the Fedora test week after a discussion last week. The test week is now scheduled to happen in the week of March 25

Do folks organizing the test week feel ready?

(if they could assign themselves to the issue that would be great for tracking)

Fedora 40 Beta was No-Go last week. Pushing out the earliest beta target to March 19. There's another meeting tomorrow to determine if F40 beta will be Go/No-Go for that date

I added some bits in the docs regarding iSCSI so it's ready to be tested :)

ash: hmm, the text in https://github.com/coreos/fedora-coreos-tracker/issues/1686 doesn't look like the latest version?

We have to find volunteers for the test week especially to carry the tests on different platforms. That is a task in hand

travier: next is still on f39. podman v5 is in branched, so it'll be in next once we rebase it to f40

Its in the hackmd that we have noted down so far : https://hackmd.io/nhLcXDbZTcWTzkvQAcUwtA

Hackmd are always temporary and should be synced back to issues as much as possible

ash: sorry if i didn't make that clear

no, its just that I thought of adding the contents from hackmd to the TO-DO list list later. I ll add it right away

Can we let you three ash apiaseck jbtrystram handle the preparation for the test week?

works for me

I'm up for it.

Yes!it works with me.

sumantro has created new pages for the new test cases, but they might need tweaking

i wouldn't worry about the "carried over" items in the todo list

Great, I'll assign the issue to you all. Anything else we should talk about for this topic?

Nothing else from me

nothing here

alright, let's move to the next one.

any priority?

This one should be a short one

The idea is to centralize the access management to repos for packages that we maintain

Option A is to re-use the coreos group to grant commit access to everyone in the group and add folks doing package management be part of this group

Option B is to create another group for commit access only and grant members of the coreos group admin access

it feels a bit working around the "open source community" aspect of becoming a fedora packager

everyone still needs to go through the new packager flow

i.e. you have to contribute something, find someone willing to sponsor you .. rather than "i'm part of X team and that grants me things"

how so?

this would just make it easier to manage our own packages

but it already works like that for the GH repos so that would be aligning stuff

We will still expect people to do pull request for changes and get reviews

You still have to be sponsored into the packager group

ah ok, I didn't realise that. ignore what I typed then !

Any preference for option A or B?

option B makes sense to me

there's also *a lot* of Rust packages we technically currently own as they are deps of some of our Rust-based upstream projects

currently, i'm the admin for all of them (inherited from Benjamin)

so spreading that better would be good indeed

yeah, this is mostly my concern around having a single person have the admin permissions and then we have troubles when we need to fix things

managing groups can happen independently

I think also the current coreos group is just used for calendar perms, which is to say, not much

Any concerns regarding option B? I'll make a proposed

proposed: We well create a coreos-packager group with commit access to packages maintained by the group and use the coreos group for admin access to those same packages.

+1

+1 but "we will" :)

Option B +

ack

proposed: We will create a coreos-packager group with commit access to packages maintained by the group and use the coreos group for admin access to those same packages.

+1

Do we have time for another one? Not sure

would be good to have Dusty too for the others anyway

maybe just open floor?

OK, so let's move to open discussion

I've updated the dates for the upcoming meetings in https://hackmd.io/OSVZR5vETkmKuA9A_KAzUg I've subscribed folks that already ran previous meeting to run upcoming ones again. Feel free to adjust. We also appreciate having new volunteers running meeting!

Don't be like me! Mark your next meeting in your calendar so that you don't forget 😅

could we pin this doc at the top of the CoreOS matrix room ?

i didn't even know Matrix supported that. cool

I'm not an admin there so I'll have to ask Dusty or ask to be made admin

Jonathan Lebon: i am not sure it does. Just asking

it does. you have to click on the channel name at the top and then "Pinned" (at least in the web UI)

it looks like change proposals for f41 are open. travier should we work together on submitting something for the scriptlet thing?

That would be good yes

travier: i think we can close this?

yes, if there is nothing else, let's close this meeting