Meeting started at 2024-02-28 16:37:56 UTC

The Meeting name is 'fedora_coreos_meeting'

pwhalen: in https://calendar.fedoraproject.org/IoT/#m9244 i see it as `#meeting`. was that meant to be a different room?

!hi

Steven Presti (spresti)

!hi

Michael Nguyen (mnguyen)

!hi

Michael Armijo (marmijo)

!hi jbtrystram

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

Since we are slightly delayed I will start with the ...

!hi

Joe Doss (jdoss)

straight away

!hi

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

!hi

None (jlebon)

apiaseck: you can view action items here https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-02-21/fedora-coreos-meeting.2024-02-21-16.34.html

Oh, thanks spresti

Jonathan Lebonthanks! Indeed we were in the wrong place

If I recall fifofonix is out or not going to be able to do this last week

so we can re-action it

As far as I remember dustymabe mentioned it... anyone would like to introduce it?

(AFAIK Dusty's not around today)

yeah, let's just re-action that one

i don't think there's any expectation that this happens soon as he made it clear

Sorry if I've re-actioned that one too fast...

Nope that was good

Cool, let's move to another subject

I can't see Yasmin around here either, anyone to touch base on this subject?

i can speak to that

Thank you!

a while ago, butane was called fcct. we pushed out releases to quay.io/coreos/fcct.

when we renamed to butane, we kept the fcct container repo up to date during releases to not break people

this ticket is asking to stop updating fcct entirely and formally turn off that repo

.hi

100! would be down for that.

Can we see how many pulls its getting?

spresti: good question, let me check

looks like a couple per day

Can you see the tag that is pulled? or is it not specific

Sorry for being silly here, where do we see stats regarding number of pull's on quay?

e.g. 4 pulls yesterday, 3 pulls the day before

I think you need the correct perms

so really not much apiaseck there's a "Logs" tab but yeah, you might not have access

We probably should send a note about turning it off, with a deadline for it. So people may know

Renata Ravanelli: my thoughts as well

Thanks.

We have the info of the repo say its depricated for a while.

https://quay.io/repository/coreos/fcct?tab=info

note also we ship an `fcct` compat symlink in the butane package

ah, I was not aware of that.

Ok

that would make sense though,

so

that one is obviously trivial to maintain, though we could also take the opportunity to stop doing that

I prepose we make an update to the butane package, stating the next version is the last with the compat in the release notes. and then just drop it after the next release?

Is there a reason why we have this fcct symlink?

That sounds like a good plan to me. Is it enough to communicate it over the release notes?

I can also sent a message in the fcos list

Renata Ravanelli: for the same reason: compatibility :)

s/I/We

yeah, i think a list email would be good. now, we *could* actually combine this with the f40 communications email

sounds good to me

it's not a perfect match because butane is an upstream project with its own release schedule, but... it's easier to communicate if it's bundled with it

so an action to update release(upcoming release) with dropping of fcct compat, and communicate it in the f40 communication email?

+1

+1

+1

+11

+1

spresti: well, that depends on timing. we can't remove it from butane before we communicate it

+1

Ah yes sorry, my english was not well formed, yes that is what I ment; to communicate that we are dropping compat

so i would phrase it as e.g. "remove the fcct compat symlink from the pkg and quay.io update from the release checklist in the butane release following the f40 rebase"

+1

+1

If we agree to the above I will set this as an action item.

Any other votes?

+1 on the new wording

+1

+1

Really quick what do we need to do to add it to the communication f40?

+1

Thank you all for voting

apiaseck: i think it's more a proposal than an action, no?

:) Offcourse it is heh

spresti: we have a tracker issue to track things to include when we write up that email

!proposed We will remove the fcct compat symlink from the pkg and quay.io update from the release checklist in the butane release following the f40 rebase

https://github.com/coreos/fedora-coreos-tracker/issues/1655

apiaseck: you might want to undo first :)

!proposed is not a thing in matrix

try "!undo" twice, and then redo the agreed

Ah, thanks - I enjoy this :D

!undo

undo once i thing since the proposed was not registered

!undo

The bot is not picking up the undo :/

jbtrystram: good point. though hmm... doesn't seem like that's a verb actually. i swear i thought this worked in the matrix bot too

Bot, please be kind to me today

well that was un-eventful halp is not halping

anyway, i guess we can just ignore that action item in the next meeting

+1

Ok, let's move to the other topic.

wait

you need to !agreed on the proposal

i guess we should've mentioned that we'll communicate it as part of the f40 rebase; we can add that directly in the ticket when you post that agreement

Here's the link to the latest topic !link https://github.com/coreos/fedora-coreos-tracker/issues/840

Here's the link to the latest topic

Jonathan Lebon: Would you like to introduce this one as well?

i think let's skip that one. this is linked to the swap on zram discussion from last week as we previously agreed we'd bundle the changes together: https://github.com/coreos/fedora-coreos-tracker/issues/859#issuecomment-867125032

i've removed the meeting label

Ok, thank you

Can we move to the last topic for today, or is there any action before that which I'm missing?

gursewak: Would you like to introduce this one?

looks like dusty tagged this in, but he's not here. maybe let's wait until he's back for that one.

+1

If anyone asks, that's ok with me...

+1

I think gursewak is out today

Cool, let's move to open floor

Anything from anyone?

not from me

nothing from my side either. thanks as always to folks cutting releases

(both upstream project releases, and FCOS releases)

Thanks all

Thanks apiaseck for running it today

With that said, I will close the meeting. Thanks all for the conversation! Hope to see you here again next week!

Thank you apiaseck for running it!

Thanks apiaseck , thanks all!

Thanks for running apiaseck ! Thanks for coming everyone

thanks all, thanks apiaseck!