On Mon, Sep 30, 2013 at 10:48:57AM -0400, Robyn Bergeron wrote:
> For F21, we are just talking about it but still it would make
sense to
> have it earlier than later to get reasonable output for F21 (or any .next
> releases).
Yeah, the thing is that the budget will still be in the next fiscal year
(March 2014-Feb 2015), and plane tickets need to be bought ahead of time,
etc.
It would be very helpful to have Flock right before we start the actual
three-project branches. Since we can't, sadly, have as many Flocks as
releases, that suggests that maybe we should have F21 as a normal or even
short cycle release, followed by Flock in June. (Which should be okay for
finding space at universities.)
I don't know if Fedora Activity Days for the product working groups would be
useful or not; they'll also need to be good at remote collaboration for the
bulk of the work anyway, but a FAD might help to kick things off. What I
*would* like to see is a FAD for QA and rel-eng automation, because we'll
need that in order to actually pull off having three separate products. (We
need it now anyway, in fact, but, then, that times three.)
That way, we're laying the groundwork for the next phase even if we're not
immediately launching it. I'm kind of excited about launching *something*,
but having it actually get to orbit or escape velocity (pick your
metaphorical destination) is... the actual point, so if it takes a little
longer to get launched and that gives us better success, that's not bad.
And, we're not sitting completely still; promoting the cloud image as
first-class is a big change even if the product isn't more differentiated.
We also can work on Fedora EPIC and other "Ring 2" ideas in parallel.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>