consider renaming project due to confusion + trademark guidelines

[caniszczyk]

Hey all, love the project!

A quick reminder, CNCF has trademark usage rules for its project names: https://www.linuxfoundation.org/legal/trademark-usage

Given that the project isn't part of the CNCF Helm project, can you consider renaming the project to adhere to our guidelines? Some unique name like "hdashboard" or "komodor dashboard for Helm" would work as to not violate our trademark guidelines.

Thanks!

[itielshwartz]

Hi @caniszczyk , happy you love the project!

Thanks for sharing the CNCF trademark usage; TBH, we love the CNCF (and also members ourself), and ecosystem and genuinely trying to give back :)

Looking at the kubernetes and CNCF ecosystem, using the project name seems like the industry standard, especially for plugins.

Here are a few examples from the official helm site https://helm.sh/docs/community/related/#helm-plugins: helm-adopt - A helm v3 plugin to adopt existing k8s resources into a new generated helm chart. Helm Diff - Preview helm upgrade as a coloured diff helm-gcs - Plugin to manage repositories on Google Cloud Storage helm-git - Install charts and retrieve values files from your Git repositories helm-k8comp - Plugin to create Helm Charts from hiera using k8comp helm-mapkubeapis - Update helm release metadata to replace deprecated or removed Kubernetes APIs helm-monitor - Plugin to monitor a release and rollback based on Prometheus/ElasticSearch query helm-s3 - Helm plugin that allows to use AWS S3 as a [private] chart repository helm-schema-gen - Helm Plugin that generates values yaml schema for your Helm 3 charts helm-secrets - Plugin to manage and store secrets safely (based on sops) helm-tanka - A Helm plugin for rendering Tanka/Jsonnet inside Helm charts. helm-unittest - Plugin for unit testing chart locally with YAML helm-val - A plugin to get values from a previous release.

Also, looking at the border CNCF eco-system, it also likes that's the case:

Kubernetes External Secrets :fire::fire::fire::fire::fire: - Kubernetes External Secrets allows you to use external secret management systems, like AWS Secrets Manager or HashiCorp Vault, to securely add secrets in Kubernetes. kubernetes-ingress :fire::fire::fire::fire::fire: - An implementation of an Ingress controller for NGINX and NGINX Plus (commercial). k8s-image-availability-exporter :fire: - Prometheus exporter that warns you proactively about images that are defined in Kubernetes objects but are not available in the container registry. k8s-image-swapper :fire::fire: - k8s-image-swapper is a mutating webhook for Kubernetes, downloading images into your own registry and pointing the images to that new location.

Obviously, there are many more of those across the eco-system :)

Do you think this project, in particular, differs from all those projects?

Looking forward to your response, Thanks!

[caniszczyk]

Sorry for the slow response, we had the US Thanksgiving holiday!

I think the line for us is as long as it isn't publicly referred to in product form (e.g., on a komodor or project website) or the logo modified in anyway... and reference it self as an unofficial Helm dashboard. We do our best documenting the usage guidelines here: https://www.linuxfoundation.org/legal/trademark-usage - if it's just a repository name that's generally OK

Any page that references the trademark Helm should have a disclaimer like "The Helm name and logo are registered trademarks of the Linux Foundation. For a list of trademarks of The Linux Foundation, please see the Trademark Usage page."

I do think one cool idea could be a discussion with the helm project if they ever wanted such a dashboard contribution upstream but that's up to all y'all to discuss, I just want to ensure that the trademark rules are followed.

[itielshwartz]

Again thanks for the detailed response!

Given everything you said, we are going to do the following:

1. Add the relvent disclaimer across the project pages
2. Make a change in the project main screen to make it clear the project was done by Komodor
3. We will update the main readme making clear this is unofficial repo

I would love to try to take your suggestion and talk about this with the helm project and make it more official; what would you suggest be the best way to proceed with that? Like you can understand we are all helm fans :)