Chris, You can add my doc to the link/wiki, has all the tech background on the first topic we discussed (function portability and common event/context model),

Argh please ignore me

Hi all, I'm away for next week's TOC and so would love Chris or Ken to chair

Hi Ken, I work closely with Pini at Container Solutions and I would like to be involved in the Working Group. -- Jason Smith Senior Developer http://jasonrichardsmith.org/

Thanks Ken for organizing, I haven't seen any serious concerns bubble up and will now officially form the CNCF Serverless WG, sponsored by Ken Owens from the TOC:

Please add me as well. Thanks Best regards 易立 Yi, Li (Mark) weiyuan.yl@...

Please add me as well: axbaretto@...

Can I get an invite too please. I opened a PR to get added but wasn't sure if that was an old way of signing up. thanks -Doug _______________________________________________________ STSM | IBM Open

+1! Iron.io (IronFunctions) would love to be involved: https://github.com/iron-io/functions

Please join me Monday afternoon! Open Source Software Fuels Explosive Growth and Startup Join ​Cloud ​Native ​Computing ​Foundation ​and ​Battery ​Ventures ​​for ​​an

+1 (non binding)

+1

+1 Mark From: <cncf-toc-bounces@...> on behalf of "Kenneth Owens (kenowens) via cncf-toc" <cncf-toc@...> Reply-To: "Kenneth Owens (kenowens)" <kenowens@...> Date: Tuesday, May 16, 2017 at 9:06

Ken, I would join for iguazio, we have high-perf “serverless” framework for internal use and will soon open-source it Seems like there is a consensus that serverless function portability

+1

thanks Sugu - that is helpful. If we are going to ask Kyle if he could 'do a jepsen', it would be very good to understand which consistency choices should be tested.

+1

I would like to participate. Thanks.

+1 This is great! Hyper.sh also built hyper func fully based on Kubernetes, and cooperating with IBM Whisk. Hope to be involved in the new WG! --- Harry

I will participate for Huawei and actively contribute to this effort. As I presented today, my key interest is consistent and portable user-facing configuration (event, function, event-function