There’s been a desire within the CNCF TOC and community to provide further clarity around project maturity levels in CNCF and this has resulted into the CNCF Sandbox proposal after a month of discussion: https://github.com/cncf/toc/pull/92

When we initially created the Inception project level, it was intended to provide an avenue for technically interesting early-stage projects that were beneficial to the cloud-native community. We are transitioning Inception projects to the Sandbox. When we say that Sandbox projects are "early stage" this covers the following examples:

- New projects that are designed to extend one or more CNCF projects with functionality or interoperability libraries. In the case of Kubernetes, the Sandbox is intended as a home for projects that would previously have started in the Kubernetes Incubator.

- Independent projects that fit the CNCF mission and provide potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need)

- Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and "experimental" projects

- Any project that realistically intends to join CNCF Incubation in future and wishes to lay the foundations for that

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

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Note, if the proposal passes, CNCF staff will make updates to website and all other marketing collateral regarding this change.

--

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

On Wed, Feb 28, 2018 at 7:46 PM, Ruben Orduz <ruben@...> wrote:
> +1 non-biding on the spirit, -1 non-binding on the naming.

Same.

+1 binding

On Wed, Feb 28, 2018 at 1:42 PM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:

There’s been a desire within the CNCF TOC and community to provide further clarity around project maturity levels in CNCF and this has resulted into the CNCF Sandbox proposal after a month of discussion: https://github.com/cncf/toc/pull/92

When we initially created the Inception project level, it was intended to provide an avenue for technically interesting early-stage projects that were beneficial to the cloud-native community. We are transitioning Inception projects to the Sandbox. When we say that Sandbox projects are "early stage" this covers the following examples:

- New projects that are designed to extend one or more CNCF projects with functionality or interoperability libraries. In the case of Kubernetes, the Sandbox is intended as a home for projects that would previously have started in the Kubernetes Incubator.

- Independent projects that fit the CNCF mission and provide potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need)

- Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and "experimental" projects

- Any project that realistically intends to join CNCF Incubation in future and wishes to lay the foundations for that

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

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Note, if the proposal passes, CNCF staff will make updates to website and all other marketing collateral regarding this change.

--

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

There’s been a desire within the CNCF TOC and community to provide further clarity around project maturity levels in CNCF and this has resulted into the CNCF Sandbox proposal after a month of discussion: https://github.com/cncf/toc/pull/92

When we initially created the Inception project level, it was intended to provide an avenue for technically interesting early-stage projects that were beneficial to the cloud-native community. We are transitioning Inception projects to the Sandbox. When we say that Sandbox projects are "early stage" this covers the following examples:

- New projects that are designed to extend one or more CNCF projects with functionality or interoperability libraries. In the case of Kubernetes, the Sandbox is intended as a home for projects that would previously have started in the Kubernetes Incubator.

- Independent projects that fit the CNCF mission and provide potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need)

- Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and "experimental" projects

- Any project that realistically intends to join CNCF Incubation in future and wishes to lay the foundations for that

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

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Note, if the proposal passes, CNCF staff will make updates to website and all other marketing collateral regarding this change.

--

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

+1 non-binding

On Wed, Feb 28, 2018 at 1:13 PM, Richard Hartmann <richih@...> wrote:

On Wed, Feb 28, 2018 at 7:46 PM, Ruben Orduz <ruben@...> wrote:
> +1 non-biding on the spirit, -1 non-binding on the naming.

Same.

On Wed, Feb 28, 2018 at 7:46 PM, Ruben Orduz <ruben@...> wrote:
> +1 non-biding on the spirit, -1 non-binding on the naming.

Same.

There’s been a desire within the CNCF TOC and community to provide further clarity around project maturity levels in CNCF and this has resulted into the CNCF Sandbox proposal after a month of discussion: https://github.com/cncf/toc/pull/92

When we initially created the Inception project level, it was intended to provide an avenue for technically interesting early-stage projects that were beneficial to the cloud-native community. We are transitioning Inception projects to the Sandbox. When we say that Sandbox projects are "early stage" this covers the following examples:

- New projects that are designed to extend one or more CNCF projects with functionality or interoperability libraries. In the case of Kubernetes, the Sandbox is intended as a home for projects that would previously have started in the Kubernetes Incubator.

- Independent projects that fit the CNCF mission and provide potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need)

- Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and "experimental" projects

- Any project that realistically intends to join CNCF Incubation in future and wishes to lay the foundations for that

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

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Note, if the proposal passes, CNCF staff will make updates to website and all other marketing collateral regarding this change.

--

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

Chris

I think the right way to reflect our governance values is in the
Graduation criteria and Incubation criteria.  Therefore the Sandbox
doc could add a statement of the form "The CNCF will help projects
adopt good principles of governance in preparation for future
Incubation, if the project leads so desire".

alexis


