#meeting-1:fedoraproject.org log

<@aaradhak:matrix.org>

16:30:10

!startmeeting fedora_coreos_meeting

<@meetbot:fedora.im>

16:30:13

Meeting started at 2025-06-25 16:30:10 UTC

<@meetbot:fedora.im>

16:30:13

The Meeting name is 'fedora_coreos_meeting'

<@aaradhak:matrix.org>

16:30:36

Hello Everyone !

<@aaradhak:matrix.org>

16:30:37

!topic roll call

<@siosm:matrix.org>

16:30:41

!hi

<@zodbot:fedora.im>

16:30:43

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

<@marmijo:fedora.im>

16:30:46

!hi

<@zodbot:fedora.im>

16:30:48

Michael Armijo (marmijo)

<@nemric:relativit.fr>

16:30:48

hello :)

<@jbtrystram:matrix.org>

16:31:58

!hi

<@zodbot:fedora.im>

16:32:00

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

<@hricky:fedora.im>

16:32:01

!hi

<@zodbot:fedora.im>

16:32:03

Hristo Marinov (hricky) - he / him / his

<@tlbueno:fedora.im>

16:32:26

!hi

<@zodbot:fedora.im>

16:32:27

Tiago Bueno (tlbueno) - he / him / his

<@aaradhak:matrix.org>

16:33:21

Lets wait couple of more minutes and we can start

<@dustymabe:matrix.org>

16:33:27

!hi

<@zodbot:fedora.im>

16:33:29

Dusty Mabe (dustymabe) - he / him / his

<@nemric:relativit.fr>

16:33:36

!hi

<@zodbot:fedora.im>

16:33:37

Emeric Chassagne (nemric)

<@jlebon:fedora.im>

16:33:48

!hi

<@zodbot:fedora.im>

16:33:49

None (jlebon)

<@aaradhak:matrix.org>

16:34:37

Alright, I think we can start now

<@aaradhak:matrix.org>

16:34:38

!topic Action items from last meeting

<@aaradhak:matrix.org>

16:35:54

I dont see any action items from our last meeting. However, we can follow up on the topic of schedule of the community meeting - https://github.com/coreos/fedora-coreos-tracker/issues/1972

<@dustymabe:matrix.org>

16:35:59

Note I also want to bring up https://github.com/coreos/fedora-coreos-tracker/issues/1972 today (/me adds the `meeting` label back to it)

<@marmijo:fedora.im>

16:36:11

I believe there was one action that I didn't officially designate. It was for dusty to create ^^

<@marmijo:fedora.im>

16:36:46

I should have just left the meeting label on that issue!

<@aaradhak:matrix.org>

16:36:51

I see that the majority of votes is to move the meeting one hour earlier

<@mnguyen:fedora.im>

16:37:29

!hi mnguyen

<@zodbot:fedora.im>

16:37:31

Michael Nguyen (mnguyen)

<@dustymabe:matrix.org>

16:37:33

yeah. let's do it under a !topic heading

<@aaradhak:matrix.org>

16:38:24

!link https://github.com/coreos/fedora-coreos-tracker/issues/1972

<@aaradhak:matrix.org>

16:38:24

!topic consider different time for community meeting

<@dustymabe:matrix.org>

16:39:19

thanks travier for updating the emoji for the 3rd option. I forgot emoji's were limited to like a handful on github :)

<@dustymabe:matrix.org>

16:40:10

It looks like we have most votes for the `Move meeting one hour earlier (15:30 UTC)` option

<@dustymabe:matrix.org>

16:40:40

I can't see who all voted for it, just the first 4 or so people.

<@aaradhak:matrix.org>

16:43:08

If the decision is to move the meeting one hour earlier, do we me make a proposed for the new schedule ?

<@tlbueno:fedora.im>

16:43:15

I was about to start to participate into the rotation to run the meeting but due the time change I will not be able to.

<@tlbueno:fedora.im>

16:43:15

I can't attend at the proposed new time but I am ok to read the metting chat later.

<@dustymabe:matrix.org>

16:43:16

yeah. I can do it.

<@dustymabe:matrix.org>

16:43:36

Sorry Tiago Bueno :(

<@dustymabe:matrix.org>

16:43:58

if it makes you feel any better when DST kicks in again in the fall the meeting will effectively move again

<@dustymabe:matrix.org>

16:44:43

Also, keep in mind that we're open to other proposals if anyone wants to make them. There may be an even better time; this was just one sample poll.

<@tlbueno:fedora.im>

16:44:58

np at all dustymabe

<@tlbueno:fedora.im>

16:44:58

I hope the the time move again I will jump in :)

<@dustymabe:matrix.org>

16:45:05

!proposed With a vote talley of 13 👍 for "Move meeting one hour earlier (15:30 UTC)" and 2 👎️ for "Keep meeting at current time (16:30 UTC)" and no votes for "I can't make it at either of those times" we will move the meeting time to 15:30 UTC.

<@aaradhak:matrix.org>

16:45:21

