Meeting started at 2026-06-02 14:00:11 UTC

The Meeting name is 'Fedora Atomic Initiative'

!hi

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

(we'll give folks ~5 minutes for roll call

(we'll give folks ~5 minutes for roll call)

!hi

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

!hi

Colin Walters: Colin Walters (walters)

a Matrix bot that can set a timer for agenda topics would be pretty cool... if anyone's bored :p

!hi

jligon: Jeff Ligon (jligon)

looks like the first topic is migration?

yup! I'm giving more folks a moment to come in

!hi

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

does anyone know if there was any discussion on the coreos side to migrate to forgejo?

Looks like we've got quorum! Please don't feel shy to add your name to the roll call after we move on and join the conversation. Meanwhile...

I would like to note that we also have an `atomic` org in the Fedora Forge staging instance.

!hi

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

(I guess general migration)

!hi

I think we can start migrating docs and issues for example, like we did with Atomic Desktops.

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

yes, that's probably what we should start with.

and then setup a test repo in the staging instance for Konflux?

Joel asked in https://forge.fedoraproject.org/releng/tickets/issues/13341 to get an account for Konflux

Hristo Marinov: do you want to help with the docs and issues migration?

Yes, but i will likely need sufficient permissions for that.

(side note: I'm going to be trying to use the bootc this week bot workflow here, so don't be surprised about different emoji reactions from me. Not sure if it will work, but giving it a shot)

I can do the repo migrations and then we'll need small fixes here and there

If you initially migrate the repos I can open PR after that.

Is there a summary of atomic desktops side of this? is any of that wired up to konflux?

If you initially migrate the repos I can open PRs after that.

If you want to do a PR for https://forge.fedoraproject.org/atomic/.profile/src/branch/main/README.md, that would be great too

For the atomic desktops, we are not yet using Konflux for builds. The docs & issues repos are not tied to Konflux AFAIK

I will do it.

so is the atomic namespace a location for all things related to bootc? or do we have some kind of definition that defines atomic?

the Konflux integration is blocked because of the missing Konflux SA/token

jligonhttps://forge.fedoraproject.org/council/tickets/issues/569

(bootc builds of the atomic desktops in progress in https://forge.fedoraproject.org/atomic-desktops/config/pulls/764, waiting on Konflux setup)

as soon as I have this token, I'll setup the pipelines in the fedora-bootc Konflux tenant

There are a bunch of repos in https://gitlab.com/fedora/bootc. Which one depend on Konflux? Should we migrate everything (and maybe archive some?)

jligon: I think the bootc eln work would/should definitely find a place in the atomic org

Yes, and I would like to actually move https://gitlab.com/redhat/centos-stream/containers/bootc here too (there's been almost no movement on konflux+centos AFAIK) and we do need it maintained

I'm hoping the eln work flows into that

I'd argue to move anything that needs a home; it's not like this is a situation where we can only move things once. If something moves and then we realize it needs a new org on the Forge, we can move it again later

https://gitlab.com/fedora/bootc/base-images

AFAIK

https://gitlab.com/fedora/bootc/compose-images

https://gitlab.com/fedora/bootc/tekton-catalog

sitting down with jcapitao and Stephen Gallagher tomorrow to discuss current status of fedora-eln

Is there anyone on the CentOS side that I need to get in touch with to let them know we're moving it? or is this the same group of maintainers? (I honestly don't know, but I can get Shaun to help me find the right people if you need me to)

OK so we'll hold on migrating those but we can migrate the rest

Once the issues are migrated, might be good to do a cleanup session? maybe on a video call?

To be honest, I am not sure how we use these issues, ie who looks at them etc ...

We've got our video session in 2 weeks

Maybe we should have a meeting tag, to discuss them during these calls?

calls/meetings

Once we move the issues repo I can start help maintain it.

is that something we could use coreos-agent-tools to start triaging? or a fork of coreos-agent-tools for bootc infra?

What else on the migration? Any concerns or extra stuff we haven't talked about?

The CI setup is also a bit in progress right now in the new forge. I'm tracking things in https://forge.fedoraproject.org/atomic-desktops/tracker/issues/114 for the atomic desktops. Konflux should do most of the CI but for the reset this is a bit in-progress

We would notably need https://forge.fedoraproject.org/forge/forge/issues/568 if we want to do testing with testing-farm

I *think* that what is currently used to test the bootc images? I don't remember

https://gitlab.com/fedora/bootc/tests/bootc-workflow-test

wow, a whole lot there

any reason to have atomic-desktops- specific runners?

The runner setup in the new forge is super manual so they are org specific by default

https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/openshift-apps/forgejo/runners/production

Clément also linked https://docs.fedoraproject.org/en-US/forge-documentation/oci_image_pipeline/ which seems to be doing something related to this too...except on codeberg (???)

Also they need to be privileged for building container images.

They have a set of default VMs for the runners but they are limited in ressources and unprivileged workflosw

Yeah, the usable disk space is only 13G.

i think it'd be nice to try to reuse konflux for CI jobs here too

Before we found out that testing-farm could be an option, we started requested privileged runners

once we have Konflux, yes!

but for the atomic org, definitely

(for the atomic desktops I needed something now as we lost all CI about 2 months ago now)

as they shut down Zuul

I still think that having runners with sufficient disk space to build bootable container inages would be useful,

I still think that having runners with sufficient disk space to build bootable container inages would be useful.

I still think that having runners with sufficient disk space to build bootable container images would be useful.

(the thing with raw testing farm is that project has no container-related infrastructure by default which causes some nontrivial friction)

ok so as far as I understand jcapitao is driving the konflux wiring (thank you!!!). We could migrate the issues repos without blocking on that, but OTOH I think we have reason to believe that blocker should be fixed in O(weeks) hopefully and could try to just do it at once?

Once we migrate the docs and issues repos, I think we need few small fixes for the docs. The issues will likely work right away.

It would make sense to move the docs, though, and anything that doesn't require Konflux wiring. Do the process, make sure we're not missing steps or have anything wonky, etc. It would give us room to work on things without waiting

OK that makes sense, is https://docs.fedoraproject.org/en-US/atomic-desktops/ already generated from https://forge.fedoraproject.org/atomic-desktops/docs ?

yes

Most of the docs repos are already migrated to Fedora Forge.

https://forge.fedoraproject.org/docs/docs-fp-o/src/branch/prod/site.yml#L78

I don't remember the status for translations however

AFAIK, the team is working on it.

3-minute warning

https://communityblog.fedoraproject.org/fedora-documentation-translations-not-available-from-march-4th-2026/

ok, time to close out

thanks for coming! let's keep chatting in #bootc:fedoraproject.org