On Mon, Feb 26, 2018 at 5:00 PM, Chris Aniszczyk
<caniszczyk@linuxfoundation.org> wrote:
> Thanks for your feedback here Stephen, a big tenant of CNCF has always been
> that projects are self governing and can bring their own governance as long
> as it's transparent + fair (we call this minimum viable governance):
> https://github.com/cncf/toc/blob/master/PRINCIPLES.md#projects-are-self-governing
>
> Over time (especially these days), I find that successful projects evolve
> towards more open governance (we've even had this happen in CNCF with
> containerd moving from bdfl to committee model) due to community/adopter
> pressure.
>
> I'll look at seeing how I can codify your point in the sandbox proposal that
> open governance is important and the earlier the better. I'm looking to
> finalize the proposal the next day or so before calling for a vote.
>
> Thanks!
>
> On Wed, Feb 21, 2018 at 5:48 AM, Stephen Watt <swatt@...> wrote:
>>
>> Thanks Chris. Firstly, I think the way the sandbox doc is articulated in
>> the doc is great. However, I imagine sandbox projects should be aware of the
>> TLP graduation criteria and trying to steer their ship towards those goals,
>> and as such, it prompted a broader meta question that I thought might be
>> better suited to the TOC list, rather than a comment on the doc.
>>
>> When I look at the graduation criteria from Sandbox -> Incubation ->
>> Graduated, I see in the criteria for "graduated" that one needs to have
>> committers from at least 2 organizations. This hints at a desire for CNCF
>> projects to have some measure of open governance but stops short of calling
>> it out directly. Why not do so?
>>
>> I believe I've heard it stated by the TOC before that you don't want to
>> preclude healthy important projects where the vast majority of committers
>> happen to be from one organization. I agree. However, I don't think that is
>> at odds with an open governance model. For example, you could have an open
>> governance model where it just so happened to be, that the participation in
>> the project is all from a single company, however, because of the governance
>> model, should contributors join later from other companies, they would have
>> a path to equal influence in the project decision making and contributions
>> being committed.
>>
>> Why am I bringing this up? An ounce of prevention is worth a pound of
>> cure. I believe the advantage of calling open gov out explicitly in the
>> graduation criteria helps avoid a future scenario where a CNCF project is
>> governed by a cabal largely dominated by one company, that has a token
>> committer from outside, that actively or passively ignores contributions
>> from the community (the incentives can differ from project to project). I
>> suspect you have come across github projects with open source licenses that
>> behave this way. Projects like this are bad for the project's and
>> foundation's brand.  The ASF had to deal with this issue a number of times
>> with popular projects in their Big Data stack. It was painful, but they were
>> able to deal with it because they are prescriptive about how ASF projects
>> are to be governed. I realize this can be a slippery slope because the next
>> step would be to become prescriptive about what type(s) of open governance
>> model CNCF projects would deem acceptable. However, perhaps something worth
>> anticipating and discussing.
>>
>> Regards
>> Steve Watt
>>
>> On Tue, Feb 20, 2018 at 12:06 PM, Chris Aniszczyk
>> <caniszczyk@linuxfoundation.org> wrote:
>>>
>>> At today's TOC call there was consensus on the CNCF Sandbox proposal is
>>> close to being ready for a formal vote. We will leave the document open for
>>> any community comments for a week and do a formal vote next week:
>>> https://goo.gl/gZhBjY
>>>
>>> After the vote and assuming the sandbox is approved, we will resume
>>> voting on new project proposals (existing inception proposals will be
>>> slotted for the sandbox).
>>>
>>> Thanks.
>>>
>>> --
>>> Chris Aniszczyk (@cra) | +1-512-961-6719
>>
>>
>
>
>
> --
> Chris Aniszczyk (@cra) | +1-512-961-6719
>

+1 (non-binding)

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Date: Monday, February 26, 2018 at 08:52
To: "cncf-toc@..." <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Kubernetes moving to graduation

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

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

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

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

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

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

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

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

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

+1 non-binding

thanks,
-chris

On Feb 26, 2018 5:52 PM, "Chris Aniszczyk" <caniszczyk@linuxfoundation.org> wrote:

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

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

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

After last week's TOC call, we decided to start moving forward with graduation reviews. Kubernetes was the project that motivated the creation of the CNCF, and was its first (seed) project. It has sustained a fast pace of growth of contributors, contributing organizations, and users, and now operates at massive scale. The project's governance and community-management practices continue to evolve and mature as the project grows, but the Kubernetes Steering Committee (https://github.com/kubernetes/steering) unanimously believes that Kubernetes fulfills all the CNCF incubating and graduation criteria:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://kubernetes.io/case-studies
- Have a healthy number of committers: Kubernetes is so large, with thousands of contributors and nearly 100 repositories, that we had to develop our own mechanism to manage approval permissions. We have hundreds of approvers, listed in more than 4000 OWNERS files across the project (https://github.com/search?utf8=%E2%9C%93&q=org%3Akubernetes+filename%3AOWNERS&type=Code)

- Demonstrate a substantial ongoing flow of commits and merged contributions: Devstats shows that we have thousands of PRs merged per month (https://k8s.devstats.cncf.io/)

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

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