<@tlbueno:fedora.im>

16:45:25

I hope when the time move again I will jump in :)

<@tlbueno:fedora.im>

16:45:25

np at all dustymabe

<@jbtrystram:matrix.org>

16:45:43

In my previous team we had community meetings alternating each week to accomodate Americas then APAC/EMEA

<@marmijo:fedora.im>

16:46:15

<@siosm:matrix.org>

16:47:10

<@jlebon:fedora.im>

16:47:17

timezones are hard... but yeah +1

<@jbtrystram:matrix.org>

16:47:38

<@tlbueno:fedora.im>

16:47:42

<@dustymabe:matrix.org>

16:48:06

!agreed With a vote talley of 13 👍 for "Move meeting one hour earlier (15:30 UTC)" and 2 👎️ for "Keep meeting at current time (16:30 UTC)" and no votes for "I can't make it at either of those times" we will move the meeting time to 15:30 UTC.

<@dustymabe:matrix.org>

16:48:57

anybody want to take an action to update the tracker repo repo and the fedocal entry in Fedora apps?

<@marmijo:fedora.im>

16:49:25

I would, but I'm about to head OOO :)

<@aaradhak:matrix.org>

16:49:56

I can update it.

<@aaradhak:matrix.org>

16:51:01

I will add it as an Action item

<@aaradhak:matrix.org>

16:51:15

Lets move on to the next topic

<@aaradhak:matrix.org>

16:51:42

!link https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html

<@aaradhak:matrix.org>

16:51:42

!topic Review Fedora 43 Release Schedule

<@aaradhak:matrix.org>

16:52:22

The deadline for changing infrastructure is today but I believe we dont have any infra changes.

<@aaradhak:matrix.org>

16:53:01

There is a System Wide Changes deadline approaching next for July 1

<@aaradhak:matrix.org>

16:53:20

my bad, it is Changes requiring mass rebuild

<@aaradhak:matrix.org>

16:53:31

my bad, it is Changes requiring mass rebuild for July 1

<@tlbueno:fedora.im>

16:53:40

and system wide as well

<@siosm:matrix.org>

16:53:49

both yes

<@aaradhak:matrix.org>

16:53:50

also , Changes requiring mass rebuild for July 1

<@siosm:matrix.org>

16:54:28

We want to submit a self contained change for https://github.com/coreos/fedora-coreos-tracker/issues/1468 so we have until 2025-07-22 (or a week before to give some times to discussions) to do it

<@leorize:envs.net>

16:55:22

!hi

<@zodbot:fedora.im>

16:55:24

leorize (leorize) - he / him / his

<@jlebon:fedora.im>

16:55:31

there's also a change for the container native path currently in draft

<@aaradhak:matrix.org>

16:58:30

ok, we have some time to discuss these changes.

<@aaradhak:matrix.org>

16:58:50

May be we can move on to the next topic

<@aaradhak:matrix.org>

16:59:07

!topic Implement Oracle Cloud Infrastructure support

<@aaradhak:matrix.org>

16:59:07

!link https://github.com/coreos/fedora-coreos-tracker/issues/1967

<@aaradhak:matrix.org>

16:59:56

Looks like "alaviss" wanted to discuss about this in the community meeting.

<@leorize:envs.net>

17:00:24

that's me, I got the ignition and afterburn portions of this merged, and would like to have new releases issued for them

<@aaradhak:matrix.org>

17:01:11

I am not sure if he is here today. Jonathan Lebon would you like to introduce this?

<@siosm:matrix.org>

17:02:31

You should be able to directly open issues with the release checklist type to ask for a new release in both repos

<@dustymabe:matrix.org>

17:03:14

Does anyone know if we already had plans to do releases soon for those?

<@leorize:envs.net>

17:03:15

I wasn't sure if that's for maintainers only and was directed to join the meeting 😄

<@jlebon:fedora.im>

17:03:21

I'm not sure if we had releases planned soon though there are some fixes that would be good to get out anyway

<@jlebon:fedora.im>

17:03:21

leorize: Hi! Really appreciate you jumping in and sending patches.

<@jlebon:fedora.im>

17:03:33

travier: yeah, i think that's more for folks doing releases

<@leorize:envs.net>

17:04:27

I'm not in much rush for those changes to be released, but it'd simplify testing the guestfish instructions

<@jlebon:fedora.im>

17:05:04

though i do wonder if we still want to follow the emerging flow for this or just produce disk images there too

<@jlebon:fedora.im>

17:05:30

we pivoted on that recently with other platforms too i think

<@dustymabe:matrix.org>

17:05:40

I would vote for disk images.. OCI is larger than most other cloud providers we provide images for

<@jlebon:fedora.im>

17:06:00

heh, good point

<@leorize:envs.net>

17:07:14

does this mean I should open a new issue to use the new platform flow, or will this still be "emerging" but with an extra bit?

<@dustymabe:matrix.org>

17:07:35

Maybe we could get someone new to learn the release process for ignition/afterburn to help ease the burden on steven/yasmin. Tiago Bueno maybe something you'd be interested in?

