Fedora 22 is out, Fedora 23 is coming :)

Josh Boyer jwboyer at fedoraproject.org
Thu Jun 11 14:47:00 UTC 2015

On Thu, Jun 11, 2015 at 10:01 AM, Matthew Miller
<mattdm at fedoraproject.org> wrote:
> On Thu, Jun 04, 2015 at 02:10:05PM -0400, Josh Boyer wrote:
>> > But in order to be really useful unless they're all-in on Fedora, many
>> > people will want the python version for their
>> > infrastructure/environment, not whichever python we happen to ship in a
>> > given release.
>> "I will provide flexibility and utility by providing no flexibility
>> and utility" sounds like a crappy marketing point to me.
> For a practical example: Ansible doesn't currently support Python 3. If
> we change the cloud image to python3 — as is the expected plan, right?

Remains to be seen.  I'm skeptical the distro-wide default will switch tbh.

> — having that system python there doesn't provide any benefit. It's
> just extra weight.

Um, ok.  It's extra weight for people that don't use python.  In this
case, what would be the solution to getting python on your cloud
image?  Would you do it via SCL or via some kind of container overlay

> The early PRD called for a library of different images for different
> purposes, in addition to the base, and I think we're still interested
> in that — it's just not ready yet. That might include various
> ansible-ready or puppet-ready images, possibly with other tools
> installed as fits the use case.

That sounds like it will have all the problems we currently face with
Spins.  Too many choices, too much burden to produce, too little
overall benefit for deviation, too niche, too much churn from release
to release and new tech of the day.  Why would we choose to repeat
those same mistakes?

While I have no vested interest in Cloud, I'd rather see an image that
is flexible with utilities for people to customize and build on top of
even if that means it isn't the tiniest, thinnest image out there.


More information about the cloud mailing list