Thanks Dan All, please do take a last look over the g/doc comments. If you see discussion there that you feel is not in GH or still unresolved, please update the GH doc. Alexis

I took the TOC Principles document created by several TOC members and: 1. Converted it to markdown. 2. Left out the notes and comments on the budget. The notes and comments are important (and remain

Would it make sense to also highlight “CNCF Member” projects, distinct from “CNCF Project”s? The former much less prominently than the latter of course. For example: Oracle Database Amazon

https://en.wikipedia.org/wiki/Key_management https://square.github.io/keywhiz/ https://lyft.github.io/confidant/ https://medium.com/@Pinterest_Engineering/open-sourcing-knox-a-secret-key-management-se

In the next version, we'll rename Public cloud to cloud and put the bare metal category next to the public cloud one. That's done on 0.9.7, along with identifying Jaeger and Envoy as CNCF

Big +1 on this request from Brian, particularly from the perspective of MAAS (Metal as a Service), as well as OpenStack, VMware, et al. Those all definitely make more logical sense at the base level,

Coming back to this: Please move Openstack, VMWare, and the other private cloud platforms back to the bottom. Bare metal should be side by side with public clouds, not in the provisioning

If it would be useful I'd like to introduce the periodic table of cloud native elements I've been driving with several of our members. It's intend is to provide an elemental view of cloud outcomes,

Can we make the 2-D one more generic with drill downs for the online version that articulate all the products? I love that it highlights choices, but it should be able to provide an illustrative

Personally I think it highlights the freedom of choice. Yes it is complex and there are many decisions to make but don't we have to do that with any complex architecture we are trying to build? I

Thanks to everyone for their support, and especially to Chris and Alexis for helping out with the process, and to Bryan for being our sponsor. We're excited to join the community and work with all

Many thanks for everyone's efforts on bringing Jaeger into the CNCF fold! Congrats to the Jaeger team and to CNCF TOC for taking this step! Diane -- Kind Regards, Diane Mueller Director, Community

Welcome!

+1

And congrats Jaeger!

To some extent I agree with Brian, and it's not the message we want to send, but the reality is that this is the state of our industry. I can't tell you how many "ecosystem" slides I've seen over the

Thanks Chris, Alexis, and CNCF community! Looking forward to working with everyone. -- Matt Klein Software Engineer mklein@...

Hey everyone, I'm happy to announce that Jaeger has been accepted as a CNCF incubation level project (sponsored by Bryan): https://github.com/cncf/toc/pull/42 +1 TOC binding votes (6 / 9): Alexis:

Congratulations Envoy!

Hey everyone, I'm happy to announce that Envoy has been accepted as a CNCF incubation level project (sponsored by Alexis): https://github.com/cncf/toc/pull/43 +1 TOC binding votes (7 / 9): Alexis: