Thanks Dan & Matt for getting this public! 

We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community. 

--

Liz Rice

@lizrice | lizrice.com | +44 (0) 780 126 1145

On 11 Mar 2020, at 13:05, Gerred Dillon <hello@...> wrote:

Excited to see this. The sandbox criteria (https://www.cncf.io/sandbox-projects/) (point 3 specifically) states:

3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects

Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?

I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon!

On Tue, Mar 10, 2020 at 3:35 PM Matt Farina <matt@...> wrote:

Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub.  From the README:

Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.

Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.

The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.

I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?

For those interested in some more history and context...

At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.

After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.

For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.

I want to thank Dan for bringing people together around this topic and working to make the idea a reality.

I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.

Regards,

Matt Farina