On Tue, Mar 17, 2020 at 10:11 PM Mohan Boddu <mboddu(a)bhujji.com> wrote:
> Peter and I talked about it a while ago about merging IoT into regular
> Fedora composes. But we never got to that point. I am not sure whats
> their plan moving forward. My idea is to merge them together and keep
> their composes as it is for their testing.
If IoT folks don't reply to this particular issue in a few days, can we
simply assume merging the composes is the best way forward for everyone and
just do it? :) I see only benefits.
This all seems like a communication issue to me, nobody wants to kick the
ball and move things forward, and everyone else is stalled.
On Tue, Mar 17, 2020 at 2:01 PM Adam Williamson
> (many, many words. All of which are reasonable)
I, too, have been a little frustrated with the state of Silverblue and
CoreOS. It's not clear to me how much they're supposed to be a part of
the normal Fedora release process and how much they exist in their own
world because of the different nature of the distribution model. To be
clear, I don't blame those teams for this, I have been content the
last 21 months to make that Future Ben's problem. Oh look, Future Ben
has entered the chat. :-) For IoT, I can't make that claim because I
show up in their meetings most week to pester Peter about things. But
even then, I've generally been more reactive than proactive because
it's also a different beast (in some similar and also different ways).
I know Adam is not looking to single out anyone for blame, but I am
stepping forward to claim my share.
In my experience, things that happen rarely in Fedora can fall into
one of two buckets:
1. Subject to an over-engineered policy that will never be tested in
any great depth
2. Have a loose, hand-wavy policy that proves entirely insufficient
This is clearly an instance of the second bucket. Fedora.next was a
great model, but we didn't carry it forward. That may be in part
because we've had two (three?) changes of Program Manager since it
became a thing and knowledge was lost in the multiple transfers.
Independently of this issue, I've been slowly working to improve the
documentation so that my successor will not have to count on me to
remember to tell them things.
But to the matter at hand, as we discussed in the Release Readiness
meeting last week, I will review the historical documentation and see
what I can do to improve the bureaucracy. It may be too late to do
much about the existing emerging editions beyond reacting to the gaps
as we find them, but we can at least make it better for the next
I won't say any more now because I have nothing useful to contribute
yet. I would love to see the discussion continue on this over the next
He / Him / His
Senior Program Manager, Fedora & CentOS Stream