+1 non-binding

+1 binding

On Thu, May 31, 2018 at 8:05 AM, Brian Grant via Lists.Cncf.Io <briangrant=google.com@...> wrote:

On Thu, May 31, 2018 at 6:19 AM Barker, Daniel <drbarker@...> wrote:

Thank you. I’ll check it out.

Specifically, this:

https://github.com/cncf/toc/pull/114#issuecomment-393029368

 

 

Dan Barker

Chief Architect

National Association of Insurance Commissioners

1100 Walnut St. Suite 1500

Kansas City, MO 64106

816-783-8669

 

From: Alexis Richardson <alexis@...>
Sent: Thursday, May 31, 2018 8:17 AM
To: Barker, Daniel <drbarker@...>
Cc: CNCF TOC <cncf-toc@...>; Christian Jantz <chris@...>
Subject: Re: [cncf-toc] [VOTE] Helm project proposal (incubation)

 

Dan

 

These are great questions.  There is some additional discussion in the GitHub issue for Helm.

 

A

 

 

On Thu, 31 May 2018, 13:47 Barker, Daniel, <drbarker@...> wrote:

+1 non-binding, however I’m concerned about the precedent being set of including k8s-only tools. I think this precedent was already set with Telepresence or Rook. The TOC requires a specification to be broadly adopted, so why not other tools. Should there be a requirement that before moving into incubation a project has to be usable across multiple primary platforms. I don’t think the language on that is accurate, so I’ll expand. For example, rkt is not dependent on k8s. It can run on a primary platform of k8s or a bare OS. Linkerd and Envoy can run on Mesos and VMs. In effect, the TOC is acting as a Kingmaker for k8s if it chooses to include so many k8s-only tools. These all are currently just in Sandbox, but I see nothing preventing all of them from graduating. Also, this is nothing against the projects or k8s, it’s about surfacing the disparity between the actual appearance of the CNCF and the intended or stated appearance of the CNCF. Are we unintentionally excluding projects that won’t run on k8s?

 

Dan Barker

Chief Architect

National Association of Insurance Commissioners

1100 Walnut St. Suite 1500

Kansas City, MO 64106

816-783-8669

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Christian Jantz
Sent: Thursday, May 31, 2018 7:17 AM
To: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] Helm project proposal (incubation)

 

+1

On 31. May 2018, at 1:08 PM, Lee Calcote <leecalcote@...> wrote:

+1 non-binding

 

On May 30, 2018, at 10:52 AM, Ken Owens <kenchristineowens@...> wrote:

 

+1 Binding

 

On Tue, May 29, 2018 at 8:59 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:

The TOC has invited Helm (https://github.com/kubernetes-helm) as an
INCUBATION level CNCF project, sponsored by Brian Grant from the TOC:
https://www.helm.sh

Helm joined the CNCF at the same time Kubernetes did as it was a
sub-project of Kubernetes at that time. Helm is seeking to become a
top-level project within the CNCF because Helm has grown up and is
taking on a life of it's own. This can be seen in the over 300
contributors to Helm, over 800 contributors to the community charts,
running a successful conference based solely on Helm
(https://helmsummitpdx-feb2018.splashthat.com/), and the unique
culture forming around Helm compared to core Kubernetes.

Please vote (+1/0/-1) by replying to this thread; the full project
proposal located here: https://github.com/cncf/toc/pull/114

Remember that the TOC has binding votes only, but we do appreciate
non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719

 

 

----------------------------------------- CONFIDENTIALITY NOTICE

This message and any attachments are from the NAIC and are intended only for the addressee. Information contained herein is confidential, and may be privileged or exempt from disclosure pursuant to applicable federal or state law. This message is not intended as a waiver of the confidential, privileged or exempted status of the information transmitted. Unauthorized forwarding, printing, copying, distribution or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or by forwarding it to the NAIC Service Desk at help@....

----------------------------------------- CONFIDENTIALITY NOTICE

This message and any attachments are from the NAIC and are intended only for the addressee. Information contained herein is confidential, and may be privileged or exempt from disclosure pursuant to applicable federal or state law. This message is not intended as a waiver of the confidential, privileged or exempted status of the information transmitted. Unauthorized forwarding, printing, copying, distribution or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or by forwarding it to the NAIC Service Desk at help@....