Meeting started at 2025-07-30 15:29:20 UTC

The Meeting name is 'fedora_coreos_meeting'

!hi

Dusty Mabe (dustymabe) - he / him / his

!hi

Hristo Marinov (hricky) - he / him / his

!hi

Michael Armijo (marmijo)

We don't have any action items for the last meeting.

So let's discuss about Fedora 43 Release Schedule.

!hi aaradhak

Aashish Radhakrishnan (aaradhak)

!hi

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

!hi

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

!hi

Steven Presti (spresti)

Is any of this subjects needed to be adressed?

mass rebuild is in progress

we fixed butane

we'll fix things as they come

looks like branching is coming up soon

Tue 2025-08-12

do we have anyone this cycle who wants to volunteer to be the release wrangler?

i.e. the items in https://github.com/coreos/fedora-coreos-tracker/issues/1935

🙋I can do it this cycle

Just a question: when are we going to have the Test Week?

Probably mid to late September. I think we typically do it after beta release.

!action: 🚩 marmijo will be the release wrangler for Fedora 43 this cycle

dustymabe has already given cookies to marmijo during the F42 timeframe

zodbot: how about a beer then?

spresti gave a cookie to marmijo. They now have 17 cookies, 6 of which were obtained in the Fedora 42 release cycle

siosm has already given cookies to marmijo during the F42 timeframe

jbtrystram has already given cookies to marmijo during the F42 timeframe

😄 thanks for trying everyone 🍪

Thank you, marmijo 🍪

So, let's move to our topics from tracker repository.

Folks from the podman team would like to take over maintenance of a Go module that we don't really maintain anymore

So +1 from me

+1 from me 👍️

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

+1 from me too.

+1 from me 👍️

+1 !

+1

I'm fine moving this to another org, but it appears to be more work than just moving the repo and it's fine to keep it in the coreos org.

Makes sense

+1 from me as well

So are we going to keep it in our org and add new mainteners from podman team?

So agreed "Add new maintainers to the go-systemd repo and keep it under the coreos org"

!agreed: Add new maintainers to the go-systemd repo and keep it under the coreos org

!agreed: 👍 Add new maintainers to the go-systemd repo and keep it under the coreos org

Not sure if it works, anyway I will comment it in the issue to let them know.

yeah. I think you didn't need the `:`

So, we have also this recently label added issue in fedora-coreos-tracker, from dustymabe

Consider switching EROFS live generation from -Eall-fragments to -Efragments #1991

The EROFS maintainer is suggesting we switch to using another option to build our EROFS images

I have not done any performance / size checks but it should be fine if the maintainer recommends it

a quick check for regressions would still be good

so +1 from me

This is where having a fairly comprehensive CI helps a lot.

I don't think we check build time or runtime performance however :)

I'd like to make the change in EL10 too but I think the version there is older and the new options aren't recommended yet

The maintainer is going to open a request to bump EL10 as well. We can update our config in the rhel-coreos-config repo with a link to the tracker for updating the version. So EL10 will stay on the old options for now, while Fedora moves to the new ones.

sounds good to me

!proposed we'll use the new flag in FCOS and update EL10 once erofs-utils 1.8.10 lands there

👍️

sgtm

I think we don't have 'proposed', let's use ideainstead

+1

So, last topic from the tracker:

Oh I think we should have agreed on that before switching topics 'i.e agreed' but maybe idea will be enough for this time

Sorry about it, we can go back on that. Should we vote?

No worries its just an automation thing; (we did agree) just the bot doesnt know

no one complained so it should be fine but agree that we should have agreed to it :)

we are a bit short on time to review the new changes but I don't see anything major so we can table that for next time and do it async

Ok, should we jump directly for the open floor?

I would say so

I wanted to ask about frequency of release for afterburn/ignition we have a new proivder being added and well that can be quite a influence on demand for a release. The issue is we just released 2 weeks ago

I guess we release as needed

do you feel like it's too much work to do it so soon?

No its not that its too much work, it just feels like it can be a time sync. Upstream is not bad its downstream that takes awhile

What's the new provider?

if we don't strictly need the changes downstream then we can skip pushing it there

It's a fairly small change and getting new providers supported is always nice so I would say we should do it

upcloud

https://github.com/coreos/ignition/pull/2110

Nice. Never heard of them

yeah. I'd say if we don't need the change downstream then we opt-out of doing that for releases

it's nice to get it into FCOS at least

Okay well I will plan to have another release in the next sprint :)

Yeah the main draw is upstream in this case for sure

It's kind of nice we are getting a lot of contributions

Thank you for working on this spresti

siosm gave a cookie to dustymabe. They now have 196 cookies, 4 of which were obtained in the Fedora 42 release cycle

Definitely share the load if we can find new people on the team interested in learning

siosm gave a cookie to spresti. They now have 3 cookies, 1 of which were obtained in the Fedora 42 release cycle

Yes! It's nice that people are participating a lot!

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

100%

We are almost finishing with our time! So thank you all for being here today! Nice discussions :)

oh.. one more thing

anyone have an oracle cloud account and want to test our new docs?

https://github.com/coreos/fedora-coreos-docs/pull/741

they just merged this morning: https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-oraclecloud/

but AFAIK no one other than the author has executed the CLI commands directly

it's based on the docs I had made which I had tested on Oracle Cloud

but agree it would be good to test it again

I still have access to an account but not so much time to do it so if someone is interested I can help

ok that's all I had. sorry for the late topic

No problem! Thank you all!