That's a symptom that this is becoming too much of an eye chart to be useful. I suggest having one diagram that shows the areas and current CNCF projects, and one diagram per area/layer/column with

No, service providers are documented elsewhere.

Good catch, Camille. Yeah, there are a bunch of changes in this version that don't make sense. For example, why is Openstack at a layer above public cloud?

Not every application in the universe should be in this map, whether they are cloud-native or not. The map is already too busy. I'd prefer to kick out a number of the projects that are currently in

AIs will create their own maps that humans cannot understand :-P

I'm sorry to hear that the changes are many and complex. Speaking for the TOC, the most important thing is to preserve the layering and buckets within each layer. Because we voted on that.

I also assume we will soon see a slew of “cloud-native” AI/ML start-ups, where would they sit? BTW interesting to learn DB2 & Oracle are “cloud-native” now, maybe we should add Lotus

Alexis, there are hundreds of positive changes in the latest version. We can do an 0.9.7 quickly, though. -- Dan Kohn <mailto:dan@...> Executive Director, Cloud Native Computing Foundation

maybe we should have a whole 'nother 'scape for data

Dan Please could you revert to the last known good version? Alexis

I made the change at the last minute to deal with a spacing issue. I will revert it in the next version and restore CI/CD to the top layer. Apologies. -- Dan Kohn <mailto:dan@...> Executive Director,

The TOC will have to fix this, by going back to the 0.92 structure, which was correct. And rebuilding from there.

That's very disappointing

It looks like it changed pretty significantly between 0.9.5 and 0.9.6.

Woah. How did CICD get moved? Wtf Landscape 0.92 is authoritative. I'm afraid this new thing is not. Dan, Chris, any ideas?

Would be good to add a section for service providers. Especially now, when we have the first batch of certified kubernetes service provides Pini -- Pini Reznik CTO T. +31 (0) 6 317 99 811 W.

Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it. Thanks, C

+1, non-binding. Dustin Kirkland VP of Product Canonical, Ltd. @dustinkirkland <cncf-toc@...> wrote:

+1 -- Benjamin Hindman Founder of Mesosphere and Co-Creator of Apache Mesos Mesosphere Inc. Follow us on Twitter: @mesosphere

+1