Nice!

On Fri, May 31, 2019 at 3:39 AM morefreeze <[email protected]> wrote:

> Congrats!
>
> On Fri, May 31, 2019 at 3:18 PM Bolke de Bruin <[email protected]> wrote:
>
> > Awesome!
> >
> > Sent from my iPhone
> >
> > > On 31 May 2019, at 08:15, Sumit Maheshwari <[email protected]>
> > wrote:
> > >
> > > Congrats Daniel. Really good news for Airflow.
> > >
> > > On Fri, May 31, 2019 at 5:05 AM Jarek Potiuk <[email protected]
> >
> > > wrote:
> > >
> > >> Congrats!
> > >>
> > >>> On Fri, May 31, 2019 at 12:54 AM Tao Feng <[email protected]>
> wrote:
> > >>>
> > >>> Daniel,
> > >>>
> > >>> Congrats! Win-win for you, Airflow and Astronomer!
> > >>>
> > >>> Best,
> > >>> -Tao
> > >>>
> > >>> On Thu, May 30, 2019 at 3:38 PM Arthur Wiedmer <
> > [email protected]
> > >>>
> > >>> wrote:
> > >>>
> > >>>> Daniel,
> > >>>>
> > >>>> Congratulations! Very exciting!
> > >>>>
> > >>>> Best,
> > >>>> Arthur
> > >>>>
> > >>>> On Thu, May 30, 2019 at 2:07 PM Daniel Imberman <
> > >>> [email protected]
> > >>>>>
> > >>>> wrote:
> > >>>>
> > >>>>> Hello Airflow community!
> > >>>>>
> > >>>>> I'm unbelievably excited to announce that after a (much-needed)
> > >>> vacation
> > >>>>> through the month of June (hmu if anyone happens to live in Chiang
> > >> Mai
> > >>> or
> > >>>>> Bali :) ), I will be joining Astronomer as a full-time
> > >>> advocate/committer
> > >>>>> for the Airflow community :D.
> > >>>>>
> > >>>>>
> > >>>>> *What this means for the airflow community*
> > >>>>>
> > >>>>> 1. Better support for the Kubernetes Executor
> > >>>>>
> > >>>>> The most noticeable change to the Aiflow community is that I will
> be
> > >>> able
> > >>>>> to focus a LOT more effort towards nurturing the Airflow +
> Kubernetes
> > >>>>> use-cases + support stories. For the last two years, I've
> > >> unfortunately
> > >>>>> only been able to work on this effort as a passion project/<20%
> > >>> project.
> > >>>>> With more flexibility I intend to become highly active on the
> airflow
> > >>>> slack
> > >>>>> and on the mailing list. I will be addressing bugs + helping users
> > >>>>> interested in adding features. There is certainly work to be done
> to
> > >>>>> stabilize/productionize this executor, and I look forward to taking
> > >>> this
> > >>>>> effort further in the near future.
> > >>>>>
> > >>>>> 2. Better Documentation
> > >>>>>
> > >>>>> A good friend of mine recently said "being a paid open source
> > >> committer
> > >>>>> means that it is now your job to smooth out the onramp for the rest
> > >> of
> > >>>> the
> > >>>>> community" and I take this charge very seriously. Once I am
> on-board
> > >>>>> full-time, I plan to write detailed documentation for running,
> > >>>>> contributing, and debugging k8s-based airflow workflows. I will
> also
> > >> be
> > >>>>> offering office hours, lunch + learns, twitch streams, and anything
> > >>> else
> > >>>>> that can help interested users join this incredibly supportive
> > >>> community.
> > >>>>>
> > >>>>> 3. A better Airflow + Kubernetes deployment story
> > >>>>>
> > >>>>> There are a few operators/helm charts/bash scripts floating around
> > >> the
> > >>>>> internet that are suggested for launching Airflow on Kubernetes. I
> am
> > >>>>> starting the process to reach out to these owners and consolidate a
> > >>>>> canonical set of deployment options to make launching airflow on
> k8s
> > >> as
> > >>>>> easy as possible
> > >>>>>
> > >>>>> ---
> > >>>>>
> > >>>>> I want to sincerely thank the team at astronomer for this
> incredible
> > >>>>> opportunity. Through my conversations and meetings with them I can
> > >> tell
> > >>>>> that this company truly cares about this project and have been
> > >>> consistent
> > >>>>> good actors in the community. I look forward to helping you all
> > >> further
> > >>>> in
> > >>>>> the near future!
> > >>>>>
> > >>>>> Best,
> > >>>>>
> > >>>>> Daniel
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >>
> > >> --
> > >>
> > >> Jarek Potiuk
> > >> Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >>
> > >> M: +48 660 796 129 <+48660796129>
> > >> E: [email protected]
> > >>
> >
>
>
> --
> One of my most productive days was throwing away 1000 lines of code.
>

Reply via email to