You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Kaxil Naik <ka...@gmail.com> on 2020/08/02 09:07:14 UTC
Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls
Hi Airflow devs,
Let's work towards delivering Airflow 2.0 together.
I have created a High-level Airflow 2.0 Planning doc (
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning).
This document is only intended for the process, objectives and the approach
(how we get to it) instead of a technical doc that discusses specific
Github issues/PRs/AIP .
We already have 2.0 Mileston (https://github.com/apache/airflow/milestone/3
- created by Ash) and the Wiki (
https://github.com/apache/airflow/issues/10085#issuecomment-667622228 --
Created by Kamil)
I have created a Shared Calendar to schedule regular calls (fortnightly -
every 15 days) to start planning for Airflow 2.0 and then keep a track of
the progress.
*Calendar Link*:
https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
I am planning to have our first call next *Monday, 10 August* at *5:30 GMT *to
kickoff the process and hear everyone's thoughts and discuss the approach,
thoughts and suggestions. Let me know if that time is good for everyone
interested in participating.
Regards,
Kaxil
Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls
Posted by Jarek Potiuk <Ja...@polidea.com>.
+1
On Wed, Aug 5, 2020 at 1:55 PM Kaxil Naik <ka...@gmail.com> wrote:
> I have scheduled the first meeting (*Monday, 10 August* at *5:30 GMT*) on
> the Shared Calendar.
>
> *Calendar Link*:
>
> https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
> The Calendar is also embedded on
> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
>
> For whatever reasons if the above links don't work for you,
> here is the link for the event details
>
> https://www.google.com/calendar/event?eid=NW00cTJiYjcxa3BnMzY2N211OTIyN2JhZjEgY19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bn&ctz=Europe/London
>
> Regards,
> Kaxil
>
> On Sun, Aug 2, 2020 at 11:09 AM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > Works for me for the time! And great to get it coming together.
> >
> > I think we might discuss the wiki/cwiki/issue offline before that
> > though :). I started a separate thread for that - also since I -
> > totally accidentally - caused all ApacheCommitters notified about our
> > upcoming 2.0 release ;)
> >
> > J,
> >
> > On Sun, Aug 2, 2020 at 11:53 AM Kaxil Naik <ka...@gmail.com> wrote:
> > >
> > > Aah yes, thanks for the correct link Tomek. I feel we should have
> > > everything in one place either wiki or cwiki (separate discussion --
> > maybe
> > > we can discuss this on our first call :-) )
> > >
> > >
> > >
> > > On Sun, Aug 2, 2020 at 10:42 AM Tomasz Urbaszek <tu...@apache.org>
> > > wrote:
> > >
> > > > Good to see that Airflow 2.0 is getting some traction! Thanks Kaxil
> for
> > > > bringing this topic to devlist.
> > > >
> > > > The proposed time is ok for me. Also is this the right link to Github
> > > > wiki with Airflow 2.0?
> > > > https://github.com/apache/airflow/wiki/Airflow-2.0
> > > >
> > > > Cheers,
> > > > Tomek
> > > >
> > > > On Sun, Aug 2, 2020 at 11:07 AM Kaxil Naik <ka...@gmail.com>
> > wrote:
> > > >
> > > > > Hi Airflow devs,
> > > > >
> > > > > Let's work towards delivering Airflow 2.0 together.
> > > > >
> > > > > I have created a High-level Airflow 2.0 Planning doc (
> > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
> > > > > ).
> > > > > This document is only intended for the process, objectives and the
> > > > approach
> > > > > (how we get to it) instead of a technical doc that discusses
> specific
> > > > > Github issues/PRs/AIP .
> > > > >
> > > > > We already have 2.0 Mileston (
> > > > > https://github.com/apache/airflow/milestone/3
> > > > > - created by Ash) and the Wiki (
> > > > >
> > https://github.com/apache/airflow/issues/10085#issuecomment-667622228 --
> > > > > Created by Kamil)
> > > > >
> > > > > I have created a Shared Calendar to schedule regular calls
> > (fortnightly -
> > > > > every 15 days) to start planning for Airflow 2.0 and then keep a
> > track of
> > > > > the progress.
> > > > >
> > > > > *Calendar Link*:
> > > > >
> > > > >
> > > >
> >
> https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
> > > > >
> > > > > I am planning to have our first call next *Monday, 10 August* at
> > *5:30
> > > > GMT
> > > > > *to
> > > > > kickoff the process and hear everyone's thoughts and discuss the
> > > > approach,
> > > > > thoughts and suggestions. Let me know if that time is good for
> > everyone
> > > > > interested in participating.
> > > > >
> > > > > Regards,
> > > > > Kaxil
> > > > >
> > > >
> >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea | Principal Software Engineer
> >
> > M: +48 660 796 129
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls
Posted by Kaxil Naik <ka...@gmail.com>.
I have scheduled the first meeting (*Monday, 10 August* at *5:30 GMT*) on
the Shared Calendar.
*Calendar Link*:
https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
The Calendar is also embedded on
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
For whatever reasons if the above links don't work for you,
here is the link for the event details
https://www.google.com/calendar/event?eid=NW00cTJiYjcxa3BnMzY2N211OTIyN2JhZjEgY19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bn&ctz=Europe/London
Regards,
Kaxil
On Sun, Aug 2, 2020 at 11:09 AM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Works for me for the time! And great to get it coming together.
>
> I think we might discuss the wiki/cwiki/issue offline before that
> though :). I started a separate thread for that - also since I -
> totally accidentally - caused all ApacheCommitters notified about our
> upcoming 2.0 release ;)
>
> J,
>
> On Sun, Aug 2, 2020 at 11:53 AM Kaxil Naik <ka...@gmail.com> wrote:
> >
> > Aah yes, thanks for the correct link Tomek. I feel we should have
> > everything in one place either wiki or cwiki (separate discussion --
> maybe
> > we can discuss this on our first call :-) )
> >
> >
> >
> > On Sun, Aug 2, 2020 at 10:42 AM Tomasz Urbaszek <tu...@apache.org>
> > wrote:
> >
> > > Good to see that Airflow 2.0 is getting some traction! Thanks Kaxil for
> > > bringing this topic to devlist.
> > >
> > > The proposed time is ok for me. Also is this the right link to Github
> > > wiki with Airflow 2.0?
> > > https://github.com/apache/airflow/wiki/Airflow-2.0
> > >
> > > Cheers,
> > > Tomek
> > >
> > > On Sun, Aug 2, 2020 at 11:07 AM Kaxil Naik <ka...@gmail.com>
> wrote:
> > >
> > > > Hi Airflow devs,
> > > >
> > > > Let's work towards delivering Airflow 2.0 together.
> > > >
> > > > I have created a High-level Airflow 2.0 Planning doc (
> > > >
> > >
> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
> > > > ).
> > > > This document is only intended for the process, objectives and the
> > > approach
> > > > (how we get to it) instead of a technical doc that discusses specific
> > > > Github issues/PRs/AIP .
> > > >
> > > > We already have 2.0 Mileston (
> > > > https://github.com/apache/airflow/milestone/3
> > > > - created by Ash) and the Wiki (
> > > >
> https://github.com/apache/airflow/issues/10085#issuecomment-667622228 --
> > > > Created by Kamil)
> > > >
> > > > I have created a Shared Calendar to schedule regular calls
> (fortnightly -
> > > > every 15 days) to start planning for Airflow 2.0 and then keep a
> track of
> > > > the progress.
> > > >
> > > > *Calendar Link*:
> > > >
> > > >
> > >
> https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
> > > >
> > > > I am planning to have our first call next *Monday, 10 August* at
> *5:30
> > > GMT
> > > > *to
> > > > kickoff the process and hear everyone's thoughts and discuss the
> > > approach,
> > > > thoughts and suggestions. Let me know if that time is good for
> everyone
> > > > interested in participating.
> > > >
> > > > Regards,
> > > > Kaxil
> > > >
> > >
>
>
>
> --
>
> Jarek Potiuk
> Polidea | Principal Software Engineer
>
> M: +48 660 796 129
>
Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls
Posted by Jarek Potiuk <Ja...@polidea.com>.
Works for me for the time! And great to get it coming together.
I think we might discuss the wiki/cwiki/issue offline before that
though :). I started a separate thread for that - also since I -
totally accidentally - caused all ApacheCommitters notified about our
upcoming 2.0 release ;)
J,
On Sun, Aug 2, 2020 at 11:53 AM Kaxil Naik <ka...@gmail.com> wrote:
>
> Aah yes, thanks for the correct link Tomek. I feel we should have
> everything in one place either wiki or cwiki (separate discussion -- maybe
> we can discuss this on our first call :-) )
>
>
>
> On Sun, Aug 2, 2020 at 10:42 AM Tomasz Urbaszek <tu...@apache.org>
> wrote:
>
> > Good to see that Airflow 2.0 is getting some traction! Thanks Kaxil for
> > bringing this topic to devlist.
> >
> > The proposed time is ok for me. Also is this the right link to Github
> > wiki with Airflow 2.0?
> > https://github.com/apache/airflow/wiki/Airflow-2.0
> >
> > Cheers,
> > Tomek
> >
> > On Sun, Aug 2, 2020 at 11:07 AM Kaxil Naik <ka...@gmail.com> wrote:
> >
> > > Hi Airflow devs,
> > >
> > > Let's work towards delivering Airflow 2.0 together.
> > >
> > > I have created a High-level Airflow 2.0 Planning doc (
> > >
> > https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
> > > ).
> > > This document is only intended for the process, objectives and the
> > approach
> > > (how we get to it) instead of a technical doc that discusses specific
> > > Github issues/PRs/AIP .
> > >
> > > We already have 2.0 Mileston (
> > > https://github.com/apache/airflow/milestone/3
> > > - created by Ash) and the Wiki (
> > > https://github.com/apache/airflow/issues/10085#issuecomment-667622228 --
> > > Created by Kamil)
> > >
> > > I have created a Shared Calendar to schedule regular calls (fortnightly -
> > > every 15 days) to start planning for Airflow 2.0 and then keep a track of
> > > the progress.
> > >
> > > *Calendar Link*:
> > >
> > >
> > https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
> > >
> > > I am planning to have our first call next *Monday, 10 August* at *5:30
> > GMT
> > > *to
> > > kickoff the process and hear everyone's thoughts and discuss the
> > approach,
> > > thoughts and suggestions. Let me know if that time is good for everyone
> > > interested in participating.
> > >
> > > Regards,
> > > Kaxil
> > >
> >
--
Jarek Potiuk
Polidea | Principal Software Engineer
M: +48 660 796 129
Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls
Posted by Kaxil Naik <ka...@gmail.com>.
Aah yes, thanks for the correct link Tomek. I feel we should have
everything in one place either wiki or cwiki (separate discussion -- maybe
we can discuss this on our first call :-) )
On Sun, Aug 2, 2020 at 10:42 AM Tomasz Urbaszek <tu...@apache.org>
wrote:
> Good to see that Airflow 2.0 is getting some traction! Thanks Kaxil for
> bringing this topic to devlist.
>
> The proposed time is ok for me. Also is this the right link to Github
> wiki with Airflow 2.0?
> https://github.com/apache/airflow/wiki/Airflow-2.0
>
> Cheers,
> Tomek
>
> On Sun, Aug 2, 2020 at 11:07 AM Kaxil Naik <ka...@gmail.com> wrote:
>
> > Hi Airflow devs,
> >
> > Let's work towards delivering Airflow 2.0 together.
> >
> > I have created a High-level Airflow 2.0 Planning doc (
> >
> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
> > ).
> > This document is only intended for the process, objectives and the
> approach
> > (how we get to it) instead of a technical doc that discusses specific
> > Github issues/PRs/AIP .
> >
> > We already have 2.0 Mileston (
> > https://github.com/apache/airflow/milestone/3
> > - created by Ash) and the Wiki (
> > https://github.com/apache/airflow/issues/10085#issuecomment-667622228 --
> > Created by Kamil)
> >
> > I have created a Shared Calendar to schedule regular calls (fortnightly -
> > every 15 days) to start planning for Airflow 2.0 and then keep a track of
> > the progress.
> >
> > *Calendar Link*:
> >
> >
> https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
> >
> > I am planning to have our first call next *Monday, 10 August* at *5:30
> GMT
> > *to
> > kickoff the process and hear everyone's thoughts and discuss the
> approach,
> > thoughts and suggestions. Let me know if that time is good for everyone
> > interested in participating.
> >
> > Regards,
> > Kaxil
> >
>
Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls
Posted by Tomasz Urbaszek <tu...@apache.org>.
Good to see that Airflow 2.0 is getting some traction! Thanks Kaxil for
bringing this topic to devlist.
The proposed time is ok for me. Also is this the right link to Github
wiki with Airflow 2.0?
https://github.com/apache/airflow/wiki/Airflow-2.0
Cheers,
Tomek
On Sun, Aug 2, 2020 at 11:07 AM Kaxil Naik <ka...@gmail.com> wrote:
> Hi Airflow devs,
>
> Let's work towards delivering Airflow 2.0 together.
>
> I have created a High-level Airflow 2.0 Planning doc (
> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+2.0+-+Planning
> ).
> This document is only intended for the process, objectives and the approach
> (how we get to it) instead of a technical doc that discusses specific
> Github issues/PRs/AIP .
>
> We already have 2.0 Mileston (
> https://github.com/apache/airflow/milestone/3
> - created by Ash) and the Wiki (
> https://github.com/apache/airflow/issues/10085#issuecomment-667622228 --
> Created by Kamil)
>
> I have created a Shared Calendar to schedule regular calls (fortnightly -
> every 15 days) to start planning for Airflow 2.0 and then keep a track of
> the progress.
>
> *Calendar Link*:
>
> https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t
>
> I am planning to have our first call next *Monday, 10 August* at *5:30 GMT
> *to
> kickoff the process and hear everyone's thoughts and discuss the approach,
> thoughts and suggestions. Let me know if that time is good for everyone
> interested in participating.
>
> Regards,
> Kaxil
>