[jira] [Created] (LEGAL-573) Is Helm Chart an official artifact?

["Kaxil Naik (Jira)" <ji...@apache.org>]

Kaxil Naik created LEGAL-573:
--------------------------------

             Summary: Is Helm Chart an official artifact?
                 Key: LEGAL-573
                 URL: https://issues.apache.org/jira/browse/LEGAL-573
             Project: Legal Discuss
          Issue Type: Question
          Components: Policy Question
            Reporter: Kaxil Naik


Hi folks,

I am working towards releasing Helm Chart for Apache Airflow ([https://github.com/apache/airflow/tree/master/chart|https://github.com/apache/airflow/tree/master/chart]).

I have the following questions:

# Is Helm Chart considered an official artifact as described in https://www.apache.org/legal/release-policy.html#artifacts? Or is it considered "convenience packages/binaries"
# Do we need to go through a three 3 days voting period for releasing a new version of Helm Chart?
# If Yes to (1) and (2), does it mean the Helm Chart should reside in the official download repository which is https://dist.apache.org/repos/dist/release/airflow/ for us (Airflow PMC Members). Some of the other Apache Projects (Tike, Pulsar, Superset to name a few) have uploaded to either Github or Apache's Jfrog Artifact repository. Example: Apache Tika: https://cwiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm | Apache Superset: https://apache.github.io/superset/index.yaml / https://github.com/apache/superset/releases/download/superset-helm-chart-0.1.2/superset-0.1.2.tgz
# If Yes to (3) -- Helm strips comments in `Chart.yaml` file when creating a Helm Package: `helm package DIRECTORY` - which means Apache License at top of the file is stripped off which will fails License check during VOTING? Any suggestions?
# If Yes to (3) -- If we have Chart dependencies (airflow has a dependency on Postgres Chart) -- then it will bring the Helm Chart from Postgres which won't have License as Headers in their files. But when you run `helm package CHART_DIRECTORY` it bundles Chart + charts listed in dependencies, which makes it fail the LICENSE check again. Is the solution for it -- to just tar the source code and vote and that instead of tar generated by `helm package CHART_DIRECTORY` from source code?

I think we should consider Helm Chart as a convenience dependency and allow PMC's to release it as they seem fit, which is the case now but there are no guidelines from ASF regarding Helm Chart & Docker images which is why is some confusion.

My goal here is to get an agreement on the guideline which will help not only us at Airflow but all other ASF projects -- happy to help writing and adding (PR'ing) to ASF Release policies too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org