Hi, William. Are there any specific large areas of upcoming development in linkerd, which would provide an opportunity for onboarding new contributors? Most post-1.3.0 (reasonably) looks like fixes

I am on vacation this week and will not be dailing in 😀

+1 (non-binding)

+1 (non-binding)

and some folks have said the google short link isn't working, here's the full link: https://docs.google.com/presentation/d/1IwxTIXta88Mb2UIj3TFiKKC7Vl2_BC1GfsBTdgwXqOk/edit?usp=sharing -- Chris

oh... and by 3/19/2018 I meant 3/20/2018, the CNCF TOC meeting is tomorrow :) -- Chris Aniszczyk (@cra) | +1-512-961-6719

Here's the draft agenda deck for tomorrow: https://goo.gl/PpznT7 We'll be welcoming NATS (incubation) to CNCF, along with OPA/SPIFEE and sandbox projects, discussing sandbox guidelines v1.0, working

+1 non-binding

+1 (non-binding) Linkerd is an excellent service mesh proxy!

+1 (non-binding)

thank-you for the detailed summary, George!

+1 (non binding) Linkerd provides a mature and production-ready implementation of a service mesh. There are several areas where its architecture has considerable benefits over currently available

+1 (non-binding)

+1 (non-binding) Linkerd is legit with a great core team and supporting community!

+1 (non-binding)

0 non-binding-- Chris Short https://chrisshort.net https://devopsish.com

​-1 non-binding I think linkerd does a great job helping applications gain resilience from the network proxy and it has done an amazing 🙌 job and educating users and gaining production usage. I

+1 non-binding

+1 (non binding) Also have a the same question, any plans to diversify that in the future ? I am glad to integrate linkerd with Apache RocketMQ 5.0 deeply :-) Best Regards, Von Gosling, Apache

+1 (non-binding)