Re: DRAFT slides for TOC meeting tomorrow
Doug Davis <dug@...>
hmm I guess it depends on the audience then. I might agree that from an app developer perspective the points of interop in the old pict might not be of great interest, but from a CNCF project perspective, and as someone working on the projects that make up the CNCF family of projects, I actually think that might be critical as that shows where in the overall picture we might be missing some community focus on projects in that space. Perhaps we need both?
On Wed, Jul 20, 2016 at 12:57 PM, Doug Davis <dug@...> wrote:
1 - what is driving the need for a new one rather than tweaking the existing one?
IMHO the old one is quite hard to understand, especially for developers who might use CNCF projects.
This is an attempt to simplify the picture somewhat. At the end of the day most developers care about CNCF's main concerns: containers, runtime platforms, core services and ancillary tooling, and how they relate to each other, and to apps in general.
I think the old one is really abstract -- much too abstract -- and contains extra info, eg about all the interop surfaces, which are unlikely to be seen or used by many developers.
Networking *is* in the stack -- it's part of the runtime layer. This is covered in the "detail" presentation of the stack that Ken showed two weeks ago.
Registries are part of app dev.
STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog
Alexis Richardson via cncf-toc ---07/19/2016 04:42:16 PM---all, https://docs.google.com/presentation/d/1h8HFOAVLrJTvjUPP6ZHG2SzVKsTaMLvbiqjzUj4vml8/edit?ts=578
From: Alexis Richardson via cncf-toc <cncf-toc@...>
Date: 07/19/2016 04:42 PM
Subject: [cncf-toc] DRAFT slides for TOC meeting tomorrow
Sent by: cncf-toc-bounces@...
comments actively sought
cncf-toc mailing list