On May 15, 2017, at 9:43 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:

The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36

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

Thanks!

--

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

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

+1 non-binding


thanks
-Doug
_______________________________________________________
STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog

<graycol.gif>Chris Aniszczyk via cncf-toc ---05/15/2017 12:44:09 PM---The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level C

From: Chris Aniszczyk via cncf-toc <cncf-toc@...>
To: CNCF TOC <cncf-toc@...>
Date: 05/15/2017 12:44 PM
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)
Sent by: cncf-toc-bounces@...

---

The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:

The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36

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

Thanks!

--
Chris Aniszczyk (@cra) | +1-512-961-6719_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

On May 15, 2017, at 11:43 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:

The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36

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

Thanks!

--

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

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

On May 15, 2017, at 2:51 PM, Kenneth Owens (kenowens) via cncf-toc <cncf-toc@...> wrote:

 

+1

 

<image001.png>
Kenneth Owens CTO kenowens@... Tel: +1 408 424 0872	Cisco Systems, Inc. 16401 Swingley Ridge Road Suite 400 CHESTERFIELD 63017 United States cisco.com

 

<image002.gif>Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here for Company Registration Information.

 

From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...] On Behalf Of Chris Aniszczyk via cncf-toc
Sent: Monday, May 15, 2017 11:44 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)

 

The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:

The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36

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

Thanks!

 

-- 

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

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

On May 15, 2017, at 2:51 PM, Kenneth Owens (kenowens) via cncf-toc <cncf-toc@...> wrote:

+1

 

<image001.png>
Kenneth Owens CTO kenowens@... Tel: +1 408 424 0872	Cisco Systems, Inc. 16401 Swingley Ridge Road Suite 400 CHESTERFIELD 63017 United States cisco.com

<image002.gif>Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here for Company Registration Information.

 

From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...] On Behalf Of Chris Aniszczyk via cncf-toc
Sent: Monday, May 15, 2017 11:44 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)

 

The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:

The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36

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

Thanks!

 

-- 

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

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

Chris, can we align the CNCF Marketing meeting time as well? It is unlikely to have TOC and Marketing meetings happening​ at the same time.

On May 4, 2017 8:34 PM, "Chris Aniszczyk via cncf-toc" <cncf-toc@...> wrote:

At the last CNCF TOC meeting, the TOC decided to update meeting times to the first and third Tuesday of the month. I've updated the TOC README with the new info:

https://github.com/cncf/toc/blob/master/README.md#meeting-time

There's also a public gcal now you can add now: https://goo.gl/eyutah

The next meeting will now be 5/16/17 @ 8am PT, see everyone then!

In June it will now be 6th and the 20th.

Thanks.

--

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

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc