Quinton has done all the "final" edits, and the team of volunteers (Erin, Matt, Alex & some others) got the doc into an editable state. THANK-YOU! a

Stephen This came up indirectly at the Kubecon 'meet the TOC' session, when Jaice asked what we are doing to make the TOC more diverse. Several people responded. One idea, that I have high hopes for,

Hi all Please DO speak up on the topic of "what can CNCF do and where can it spend money to track and improve project health, as transparently as possible". a <caniszczyk@...> wrote:

+1 binding

thank you! @all -- please shout if you have urgent topics for next week's call. I'd like to press on with the SIGs/Categories effort. a

Chris Do we have a TOC call tomorrow, or is it in eight days time? a

Excellent Chris, thanks so much re bounties! Happy 2019 all

https://m.hexus.net/tech/news/software/125747-14-open-source-projects-get-eu-funding-bug-bounty-payments/

As the chairs are volunteering in spare time, I suggest that more support is necessary.

+1 for track chairs! I'd like to see CNCF appoint a permanent Kubecon liaison who can help the conference chairs achieve continuity. WDY(A)T?

Addendum: Thanks to Justin Cormack for adding some narrative around an example SIG for Security. Please see the doc & comment!

Hi all REMINDER to please look at and comment on this doc on SIGs https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit# I know we are all ridic busy with Kubecon loomin

congratulations! <caniszczyk@...> wrote:

Brian The containerd folks made a good presentation last week. In the Q&A afterwards both Quinton and I were asking if you could provide more colour on why you think they are ready to graduate, possib

thank-you Chris

+1 binding

+1 binding

It may be better to serve the community needs through smaller events.

I'm in favour of the TOC being a focal point for a community discussion on how that community meets. At the same time we should be conscious that cncf events have many stakeholders ie. The foundation,

I may be mistaken, but iiuc the Knative team spent time in q2 working with many of the serverless oss projects, so that they used Knative CRDs. That could explain the appearance of proliferation in th