100% agree with encouraging diversity and not being king makers. However, I also think that applies within projects, not just between projects. I want to make sure that we adopt tools that encourage

To add to your thought, Brendan...I believe we should be thorough with our technical due diligence and understand what differentiates one project from another in the same space. And the CNCF, like any

I'm in full agreement regarding transparency in the CNCF. However, I think the discussion about OperatorHub has more to do with it's intersection with Helm and the Helm Hub as well as whether Operator

While I recognize the importance and the impact of an initiative like hub.cncf.io to the cloud native mission, I also agree that this should be discussed and introduced in a more open manner. The

Amen!

Yes, I completely agree

"kick" --> "kick off", obv ;-) <alexis=weave.works@...> wrote:

Heartily seconded! -- Dims-- Davanum Srinivas :: https://twitter.com/dims

I believe the issue here is simple. The CNCF is an open organisation and should not develop its own projects in secret. End of story. We saw this happen before eg "cloud native network functions"

Agree with the sentiment here. I'd put it as domain squatting or cookie licking is not healthy for the broader industry. What I find uncomfortable here is the potential added component of lack of

Thumbs up on the Conf Hub from the Litmus community. The community has a hub (https://hub.litmuschaos.io) for chaos experiments of Kubernetes applications. It will be nice to see the community coming

Thank you for raising this Chris. I have contacted the TOC multiple times on unfair treatment and inequality, especially when it comes to TOC sponsorship and prioritisation even for sandbox

Lots to unpack here, Chris, and as it’s 11pm I may not do it full justice in this response but I did want to make a couple of quick points: First come, first served project assessment has been a

During the evaluation of the Operator Framework for acceptance into the CNCF as an incubation project, I was surprised to learn that the vote was being held up by a request on behalf of a project yet

Erin, I was hoping to have a conversation with the TOC, CNCF staff, and other projects needing/having a hub (e.g., Falco and OPA) first for two reasons: The CNCF provides services for projects.

This is an exciting development. Having a central repository/hub for all the cloud-native artifacts makes sense. -Devdatta

Well it appears I have stuck my foot in my mouth...so apologies. It looks like this is the most broad list we have for the CNCF community. Can we safely assume that all the SIGs are also subscribed

Happy to move this anywhere - can you suggest a place that would be more appropriate? -- Kris Nova Chief Open Source Advocate 85 2nd Street San Francisco, CA 94105 nova@...

Erin, Which public mailing list are you referring to? Thanks, Matt -- Erin A. Boyd Senior Principal Software Engineer, OCTO Red Hat eboyd@...

Kris/Matt, Can we please move all these discussions to the public mailing list and/or a PR for sandbox? Now that the repo has been made public, let's invite the other interested parties that aren't