Jess That's really one for Dan but AIUI the whole website is in the process of being nurtured into an optimal state for 2018 .... So all comments good & timely, anywhere. a

Quick question: what are the platinum members, the ones who paid the 300k? Do they need to be on the same slide / materials as the projects? Is that written into a contract or something? Also I'm

thanks Dan & team @all TOC community, please do comment to Dan directly or on tomorrow's TOC call

We'll be discussing maturity levels on the TOC call. This is just a quick note that at the TOC's request, we revised CNCF marketing materials to clearly separate Incubating and Inception

Draft slides https://docs.google.com/presentation/d/1jRS8QTalE6ct-yShLS9h3d6qDRQj16YjS04No9b3-XE/edit?ts=5a783a4d#slide=id.g25ca91f87f_0_0

I agree that it's an end goal. I also agree that it's vague and not specific to cloud-native approaches. Even the principle of least privilege dates back to at least the 70s, so I don't think it's

I feel like "secure" is more along the lines of the end goals, not engineered attributes. I agree it's very important (see chapter 8 of Cloud Native Infrastructure) but many of the ways to make

Wonderful collaboration! I think this is a very strong definition of the essence of CNCF! Great job all!

Great thread and I totally agree what's been discussed and summarized so far here. Do you mind incorporating a notion on security in the definitions? Something like: Secure by design Zero-trust (vs.

+1 (non-binding)

Another go: The mission of the Cloud Native Computing Foundation is to drive the adoption of technologies designed for modern dynamic, distributed environments, such as public clouds and private

Deliberately vague. Yes, it could include the platform, such as Kubernetes. I don't know that we're ready to draw a firm boundary yet. Cloud Native is still somewhat aspirational.

This is much, much better!

+1 (non-binding)

​Not at all. Please do! I shared them​ ​so they could be incorporated​​ I agree. Many things can claim to be "scalable" but every design decision has trade-offs. How you get to scalability

+1 (non-binding)

+1

As much as I'm a strong proponent of declarative configuration and APIs (and declarative APIs :-)), I agree that they are implementation techniques. I think we should provides examples of such

I prefer the engineered attributes: Operable Observable Elastic Resilient AgileOver the end goals: Scalable Durable Continuous Since I think some indication of strategy/technique is needed in order

Great discussion. Thanks! Do you mind if we incorporate some/all of them? ChrisA also pointed out that Schedule A at the bottom of the charter also needs to be similarly updated. My current thinking