Hello, 

I finally had some time after Airlfow 2.0 release and I opened discussion about 
the policy in legal-disc...@apache.org:
 
https://lists.apache.org/thread.html/r7c9ceb3d6c764119b14dfedb0e22957993d93cf529792c402aaa05fc%40%3Clegal-discuss.apache.org%3E

I propose we continue the discussion there:

On 2020/09/04 02:01:05, Ween Jiann <wjlee.2...@smu.edu.sg> wrote: 
> Hi Kamil,
> 
> What's your take of having the helm chart in a single repo?
> It will lessen the load to maintain tests and distribution.
> 
> On 2020/09/03 19:54:17, Kamil Breguła <kamil.breg...@polidea.com> wrote: 
> > Hello,
> > 
> > In the case of Airflow, we have developed our own chart and want to develop
> > and release it soon. For now, there is little chance that our community
> > will be interested in developing two independent charts.
> > https://github.com/apache/airflow/issues/10523
> > 
> > That would be the 3rd method of deploying Airflow on Kubernetes maintained
> > by our project. We have Kubernetes Operators also.
> > https://github.com/apache/airflow-on-k8s-operator
> > 
> > Best regards,
> > Kamil Breguła
> > 
> > On Thu, Sep 3, 2020 at 9:33 PM Ween Jiann <wjlee.2...@smu.edu.sg> wrote:
> > 
> > > Hi all,
> > >
> > > The helm team has deprecated the charts repository and will be archiving
> > > it in Nov. Here’s the link to the notice
> > > https://github.com/helm/charts/blob/master/README.md#deprecation-timeline
> > >
> > > It looks like that are quite a few charts for ASF projects such as
> > > Airflow, Hadoop, Spark, Solr (not exhaustive) that have yet to be adopted
> > > by anyone. It would make sense to re-home them into a single git in for
> > > example apache/charts. This would facilitate easier distribution of 
> > > various
> > > ASF projects via a single helm repo, and setting up tests and CI
> > > integration needs only to be done once.
> > >
> > > Cheers,
> > > WJ
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to