Meeting started at 2026-09-23 15:30:31 UTC

The Meeting name is 'fedora_coreos_meeting'

!hi

marmijo: Michael Armijo (marmijo)

!hi

Hristo Marinov: Hristo Marinov (hricky) - he / him / his

!hi

Tiago Bueno: Tiago Bueno (tlbueno) - he / him / his

!hi aaradhak

aaradhak: Aashish Radhakrishnan (aaradhak)

!hi

Cade: Cade Jacobson (cadejacobson)

!hi

Nemric: Emeric Chassagne (nemric)

It seems we are now past the beta release, and the next event will be `Retire FTI packages in NEW state` next Tuesday

There's not much for us to do until Final Freeze. Test week is still going on though!

Ah yes, in case someone missed that, I'll add the link for it

!hi

Yasmin Valim de Souza: Yasmin Valim de Souza (ydesouza)

Yasmine did share the link in coreos channel 😉

We already have a few tests, thanks everyone!

Yasmin did share the link in coreos channel 😉

If no one else has something to add about the key dates, we can get started with tracker topics

Thanks and feel free to reach us out in the channel if there is any questions about the tests :🎉

I'm running 2 f45 nodes, that don't really fit tests, but everything works as expected

I saw this a couple of days ago and added the meeting label. I personally like the idea, I think it would be great for CoreOS to be in the weekly report, was wondering how the community feels about it

It would basically mean that anything we send in the matrix channels could end up in a weekly report that is LLM generated but verified/read over by a human. If someone does not want to be in the newsletter, they would need to opt out.

Some context: https://forge.fedoraproject.org/atomic-desktops/tracker/issues/128

Thanks for that context, I had not seen that

My personal opinion is that it would be nice for CoreOS to have some more visibility, and in that way it would be nice to be in the newsletter. The LLM generated content is read over by a person, which I like much more than fully automated. However, someone new may join the coreos channel and not know that their data is being used for newsletters.

I like the idea but Timothée Ravier point about the matrix chats in Hristo Marinov link makse sense to me. Regarding the future people that will join in the channel, anyones knows is we could have some "welcome" message sent to the user that is joining explaining things like the data collected, maybe other things as well.

I like the idea but Timothée Ravier point about the matrix chats in Hristo Marinov link makse sense to me. Regarding the future people that will join in the channel, anyones knows if we could have some "welcome" message sent to the user that is joining explaining things like the data collected, maybe other things as well.

I don't have a strong preference either way. I think it's nice that the reporter asked before enabling the data collection. I'm all for it being read by a human, but is that always going to be the case?

Yes, I think the newsletter automatized could help just gathering data like important PRS and issues by our repos, but would be nice to have human eyes on that. To be honest, I think that we are all a little bit overwhelmed by things written by AI and would be nice to have some human writing something. I

Yes, I think the newsletter automatized could help just gathering data like important PRS and issues by our repos, but would be nice to have human eyes on that. To be honest, I think that we are all a little bit overwhelmed by things written by AI and would be nice to have some human writing something.

Tiago Bueno, that's a good idea to inform new users that way. maybe we could put it in the channel description as well

> I don't have a strong preference either way. I think it's nice that the reporter asked before enabling the data collection. I'm all for it being read by a human, but is that always going to be the case?

I am not sure if it will always be the case - we could ask. There is of course still a chance that mistakes go through, since someone(s) from coreos woud need to read over with context to be sure.

I do agree its nice that they asked.

I think as a start we can support including our meeting logs, Discourse posts and issue trackers. These are already public, structured and intended for official updates.

A while ago I did a bot to document stuff, its a private room and it is not running at the moment but I remember that the problem that I found to put in our own channel was about data.

The question I have is should we keep general #coreos chat out of the scraper or rely on explicit opt-ins / issue summaries instead?

Nice, I did not put our community meeting logs in the newletter. It's a good idea.

> These are already public, structured and intended for official updates.

I agree - this is a great start. I also think this does not need any sort of notice, as its a formal meeting that is being logged already. I think that for the CoreOS channel it would be best to defer the decision to another week when we have timothee/dusty/...

If there are no more opinions, we can move to the next topic

Thanks for bringing this up! I`ve been struggling a lot with the AI newsletter outputs.

Maybe when we have our newsletter ready, we can share it with the other newsletter. They can filter what they want from it, and no need for extra verifications.

Moving on to the next topic:

This seems to be a bug report by dustymabe. I am not sure what there is to discuss here, maybe someone else knows ?

This seems to be a bug report, with the meeting label added by dustymabe. I am not sure what there is to discuss here, maybe someone else knows ?

Maybe the meeting label was not intended or it was an FYI for the community.

I don't have much idea about that. Unless anyone has a better idea we should wait for dustymabe . Looks like it is requesting to pin the kernel version for next/testing.

I don't have much idea about that. Unless anyone has a better idea we should wait for dustymabe . Looks like it is requesting to pin the kernel version for next/testing. that is my understanding

I agree, we can wait. In that case, we can move onto the next and final topic before the open floor

wow ... I'm using cilium 1.20.2 on 2 f45 k7.2 nodes without issue 😕

sorry, I only have 1 f45 node in my cluster

This one is by marmijo, we started discussing this a couple weeks ago but did not finish, do we have any further updates ?

you should report back :)

No new updates right now. We're past beta release and in test week, and I saw we have a failed test reported due to one of the changes we're tracking. I'll try to look at that ASAP.

Thank you very much marmijo

It looks like it's now resolved following fifonix link in first post : https://github.com/cilium/cilium/issues/48016

Since there were no further updates, we are ready for the open floor

Hey team, just a quick reminder that we are in our Test Week! So it would be nice to have your participation!

We have all our information in our channel, but here is our most important links:

Wiki & Details: https://fedoraproject.org/wiki/Test_Day:Fedora_45_CoreOS

Log Results: https://testdays.fedoraproject.org/testday/27

We have all information in FCOS channel, but here is the most important links:

Wiki & Details: https://fedoraproject.org/wiki/Test\_Day:Fedora\_45\_CoreOS

Log Results: https://testdays.fedoraproject.org/testday/27

We have all information in FCOS channel, but here is the most important links:

Wiki & Details: https://fedoraproject.org/wiki/Test\_Day:Fedora\_45\_CoreOS

Log Results: https://testdays.fedoraproject.org/testday/27

I will give us a couple more minutes, and if there are no more open floor topics I will end the meeting 5m early.

Thank you very much everyone for attending! Enjoy the rest of your day!

thanks Angel Cervera Roldan