Re: updating what it means to be "Cloud Native"
Brian Grant
I prefer the engineered attributes:
Since I think some indication of strategy/technique is needed in order to distinguish CN from other/prior approaches.
On Fri, Feb 2, 2018 at 7:09 AM, Brian Grant <briangrant@...> wrote:
|
|
Re: updating what it means to be "Cloud Native"
Brian Grant
Great discussion. Thanks! On Wed, Jan 31, 2018 at 10:12 PM, Justin Garrison <justinleegarrison@...> wrote:
Do you mind if we incorporate some/all of them? ChrisA also pointed out that Schedule A at the bottom of the charter also needs to be similarly updated. My current thinking is that we aim for a concise definition of the What in the mission statement and defer the How examples (declarative, APIs, microservices, etc.) to Schedule A.
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Justin Cormack
+1 non binding
On Thu, Feb 1, 2018 at 4:44 PM, Chris Aniszczyk <caniszczyk@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Michael Fertik
+1 (non-binding)
-- Michael Fertik michael@... DISCLAIMER Any private opportunity discussed in this email or its attachments is being presented to you because you have expressed an interest in such opportunities, and any decision to invest in a venture fund or special purpose vehicle ("SPV") or any similar investment vehicle should be based on your own diligence and analysis. Please consult with your own tax, legal and financial advisors. An investment in the fund or SPV should only be considered by investors who can reasonably afford a loss on their investment. The investment presented in this email may be in a company or companies in which the sender, the sender's affiliates, and/or the GP in the investment vehicle has a related party interest, which may exist in the form of separately owned or earned shares or options, consulting compensation, executive compensation, and/or other forms of economic interest that are distinct and separate from those which may be of beneficial interest to the investor.
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Kevin Lynch
+1 non-binding
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Andrew Randall
+1 non-binding
toggle quoted messageShow quoted text
Andrew Randall Tigera
On Feb 1, 2018, at 7:44 AM, Chris Aniszczyk <caniszczyk@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Justin Garrison <justinleegarrison@...>
0 non-binding I think the spec is very interesting and necessary but I feel like it, and associated example tooling (SPIRE), may be too early for even inception level
On Thu, Feb 1, 2018 at 7:14 PM, Brian Grant via Lists.Cncf.Io <briangrant=google.com@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Brian Grant
+1 binding
On Thu, Feb 1, 2018 at 8:04 AM, alexis richardson <alexis@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Alan <alan.fraser@...>
+1 (non-binding)
Alan Fraser ==============================================================================
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Camille Fournier
-1 binding. I would rather see this mature for a while.
On Thu, Feb 1, 2018 at 8:44 PM, Jessica Frazelle <me@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Kb, Ramkumar <ramkumar.kalpathy@...>
+1 (non-binding)
Ramkumar Kb Lead Engineer, APAC-PB-IT Channels
==============================================================================
|
|
Re: [VOTE] SPIFFE project proposal (inception)
me@...
I’m +1 only the spec. -1 anything else. On Thu, Feb 1, 2018 at 17:34 Thangavelu, Kapil via Lists.Cncf.Io <kapil.thangavelu=capitalone.com@...> wrote:
--
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Thangavelu, Kapil
+1 (non-binding) From: cncf-toc@... <cncf-toc@...> on behalf of Micheal Benedict <micheal@...>
Sent: Thursday, February 1, 2018 7:02:58 PM To: cncf-toc@... Subject: Re: [cncf-toc] [VOTE] SPIFFE project proposal (inception) +1 (non binding)
On Thu, Feb 1, 2018 at 7:44 AM Chris Aniszczyk <caniszczyk@...> wrote:
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Micheal Benedict
+1 (non binding)
On Thu, Feb 1, 2018 at 7:44 AM Chris Aniszczyk <caniszczyk@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Sam Lambert <samlambert@...>
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Jon Debonis <Jondebonis@...>
+1 non-binding
|
|
Re: [VOTE] SPIFFE project proposal (inception)
dino@...
+1 non-binding
On Thu, Feb 1, 2018 at 5:04 PM, Tim Hinrichs <tim@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Tim Hinrichs
+1 (non-binding)
On Thu, Feb 1, 2018 at 1:11 PM John Fan <johnshunfan@...> wrote:
|
|
Re: [VOTE] SPIFFE project proposal (inception)
John Fan
+1 (non-binding)
|
|
Re: [VOTE] SPIFFE project proposal (inception)
Mark Lakewood <mlakewood@...>
+1 non-binding
|
|