+1 binding Looks great. Thank you!

The CNCF Hub looks very Helm-specific and not obviously extensible, so it's not clear to me how it intends to accomplish

+1 non-binding

+1 (binding) Justin

+1 binding from me, thank you! -- Liz Rice @lizrice | lizrice.com | +44 (0) 780 126 1145

+1 (nb), thanks Paris and all.

Pitching in here, I think most would agree that ideally tools and projects need to be shared openly from their conception. However, I think from the usability point of view we also want to have a

+1 non-binding --Kiran Mova | Co-Founder, Chief Architect MayaData | kiran.mova@... https://github.com/openebs/openebs

+1 NB!! Looking forward to this!! :)

Hi TOC: We are ready for a vote. I know many of you gave +1s when we initially proposed this with the last iteration of TOC, but we are now ready for the final vote with the new crew.

All of these discussion got me thinking about a few things. I figured I'd share. First, I agree this should have been done in the open from the start. While I didn't run the show and I did ask for

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"