Thanks Aizhamal for starting the conversation.
Thanks to Daniel Imberman for his support over the last year.

Iam definitely maintaining it. Just trying to prioritize it among
other things.

regs
Barni

On Thu, Sep 12, 2019 at 10:45 AM Aizhamal Nurmamat kyzy <aizha...@apache.org>
wrote:

> On Tao's comment: yes, the current author - Barni (cc'ed here) will
> continue to maintain the project :)
>
>
> On Thu, Sep 12, 2019 at 10:05 AM Daniel Imberman <
> dimberman.opensou...@gmail.com> wrote:
>
>> +1 here!
>>
>> On Thu, Sep 12, 2019 at 10:20 AM Jarek Potiuk <jarek.pot...@polidea.com>
>> wrote:
>>
>> > The name is indeed misleading. My proposal would be
>> > k8s-operator-for-airflow - this might make it unambiguous .
>> >
>> > czw., 12 wrz 2019, 16:17 użytkownik Jarek Potiuk <
>> jarek.pot...@polidea.com
>> > >
>> > napisał:
>> >
>> > > Fantastic! Strong +1 from me.
>> > >
>> > > To alleviate some of the concerns - we @Polidea are just starting a
>> > > project for big and serious customer where we will most likely use and
>> > > extend Kubernetes Operator.
>> > >
>> > > We have 3 people that could become contributors and commiters day
>> one, so
>> > > we can already help building community for it. Looking forward to
>> > following
>> > > the Apache way in this case !
>> > >
>> > > J.
>> > >
>> > > On Thu, Sep 12, 2019 at 7:23 AM Tao Feng <fengta...@gmail.com> wrote:
>> > >
>> > >> +1 as well. One question: does the original author still actively
>> > maintain
>> > >> or would like to continue maintaining the code base after the repo is
>> > >> moved
>> > >> to Airflow?
>> > >>
>> > >> On Wed, Sep 11, 2019 at 11:10 PM Sumit Maheshwari <
>> > sumeet.ma...@gmail.com
>> > >> >
>> > >> wrote:
>> > >>
>> > >> > Strong +1
>> > >> >
>> > >> > On Thu, Sep 12, 2019 at 7:29 AM Aizhamal Nurmamat kyzy <
>> > >> > aizha...@apache.org>
>> > >> > wrote:
>> > >> >
>> > >> > > Hello Airflow community,
>> > >> > >
>> > >> > > Over the last year, an engineer at Google developed, and open
>> > sourced
>> > >> a
>> > >> > > Kubernetes operator to run Airflow[1]. Anyone can use it to
>> deploy
>> > >> > Airflow
>> > >> > > on their k8s cluster freely.
>> > >> > >
>> > >> > > There have been discussions among community members that it
>> would be
>> > >> > great
>> > >> > > to donate the operator to Apache to be part of Airflow. That way
>> it
>> > is
>> > >> > easy
>> > >> > > to accept contributions from the community, improve and maintain
>> it
>> > >> > > collectively and transparently, along with the Airflow-k8s
>> > >> integration.
>> > >> > >
>> > >> > > This idea has been discussed at Google, and we have obtained all
>> > >> > necessary
>> > >> > > approvals to donate the operator.
>> > >> > >
>> > >> > > This discussion is to gather opinions from the community whether
>> you
>> > >> all
>> > >> > > think that it is a good idea. I personally think that this would
>> be
>> > a
>> > >> > great
>> > >> > > addition to Airflow.
>> > >> > >
>> > >> > > Please express your thoughts or concerns if you have any.
>> > >> > >
>> > >> > > The discussion will run for 72 hours, and if there is consensus
>> on
>> > >> > > accepting the donation, we will move the code under the Apache
>> > >> > > organization, to be owned by the Airflow community. If consensus
>> is
>> > >> not
>> > >> > > evident, we can have a vote after this discussion.
>> > >> > >
>> > >> > > Thanks,
>> > >> > > Aizhamal
>> > >> > >
>> > >> > > [1] https://github.com/GoogleCloudPlatform/airflow-operator
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> > >
>> >
>>
>

Reply via email to