OK – continuing discussions in the issue.

 

From: Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, February 19, 2019 at 11:08 AM
To: Joe Beda <jbeda@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] containerd moving to graduation

 

I can't think of an example but we have nothing in the rules to prevent it.

 

I think it's fair game to ask the containerd community about it and what their long term plans are: https://github.com/cncf/toc/pull/165#issuecomment-465222545

 

On Tue, Feb 19, 2019 at 11:05 AM Joe Beda <jbeda@...> wrote:

Hi all,

 

Double checking things before I vote but I notice that the governance ultimate rolls up to the Moby TSC for ultimate arbitration of technical disputes: https://github.com/containerd/project/blob/master/GOVERNANCE.md. I'd love to see the project stand on its own vs. deferring to an outside community.

 

Do we have any other examples where CNCF projects are ultimately governed by an outside body like this?

 

Hate to bring this up at the 11^th hour but I'm still catching up on stuff after joining the TOC.

 

Joe

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, February 18, 2019 at 10:59 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] containerd moving to graduation

 

containerd has requested to move to the graduation maturity level:
https://github.com/cncf/toc/pull/165

The containerd community believes it has fulfilled all the graduation criteria:

- Have a healthy number of committers and at least two from different organizations: Containerd has had a variety of maintainers and reviewers since its inception, and currently have 12 committers representing Docker, NTT, Google, IBM, Microsoft, Facebook, Tesla, and Cruise Automation. They also have reviewers representing Alibaba, ZTE, Huawei, Docker, Microsoft and an independent developer.

- Document that it is being used successfully in production by at least three independent end users:

Containerd began life prior to its CNCF as a lower-layer runtime manager for the Docker engine. Continuing today, containerd has widest usage and adoption as the layer between the Docker engine and the OCI runc executor. However, as containerd and its CRI plugin project have merged in January 2018, the combined use of containerd and the CRI plugin has grown to include several public cloud providers, as well as several projects who are attracted to the simplicity of the Go client API library for embedding container runtime capabilities.

IBM Cloud Kubernetes Service (IKS)
IBM Cloud Private (ICP)
Google Cloud Kubernetes Engine (GKE) [offers containerd in "alpha clusters"]
Cloud Foundry
Alibaba's PouchContainer
Rancher's Rio project
Eliot
Balena
LinuxKit
BuildKit
AWS Firecracker
Kata containers
Docker engine

- Demonstrate a substantial ongoing flow of commits and merged contributions: https://github.com/containerd/containerd/graphs/contributors + https://containerd.devstats.cncf.io + https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=containerd

- Have achieved a CII badge: https://bestpractices.coreinfrastructure.org/en/projects/1271

- Define a governance model: https://github.com/containerd/project/blob/master/GOVERNANCE.md

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

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

 

--

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