Any and all constructive feedback on project proposals from the community is definitely encouraged.

Justin, may I suggest that you add your specific questions or concerns to the PR at https://github.com/cncf/toc/pull/163

That way the project team and other users of Harbor can respond to specifics.

Regards

Q

Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # C2-27

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

From: <cncf-toc@...> on behalf of "Chris Short via Lists.Cncf.Io" <chris=chrisshort.net@...>
Reply-To: "chris@..." <chris@...>
Date: Thursday, November 8, 2018 at 07:28
To: Justin Garrison <justinleegarrison@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] Harbor moving to incubation

I genuinely appreciate Justin's feedback on these votes. If I'm not intimately familiar with the project/product I often wait for Justin's input prior to voting. I wholeheartedly encourage Justin's input on these votes. They bring up bigger points and provide levity to the process. Any effort to not have this feedback on the record should be discouraged, in my opinion.

Chris Short

Web | Newsletter | Twitter

On Wed, Nov 7, 2018 at 11:37 AM Justin Garrison <justinleegarrison@...> wrote:

I'm well aware of the adoption and uses of Harbor. My company runs it and my criticisms come from first hand experience as a user and operator of the software.

I'm happy to move my feedback out of this thread so voting can continue without any extra noise.

--
Justin Garrison
justingarrison.com

On Tue, Nov 6, 2018 at 4:27 PM Haining Zhang <hi@...> wrote:

(in reponse to Justin's comment)

Though Harbor may not be the only solution to a private registry, thousands of users choose Harbor to manage container images in their production environments. The user base includes many large internet companies and enterprises in the world. In some environments, Harbor manages tens of thousands of images and supports thousands of container hosts. Typical use cases of Harbor include RBAC on images, image replication across geographically distributed locations, vulnerability scanning etc.

Haining

On 11/7/18 3:21 AM, Justin Garrison wrote:

-1 nb

I understand the need for container registries in a containerized environment, but I'm not sold Harbor being the solution for most people's needs when they need to run their own registry.

--
Justin Garrison
justingarrison.com

On Tue, Nov 6, 2018 at 8:56 AM Lee Calcote <leecalcote@...> wrote:

+1 non-binding

On Nov 6, 2018, at 8:27 AM, Chris Aniszczyk <caniszczyk@...> wrote:

The Harbor community has requested to move to the incubation maturity level and believes it has fulfilled the criteria: https://github.com/cncf/toc/pull/163

They have also created a presentation on top of the proposal for the community: https://docs.google.com/presentation/d/1aBQnE96kKatc1_t3E97lJBwiWvL-3GTitojuv-nWMuo/edit?usp=sharing

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/goharbor/harbor/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/goharbor/harbor/blob/master/OWNERS.md

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/goharbor/community/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: 7 major releases - https://github.com/goharbor/harbor/releases
Roadmap: https://github.com/goharbor/harbor/wiki/Harbor-Roadmap
Contributors: https://github.com/goharbor/harbor/graphs/contributors
Commit activity: https://github.com/goharbor/harbor/graphs/commit-activity
CNCF DevStats: https://harbor.devstats.cncf.io

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

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