Thanks! And those are just the public ones. :)

Re: code percentages. This is a side-effect of where the project started, but we definitely want to diversify and I expect that it will happen naturally over time. E.g. we've had a couple non-Buoyant folks who have done major bits of work over the past year (and we've been expanding the maintainers list to reflect that).

-William

On Thu, Mar 15, 2018 at 11:08 AM, Quinton Hoole <quinton.hoole@...> wrote:

+1 (non binding)

Impressive production adoption!

I notice that 95%+ of code is contributed by current Buoyant employees.  Any plans to diversify that in the future?  To be clear, this is not a pre-requisite for incubation.

Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # E2-9

Email: quinton.hoole@...   ID#Q00403160

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Thursday, March 15, 2018 at 10:28
To: "cncf-toc@..." <cncf-toc@...>
Subject: [cncf-toc] [VOTE] linkerd moving to incubation

The linkerd team has requested a move to the incubation level: https://github.com/cncf/toc/pull/86 

You can see the project statistics here: https://linkerd.devstats.cncf.io/ and the linkerd project believes they meet the incubation criteria requirements:

- Used successfully in production by at least three independent end users of sufficient scale and quality: https://github.com/linkerd/linkerd/blob/master/ADOPTERS.md

- Have a healthy number of committers: https://github.com/linkerd/linkerd/blob/master/MAINTAINERS.md
- Demonstrate a substantial ongoing flow of commits and merged contributions: https://github.com/linkerd/linkerd/releases and https://github.com/linkerd/linkerd/graphs/contributors

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

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