Fedora.NEXT Products and the fate of Spins

Bill Nottingham notting at redhat.com
Thu Jan 30 19:53:48 UTC 2014

Jiri Eischmann (eischmann at redhat.com) said: 
> >         That being said, as we go forward as Fedora.NEXT, we start to
> >         see more
> >         clearly defined divisions between Products, Spins and Remixes.
> >         Since
> >         these discussions needed to happen, we (FESCo) felt it was
> >         best to try
> >         to move the conversation public.
> > 
> > 
> > Part of the problem I have with this discussion other than the
> > alarmist subject is that we are discussing the "fate of spins" before
> > even coming out with concrete products out of the fedora.next
> > proposals.  That seems premature. 
> +1
> I cannot agree more. We still don't have (at least I don't) have a clear
> idea how basics of Fedora.NEXT will look. So this discussion is really
> kinda premature. We should clearly define the products first, then we
> can discuss spins and the border between them and remixes. From bottom
> up please :)

Blame me, I filed the original ticket. My concern was that we're (obviously)
doing work in the Fedora.next space around:

1) the three products (workstation, server, cloud)
2) the base, which lives under them in some manner
3) environments & stacks, which can live on top of them

First, I'm making the assumption that those three products are not the
end-all/be-all of what Fedora can ever be. So we should have a defined
process for how new products can be formed. And that can tie into some
things that are now spins, if they want to go that route.

Second, as we design how we build and ship all of those things above, it
stands to reason that implementation choices made there have the possibility
of breaking spins as they exist now.  That shouldn't happen in a complete
vacuum without warning, so it's worth discussing where things that are spins
now fit into that process.


More information about the devel mailing list