-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OFFICIAL] Druid #3673
Comments
Hi @asdf2014 👋 Could you please publish this chart using an organization (i.e. Apache Druid) and host the charts repo using an apache.org subdomain? I understand you're a Druid maintainer, and we'd love to get this done. But at the moment, the package is published using your account in Artifact Hub and the repository is hosted in your personal GitHub account as well, at https://asdf2014.github.io/druid-helm/. This may be misleading for users, as it's not clear if this is something officially maintained by the Apache Druid team. For reference, there are some other official Apache packages, like Airflow and Solr, and both are published by Apache Airflow and Apache Solr, and hosted at https://airflow.apache.org/ and https://solr.apache.org/charts respectively. It'd be great to have the same for Druid 🙂 |
Hi @tegioz Thank you for viewing this. This Druid Helm Chart was originally separated from the main repository (https://github.com/apache/druid/), and the Druid official documentation has already pointed to this new repository specifically for maintaining the Druid Helm Chart, FYI, https://github.com/apache/druid/blame/master/README.md#L22 |
No worries! It's OK if it's not in the I just saw this PR, which explains why it got removed from the main repo. An official Druid chart should be owned, published and maintained by the Druid project, and it looks like this isn't clear at the moment. I'm really sorry but in the current state we cannot mark this package as official. But we'd be happy to do it as soon as the points described above are addressed. Hope this makes sense 🙂 |
@tegioz Got it, this background is somewhat complex. Initially, it was maintained within helm/charts by me and others, but later, due to cost reasons, it stopped maintaining Helm Charts centrally, and this Helm Chart was migrated to the Apache Druid main repository for maintenance by me. Subsequently, due to IP clearance reasons, it was spun off again... and here we are, we will maintain Druid Helm Chart in this new repo. You might not find a more official Druid Helm Chart elsewhere. However, I can deeply understand you need stick to these rules in Artifact Hub, that's ok, have good a day, thanks a lot. |
Thanks for understanding @asdf2014! I'm sure this is the most official Druid chart, so hopefully the situation will change soon and we can mark it as such. Have a great day you too! 👋 (will close this issue for now but please feel free to reopen it if the situation changes) |
In Artifact Hub, the
official
status means that the publisher owns the software a package primarily focuses on. If we consider the example of a chart used to install Consul, to obtain theofficial
status the publisher should be the owner of the Consul software (HashiCorp in this case), not just the chart. Similarly, a Tekton task used to perform operations on Google Cloud would need to be published by Google to be marked asofficial
. In the case of a MySQL operator, only one published by MySQL/Oracle would be consideredofficial
.The
official
status can be granted at the repository or package level. When it is granted for a repository, all packages available on it will display theofficial
badge, so all packages in the repository must be official. If only some of the packages in your repository are official, please list them in theOfficial packages
field below.artifacthub.io
): https://artifacthub.io/packages/helm/druid-helm/druidBefore applying for this status, please make sure your repository complies with the following requirements:
README.md
file with some documentation that can be displayed on Artifact Hub.The text was updated successfully, but these errors were encountered: