Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-13 Thread Justin Mclean
Hi, > If that clarifies everything, I think we can resume voting, correct? I'd like > to request others to vote please. I’’m satisfied with the explanation. The vote is lazy so you don’t aurally need any explicit +1s. Thanks, Justin -

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-13 Thread Aizhamal Nurmamat kyzy
Fair comment, Justin. The headers were in the file just 'aspirationally', and had not actually been donated to Kubernetes. If that clarifies everything, I think we can resume voting, correct? I'd like to request others to vote please. Thanks, Aizhamal On 2020/01/11 00:11:15, Justin Mclean wro

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-10 Thread Justin Mclean
Hi, Thanks for the explanation and I believe that clears it up. What I don’t understand is why you would put these headers on before it was donated to Kubernetes, the headers should reflect current ownership/license not potential future ownership/license. Thanks, Justin -

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-10 Thread Pablo Estrada
Hello, My name is Pablo, and I have supported some of the process of the donation of this code. The files with headers replaced in [1] were originally meant to be donated, and used as an external dependency under Kubernetes, hence their original headers. This plan did not happen, and thus we are

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-10 Thread Justin Mclean
Hi, > They are being manually vendored because we did not get through the process > of creating another repo to host them. I don’t know what you mean by "manually vendored”. > When we get there we could remove these files from the airflow operator > repo and add it as a dependency. So it is 3rd

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-10 Thread Barni Seetharaman
Hi Justin, They are being manually vendored because we did not get through the process of creating another repo to host them. But we plan to do so. When we get there we could remove these files from the airflow operator repo and add it as a dependency. There is another project doing the same: htt

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-09 Thread Aizhamal Nurmamat kyzy
+Barni Seetharaman could you chime in here to answer Justin's questions, please? On Thu, Jan 9, 2020 at 2:21 PM Justin Mclean wrote: > Hi, > > > Those files were authored by Barni, and we have his approval to > relicense and donate. > > I think we need some more information here. If he authored

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-09 Thread Justin Mclean
Hi, > Those files were authored by Barni, and we have his approval to relicense and > donate. I think we need some more information here. If he authored all of those files why did they have that header in this repo? Did they original come from another repo, if so where is that? Thanks, Justin

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-09 Thread Aizhamal Nurmamat kyzy
Hi Justin, Answers inline > I notice that some of the header previously said: > Copyright 2018 The Kubernetes Authors. > And some said: > Copyright 2018 Google LLC > > Given this is a donation from google did yo have permission from Kubernetes > to remove the "Copyright 2018 The Kubernetes A

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2020-01-01 Thread Justin Mclean
Hi, Do we have an answer to why this is the case? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] Accept airflow-on-k8s-operator to Airflow

2019-12-17 Thread Justin Mclean
Hi, I notice that some of the header previously said: Copyright 2018 The Kubernetes Authors. And some said: Copyright 2018 Google LLC Given this is a donation from google did yo have permission from Kubernetes to remove the "Copyright 2018 The Kubernetes Authors.” from files marked like that? T