Meeting started at 2026-07-07 14:01:36 UTC

The Meeting name is 'Fedora Atomic Initiative'

!hi

nimbinatus: Laura Santamaria (nimbinatus) - she / her / hers

!hi

John Eckersberg: John Eckersberg (jeckersb)

!hi

dustymabe: Dusty Mabe (dustymabe) - he / him / his

!hi

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

!hi

Sean Thrailkill: Sean Thrailkill (snthrailkill)

!hi

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

!hi

jmarrero: Joseph Marrero (jmarrero)

!hi

jligon: Jeff Ligon (jligon)

so I don't have any specific topics in mind today as I've been heads down elsewhere, but there's been a lot of discussion in the channel. Does anyone have topics they'd like to bring to the table early, or shall I just open the floor and we go at it?

Just a quick update on the unified pipeline it looks like we got access now: https://forge.fedoraproject.org/infra/tickets/issues/13443 I will reach out to a couple of interested parties about migrating the fedora-bootc repo.

nimbinatus has already given cookies to jmarrero during the F44 timeframe

> But even in the bootc case, using a boot media from OS A to install OS B is not really a good experience.

I'd like to continue the thread that Timothée Ravier and I had yesterday about

if theres time

let's get into it, then :)

!hi

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

Having a generic bootc installer for any bootc host isn't a bad thing in my mind, but the idea that a iso installs what is on it seems like something most people expect

so why not have a neutral installer that installs anything?

SIG membership should be fixed for the new forge org. Let me know if you need access

!hi

jcapitao: Joel Capitao (jcapitao) - he / him / his

jligon: so net installer ?

The unified pipeline access > Hum, that's not the case

nimbinatus has already given cookies to siosm during the F44 timeframe

only the access to the org on the forge is readt

only the access to the org on the forge is ready

I see only four members in https://forge.fedoraproject.org/atomic.

jligon: any installer can be a "net installer" you just point it at the thing you want to install instead of it installing what's baked into it.

agreed, and I want anaconda's gui to support pointing it a bootc repo

anyone that got granted membership has to log out / log in again to be added as member

I think no one disagree with that

(s/bootc repo/registry/)

Yeah, after I log out and log back in, it seems to be fine. Sorry for the noise.

logged in, not a member

No worries!

https://forge.fedoraproject.org/org/atomic/members shows you as a member, jligon ?

oops, looking at atomic desktops, my bad

so on the installer discussion... are we needing to open a ticket on Anaconda asking for the ability to have a selector?

or look for an existing ticket for it

!hi

Clément Verna: Clement Verna (cverna) - he / him / his

I'll be honest that I've been eyeballing this with the thought of trying to get it to work in my free time (whatever that means): https://github.com/projectbluefin/bootc-installer

I don't know yet if that can take just the image or if it needs an ISO though

there's also `bootc install to-disk`, but I think that's still a big leap for someone just wanting to do an install. GUIs would be the way to go imho

I think installers are not the most important thread? we were talking about the pipeline which is i think still blocked on https://forge.fedoraproject.org/releng/tickets/issues/13341

there's two conversations happening here at once :D

happy to table mine, since everyone already agrees with me

sounds good

let's hop

Anything specific on the installers/Konflux service account? Or just wanting to talk about the blockers and figure out what's needed?

TBH I'm lost with the last solution

> this would mean that all the admins of all the namespaces where this token/secret is created would have access to all the repos.

that was our concern

but it looks like there is no better solution AFAIU

So I guess we should have to create one mailing list for each org with the owners on it, then create one konflux fas account from that mailing list and then create a token for that account.

So I guess we whould have to create one mailing list for each org with the owners on it, then create one konflux fas account from that mailing list and then create a token for that account.

Ideally we don't create another group for the email and account and reuse the existing owner group

This way only owners can get the token but at the same time they already have full access to all the repos anyway

sounds good

I'll update the ticket with that proposal

sad that we are back to the workaround solution we had at the beginning :/

but I don't see another immediate option (and we can always revisit if one come up)

agreed :( maybe there is someone on infra team we can ask just to make sure theres no better workaround available?

like continue with our workaround but open a ticket just in case

yep, I think all the stakeholders are in the thread

So we should make sure that ticket doesn't get closed (so the feature request is tracked) when the workaround is in place

yes I'll handle that as a follow-up once the current ticket is addressed

Let's move to the next topic?

sorry! door-to-door person interruption

(and don't forget to watch the tracker repo on the new forge as Forgejo does not watch repos by default)

do we have another topic?

We got approval to use the Atomic name

yup! that was at Council last week

Maybe we should create a proper SIG (we have most of it already, I think we just need a new Wiki page)?

:D I think that would be a good move, personally.... let me set up meetbot; one sec

so, what do folks think?

As part of this can we get a new subsection of the calendar? i.e. not under SIGs - when I subscribe to a calendar I don't want to see all SIG meetings, just the ones I'm interested in. Right now it's: https://calendar.fedoraproject.org/SIGs/#_

as opposed to CoreOS, which is: https://calendar.fedoraproject.org/CoreOS/

I'll be honest that I don't really know much about how getting a calendar works, but I can figure it out

I can't picture why we couldn't

probably an infra ticket.. if it's self service they will let you know

if you can use a link for the group then any new meetings that get added will auto show up

yeah. the reason for the frustration here is I've added this specific meeting to my cal a few times, but any time it gets deleted/recreated (different time or different details) it gets a new calender ID/link and all of a sudden it's missing from my calendar.

so I could use the group link for SIGs today, but I don't care much about seeing meeting info for ELN and riscv

yeah, that makes sense. And tbh, I would think that, once things get a bit more centralized, you'll want meetings on Konflux infra, on different Atomic Desktop variants, on general bootable topics, etc.

we've got about 5 minutes. Can I get a rough vote on who's interested in joining an Atomic SIG? Then we can parcel out what needs to get done (or I can get that process rolling for all of us). Reply with +1 or similar pls?

Just to get a sense of how interested folks are

+1

+1

+1

+1

not sure exactly what membership means here, but I'm interested in following the developments closely.

yup, I mostly am just asking in case someone tries to tell us we're too small or don't have enough interest

I'm interested :)

that's all I really needed 😁

+1

ok, so those are the three action items here that I can think of

+1 from me too (got side tracked)

belated +1 too :)

no worries!

ok, time to end. thanks for coming!