<@dustymabe:matrix.org>

17:07:52

would also be cool to get some of the flatcar folks to join in at least doing ignition releases

<@jlebon:fedora.im>

17:08:15

leorize: i think we can copy/paste and keep the same issue

<@tlbueno:fedora.im>

17:08:30

yes dustymabe I am up to do the igntion/afterburn release for sure.

<@dustymabe:matrix.org>

17:09:07

leorize: yeah I converted the proxmox issue into a full platform by just copying in the new template and updating it.. and then making a comment lower down.

<@tlbueno:fedora.im>

17:09:10

I can get in touch with steven/yasmin and check if there is any scheduled one and mention the need

<@dustymabe:matrix.org>

17:09:19

leorize: yeah I converted the [proxmox issue](https://github.com/coreos/fedora-coreos-tracker/issues/1652) into a full platform by just copying in the new template and updating it.. and then making a comment lower down.

<@leorize:envs.net>

17:09:32

the new platform checklist sure is long 😅

<@nemric:relativit.fr>

17:10:03

:/ not sure to well understand, you're looking for folks that could release fcos every 2 weeks ?

<@dustymabe:matrix.org>

17:10:29

Nemric: in this case we're talking about upstream releases for Ignition and Afterburn (not FCOS specifically)

<@dustymabe:matrix.org>

17:11:04

but TBH we should try to open it up so more people are able to do actual FCOS releases.. We have a checklist for those too :)

<@jlebon:fedora.im>

17:11:32

leorize: most of it is quite straightforward, but yeah i wouldn't expect you to do all the pieces either :)

<@nemric:relativit.fr>

17:11:40

well, I'm not opposed to give it a try ^^

<@dustymabe:matrix.org>

17:11:46

or.. if anyone is interested.. we could really use extra/new maintainers on some of our projects. If there's one anybody would be interested in

<@jlebon:fedora.im>

17:11:56

related to https://github.com/coreos/fedora-coreos-docs/issues/650

<@aaradhak:matrix.org>

17:14:14

I would like to contribute something to this

<@aaradhak:matrix.org>

17:18:24

Is there anything else to be discussed on the Oracle cloud infra support?

<@leorize:envs.net>

17:19:12

travier: do you mind handling the docs for OCI? I'm not that big of an user and don't know much about how their networking works

<@siosm:matrix.org>

17:21:14

I think I already wrote the networking part in the docs PR?

<@siosm:matrix.org>

17:21:36

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

<@leorize:envs.net>

17:23:03

that's great then, I'll look into getting that done once we have ignition/afterburn in testing

<@aaradhak:matrix.org>

17:24:07

Assuming that there is no other question, lets move on to the next topic

<@aaradhak:matrix.org>

17:24:19

!link https://github.com/coreos/fedora-coreos-tracker/issues/1934

<@aaradhak:matrix.org>

17:24:19

!topic tracker: Fedora 43 changes considerations

<@marmijo:fedora.im>

17:24:46

I updated the list this morning and one new change came through in each section

<@aaradhak:matrix.org>

17:25:35

Thanks for running the script marmijo , we can run through the new changes.

<@aaradhak:matrix.org>

17:26:45

https://fedoraproject.org/wiki/Changes/RPM-6.0

<@aaradhak:matrix.org>

17:26:45

111. RPM 6.0

<@aaradhak:matrix.org>

17:26:54

https://fedoraproject.org/wiki/Changes/RPM-6.0

<@aaradhak:matrix.org>

17:26:54

111 - RPM 6.0

<@marmijo:fedora.im>

17:27:28

We've already discussed this in a previous meeting. I'll open the tracker issue for it before I leave today. We can move to the next one.

<@siosm:matrix.org>

17:27:55

it's almost time so maybe this would be for the next meeting

<@marmijo:fedora.im>

17:28:17

I'll open the issue and add the `meeting` label to it

<@aaradhak:matrix.org>

17:28:32

sounds good. lets move to open floor

<@aaradhak:matrix.org>

17:28:37

!topic Open Floor

<@siosm:matrix.org>

17:29:02

if folks are interested in taking a look at those changes in advance and posting their ananlisys in the issue, that would speed things up for next tiume

<@siosm:matrix.org>

17:29:12

if folks are interested in taking a look at those changes in advance and posting their analysis in the issue, that would speed things up for next time

<@marmijo:fedora.im>

17:30:19

!info The community meeting on 2025-07-02 will be one hour earlier, at 15:30 UTC.

<@marmijo:fedora.im>

17:30:57

!info Starting on 2025-07-02, the community meeting will be moved to one hour earlier, at 15:30 UTC.

<@aaradhak:matrix.org>

17:31:38

I think we ll wrap it up if there is nothing else.

<@aaradhak:matrix.org>

17:31:48

Thanks everyone for participating!

<@aaradhak:matrix.org>

17:31:52

!endmeeting

<@aaradhak:matrix.org>

17:31:52