On 3/17/20 2:01 PM, Adam Williamson wrote:
> 3) CoreOS - CoreOS is just a *whole* other thing. It is not built like
> the rest of Fedora at all. It's not built as Pungi composes, whatever
> compose process it does have doesn't run alongside our other compose
> processes or output to the same locations, it's like a whole other
> product. It also doesn't seem to be terribly well documented (I can't
> find any detail on the wiki, docs sites, or any of the git repos I
> happen to know of) or even introspectable - for instance, ISO locations
> look like
> , but if you try and browse around that tree by visiting URLs like
> https://builds.coreos.fedoraproject.org/prod/streams/ , you just
> get 'Access Denied'. So if the process appears to have broken down and
> some poor monkey like me is left trying to help people figure out where
> they can get a 'Fedora CoreOS 32' image to try - it isn't very easy.
> Right now I simply have no clue if there is something you could
> reasonably call 'Fedora CoreOS 32 Beta' or a decent analogue of it.
You have reasonable points here. I do agree that the current state of integration
between Fedora CoreOS and the rest of Fedora is not quite complete. Part of the
reason for this is that we've been working hard on building Fedora CoreOS from
the ground up and getting it out the door. There are two things here worth being
1. Fedora CoreOS is today not composed by pungi on Fedora infra. It is composed
using coreos-assembler in CentOS CI. I think this fundamental difference
is the root to a lot of the mystery here surrounding FCOS. People integrated
into Fedora processes are familiar with pungi and how it works. OTOH, I'm
sure not many of us are familiar with coreos-assembler.
2. Fedora CoreOS follows a rolling release model, where by design, we don't want
people to care about whether they're on f31 or f32 (at least in principle).
For FCOS, the f32 update just goes out like any other update when we're ready
to do the cutover. Thus, sentences like "Fedora CoreOS 32" don't have quite
the same meaning as for e.g. Workstation or Server. That said, Fedora CoreOS
does have more streams than just stable and testing, and one of those streams
should be $((N+1))-based. So we definitely could have some marketing/banners/whatever
to point people at. Right now there is not yet a F32 based coreos, but there
will be soon as part of our `next` stream .
That said, we know there is work to do to make things better understood and more
predictable from the rest of Fedora's point of view. Note that there was a lot of
hard work to integrate and participate in more Fedora processes as Fedora Atomic
Host matured. Know that this work will come as we finish building out the more
foundational pieces of Fedora CoreOS. We have opened a discussion ticket  for
this in our issue tracker, which is where our meeting topics get sourced from and
our discussions generally take place.
This is a reminder our meetings are in UTC time and stay at the same
UTC time year round regardless of daylight savings time. Please check
your local time for 16:30 UTC and adjust any calendar invites you may
Note that you can subscribe to the community meeting on our CoreOS
calendar in FedoCal (https://apps.fedoraproject.org/calendar/CoreOS/#m9437)
by clicking the `iCal export` link and importing that into your calendaring
software of choice.
Also you can request to be pinged before the meeting starts each time by
adding your name to this list: https://github.com/coreos/fedora-coreos-tracker/blob/master/meeting-peopl...