Meeting started at 2026-07-29 15:30:22 UTC

The Meeting name is 'fedora_coreos_meeting'

!hi

!hi

!hi

!hi

!hi

!hi

!hi

I think the bot that announces our names might be not working right now

hopefully it's recording attendance anyway

It has PTO maybe

!hi

yeah the bot is broken, people over at the main meeting chat are having issues too (sorry for budging in)

!hi

What is the protocol for this, should we take notes by hand for the community post / email ?

For the action item: we had that meeting about /boot partition size and now need to go off and perform some tests to see what actual failure scenarios we have

Angel Cervera Roldan: that was my idea, I'll just format the community post/email manuall if the meetbot doesn't come back up soon. I think it's actively being worked on

Attended by myself, Angel Cervera Roldan, Yasmin Valim de Souza, dustymabe , Timothée Ravier

I suppose we can go to open floor unless someone has a topic to bring up now

Quick one

The meeting that is - I don't have any topics

The QE Team asks if we're going to have CoreOS test days for Fedora 45. See https://forge.fedoraproject.org/quality/tickets/issues/916#issuecomment-1072055.

Nice.. Let's organize one?

Hristo Marinov: We will do a test day(s) for Fedora 45

Hristo Marinov: We will do a test day(s) for Fedora 45

We were a bit late/rushed in scheduling the test day for Fedora 44, so maybe we can organize it a bit sooner this cycle.

I'm looking forward to the nice CoreOS cartoon images from Yasmin Valim de Souza

I already have experience so I can participate.

We usually hold the event after the beta release, which is slated for `2026-09-15`

Sorry, could not get info from FASJSON (code 401)

Hristo Marinov++

Sorry, could not get info from FASJSON (code 401)

I can help with it too!

Sorry, could not get info from FASJSON (code 401)

Sorry, could not get info from FASJSON (code 401)

Sorry, could not get info from FASJSON (code 401)

I can't give you a cookie apparently, but thank you Hristo Marinov for volunteering and for all your help with CoreOS

Sorry, could not get info from FASJSON (code 401)

ugh

Thanks Hristo Marinov :)

Sorry, could not get info from FASJSON (code 401)

Sorry, could not get info from FASJSON (code 401)

Anyway, Beta Release is scheduled for 2026-09-15 and final freeze on 2026-10-06. That gives us 3 weeks to hold the test day(s) event.

I can open the ticket in the tracker.

Sounds great, maybe we can try to nail down a date soon. Perhaps 2026-09-21 for the live sync call? I feel like we typically do it on a monday

Of course, beta release could slip so we'll have to be ready to adjust

I think it give us plenty of time to test and report eventual problems

We can set this date and if something happens to beta release schedule we can change

+1

+1

+1

+1

On a different topic, maybe Peyton Robertson wants to bring up https://github.com/coreos/afterburn/pull/1264? Seems we're close to merging

Maybe one more look from spresti

on another note Peyton Robertson: I'm interested to know if the butane change in ignition is something flatcar is interested to also use (IIRC from our original discussions you guys were on board with the change).

on another note Peyton Robertson: I'm interested to know if the butane change in ignition is something flatcar is interested to also use (IIRC from our original discussions you folks were on board with the change).

hricky gave a cookie to ydesouza. They now have 15 cookies, 7 of which were obtained in the Fedora 44 release cycle

Yes!! Thank you to everyone who has taken a look, I'm addressing the CodeRabbit comment right now but otherwise I think we should be super close to merging / ready to merge after that!

Is this the one about adding butane generation into ignition? I've honestly not looked into it deeply, but I can do that this week! Is there something specific you're thinking about in regards to a Flatcar use case?

We would be happy to pass it along to the Flatcar folks and get their input!

basically this is the change: https://fedoraproject.org/wiki/Changes/IgnitionNativeButaneSupport

TL;DR merging butane functionality into Ignition itself, which means users don't have to do the "convert butane -> Ignition" step when provisioning.

They can just pass the butane config directly.

Nice! I will pass this along to the Flatcar team and see if they have any feedback/input😀

I see that code rabbit recently got enabled for afterburn - but could we prevent it from (jokingly) insulting people opening PRs: https://github.com/coreos/afterburn/pull/1264#issuecomment-5120164060

It generates text in the comment before it's had a chance to complete the review

I think that the PR itself should disable that

rapneset: yeah that doesn't seem appropriate for a professional code review. I can understand the sarcasm between friends, but that's no useful in any way in our repos.

ooops, I meant this one: https://github.com/coreos/afterburn/pull/1292

Ok nice so it will be fixed

I believe that should disable those things, thanks Yasmin Valim de Souza!

Very odd default behaviour

Thanks Yasmin Valim de Souza!

Maybe we could make a `coreos/coderabbit` repo with a default config that disables these things by default, so that if we enable coderabbit on a repo before adding the repo-specific config, it wont add a lot of noise to open PRS

And start enabling coderabbit on more of our repos

hmm. should we use repo-templates for this purpose?

I don't think we can :)

Coderabbit will look for a repo named coderabbit if there is no .coderabbit.yaml file in the repo itself

but why can't we put a .coderabbit.yaml file (via repo-templates)?

but tbh maybe a coderabbit repo in an org is better (prevents having to sync everything around

And each repo has its own prompts, and no way of merging two configs (global + project specific prompts) that I could find

Maybe there is a nice way to do it, but it could become a lot of work to deal with pulling in changes from the repo-templates, and then having to have repo-specific modifications on it

And each repo has its own prompts, and no way of merging two configs (global + project specific prompts) that I could find (I really think coderabbit should be able to merge global and project specific configs for this case...)

I'm happy with a coreos/coderabbit repo

though unfortunately my experience with coderabbit so far is: "I liked gemini way better" :)

Yep...

I agree, I think that maybe once we reduce the spam it produces it could be nice. But it has very questionable defaults for a professional setting imo

I'll close out in the meeting in a minute if there isn't anything else to discuss