FYI: Treasure Data (Fluentd) will be at re:Invent and will host an after-party at Tao Night Club (best club in Last Vegas). TD is extending the invitation to CNCF members, if you are interested into

Sorry for the mass mailing, but we are looking for a few more Re/Invent tickets if anyone has any to spare. Thanks! -- Chenxi Wang, Ph.D. Chief Strategy Officer, Twistlock @chenxiwang +1.650.224.7197

The Supergiant/Qbox team will be at re:invent in force. Mark Brandon CEO and Co-Founder, Qbox, Inc.Email:mailto:mark@... Website:http://qbox.io/

You may have heard that CNCF is launching a curriculum development, training and certification initiative for Kubernetes that was announced at CloudNativeCon last week. If you are interested in

I do not plan to be there but can adjust if required.   Kenneth Owens CTO kenowens@... Tel: +1 408 424 0872 Cisco Systems, Inc. 16401 Swingley Ridge Road Suite 400 CHESTERFIELD 63017 United

Slides https://docs.google.com/presentation/d/124ouW9yzJHukNbYa1-orQP2O0EjQHQmiU7yGHw0FkRY/edit?ts=582c51e4#slide=id.gd5ae4e962_2_136

Will there be enough of us at Re:invent to justify a f2f attempt?

Hi all, We can talk about this on the call, but the main point is "it feels like we are close". I propose to keep the doc open for comment for another 10-11 days and kick off a vote, if possible,

Hi all, Some logistical issues with google docs mean that I'm posting the draft agenda as below. Slides will land just before the meeting. a Projects: - Welcome Fluentd + link to Blog

+mohr If you have feedback on the kubernetes proposal, please do provide that feedback on the doc or on the issue.

Thanks Dan. I plan on pushing more on this post-KubeCon. Hopefully get PRs up against the documentation in the coming days. I will take this discussion under advisement but I think there are some

We believe we're Ready to call for a vote on the project graduation criteria. Could TOC members and others please add comments to the doc if they have additional concerns.

I mailed a few of the OpenSSL team to ask them about this. Here's the reply from Rich Salz: I hope that clarifies things. Cheers, Nicko -- Nicko van Someren CTO, Linux Foundation +1 (978) 821-0391

Ah, but I don't, I'm a horrible release maker. I did 3 releases 2 weeks ago, none last week, and then one this week. Or was it one last week, I can't remember... And all were on different days of

​I don't disagree but in the absence of a highly regular release cadence, or in the case of an out-of-cycle release, it is still valuable to know when a new​ release is coming. ​I will do.

Users might get warm and fuzzies thinking that this is the only time they need to update, but really, they should be updating all the time. Announcing it ahead of time really doesn't help companies

It's also worth noting that precisely because the Linux kernel team put out a release every single week the scheduling of IT resources for deployment is not a problem. People know in advance when your

That's interesting feedback. I was speaking to the VP of infrastructure at a major bank last week and he said that having a heads up from OpenSSL helps him hugely and he wished that more projects did

I think you might want to reconsider that, as over beers, the OpenSSL team says that this type of thing really doesn't work and just causes more problems... But hey, remember that I'm on a project

Hi Alexis, Thanks for that. I read through the Google Doc and added some comments. One thing I think would be valuable to include in the security process is for there to be a broadcast mail to some