You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Bolke de Bruin <bd...@gmail.com> on 2018/11/24 11:57:16 UTC

[DISCUSS] Apache Airflow graduation from the incubator

Hi All,

With the Apache Airflow community healthy and growing, I think now would be a good time to 
discuss where we stand regarding to graduation from the Incubator, and what requirements remains. 

Apache Airflow entered incubation around 2 years ago, since then, the Airflow community learned 
a lot about how to do things in Apache ways. Now we are a very helpful and engaged community, 
ready to help on all questions from the Airflow community. We delivered multiple releases that have 
been increasing in quality ever since, now we can do self-driving releases in good cadence. 

The community is growing, new committers and PPMC members keep joining. We addressed almost all 
the maturity issues stipulated by Apache Project Maturity Model [1]. So final requirements remain, but
those just need a final nudge. Committers and contributors are invited to verify the list and pick up the last 
bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can see got resolved. 

Base on those, I believes it's time for us to graduate to TLP. [2] Any thoughts? 
And welcome advice from Airflow Mentors? 

Thanks, 

[1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
[2] https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project Regards,

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Dan Davydov <dd...@twitter.com.INVALID>.
+1 thank you for everyone who helped drive this (especially Bolke!).

On Tue, Nov 27, 2018 at 1:02 AM Tao Feng <fe...@gmail.com> wrote:

> And happy to help out any items for the TLP push.
>
> On Mon, Nov 26, 2018 at 9:53 PM Tao Feng <fe...@gmail.com> wrote:
>
> > +1 as well. (do we need to start another vote thread per Jakob's
> > suggestion?)
> >
> > Great to see the thriving community!
> >
> > On Sat, Nov 24, 2018 at 3:57 AM Bolke de Bruin <bd...@gmail.com>
> wrote:
> >
> >> Hi All,
> >>
> >> With the Apache Airflow community healthy and growing, I think now would
> >> be a good time to
> >> discuss where we stand regarding to graduation from the Incubator, and
> >> what requirements remains.
> >>
> >> Apache Airflow entered incubation around 2 years ago, since then, the
> >> Airflow community learned
> >> a lot about how to do things in Apache ways. Now we are a very helpful
> >> and engaged community,
> >> ready to help on all questions from the Airflow community. We delivered
> >> multiple releases that have
> >> been increasing in quality ever since, now we can do self-driving
> >> releases in good cadence.
> >>
> >> The community is growing, new committers and PPMC members keep joining.
> >> We addressed almost all
> >> the maturity issues stipulated by Apache Project Maturity Model [1]. So
> >> final requirements remain, but
> >> those just need a final nudge. Committers and contributors are invited
> to
> >> verify the list and pick up the last
> >> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can
> >> see got resolved.
> >>
> >> Base on those, I believes it's time for us to graduate to TLP. [2] Any
> >> thoughts?
> >> And welcome advice from Airflow Mentors?
> >>
> >> Thanks,
> >>
> >> [1]
> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >> [2]
> >>
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> >> Regards,
> >
> >
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Tao Feng <fe...@gmail.com>.
And happy to help out any items for the TLP push.

On Mon, Nov 26, 2018 at 9:53 PM Tao Feng <fe...@gmail.com> wrote:

> +1 as well. (do we need to start another vote thread per Jakob's
> suggestion?)
>
> Great to see the thriving community!
>
> On Sat, Nov 24, 2018 at 3:57 AM Bolke de Bruin <bd...@gmail.com> wrote:
>
>> Hi All,
>>
>> With the Apache Airflow community healthy and growing, I think now would
>> be a good time to
>> discuss where we stand regarding to graduation from the Incubator, and
>> what requirements remains.
>>
>> Apache Airflow entered incubation around 2 years ago, since then, the
>> Airflow community learned
>> a lot about how to do things in Apache ways. Now we are a very helpful
>> and engaged community,
>> ready to help on all questions from the Airflow community. We delivered
>> multiple releases that have
>> been increasing in quality ever since, now we can do self-driving
>> releases in good cadence.
>>
>> The community is growing, new committers and PPMC members keep joining.
>> We addressed almost all
>> the maturity issues stipulated by Apache Project Maturity Model [1]. So
>> final requirements remain, but
>> those just need a final nudge. Committers and contributors are invited to
>> verify the list and pick up the last
>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can
>> see got resolved.
>>
>> Base on those, I believes it's time for us to graduate to TLP. [2] Any
>> thoughts?
>> And welcome advice from Airflow Mentors?
>>
>> Thanks,
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>> [2]
>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>> Regards,
>
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Tao Feng <fe...@gmail.com>.
+1 as well. (do we need to start another vote thread per Jakob's
suggestion?)

Great to see the thriving community!

On Sat, Nov 24, 2018 at 3:57 AM Bolke de Bruin <bd...@gmail.com> wrote:

> Hi All,
>
> With the Apache Airflow community healthy and growing, I think now would
> be a good time to
> discuss where we stand regarding to graduation from the Incubator, and
> what requirements remains.
>
> Apache Airflow entered incubation around 2 years ago, since then, the
> Airflow community learned
> a lot about how to do things in Apache ways. Now we are a very helpful and
> engaged community,
> ready to help on all questions from the Airflow community. We delivered
> multiple releases that have
> been increasing in quality ever since, now we can do self-driving releases
> in good cadence.
>
> The community is growing, new committers and PPMC members keep joining. We
> addressed almost all
> the maturity issues stipulated by Apache Project Maturity Model [1]. So
> final requirements remain, but
> those just need a final nudge. Committers and contributors are invited to
> verify the list and pick up the last
> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can
> see got resolved.
>
> Base on those, I believes it's time for us to graduate to TLP. [2] Any
> thoughts?
> And welcome advice from Airflow Mentors?
>
> Thanks,
>
> [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> [2]
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> Regards,

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Kaxil Naik <ka...@gmail.com>.
It is about time :) for Airflow to be a TLP.

I will take a look at pending issues but I agree with that it is the
correct time for us to graduate to a TLP.

Regards,
Kaxil

On Mon, Nov 26, 2018 at 7:46 PM Bolke de Bruin <bd...@gmail.com> wrote:

> Ping!
>
> Sent from my iPhone
>
> > On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >
> > Hi All,
> >
> > With the Apache Airflow community healthy and growing, I think now would
> be a good time to
> > discuss where we stand regarding to graduation from the Incubator, and
> what requirements remains.
> >
> > Apache Airflow entered incubation around 2 years ago, since then, the
> Airflow community learned
> > a lot about how to do things in Apache ways. Now we are a very helpful
> and engaged community,
> > ready to help on all questions from the Airflow community. We delivered
> multiple releases that have
> > been increasing in quality ever since, now we can do self-driving
> releases in good cadence.
> >
> > The community is growing, new committers and PPMC members keep joining.
> We addressed almost all
> > the maturity issues stipulated by Apache Project Maturity Model [1]. So
> final requirements remain, but
> > those just need a final nudge. Committers and contributors are invited
> to verify the list and pick up the last
> > bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can
> see got resolved.
> >
> > Base on those, I believes it's time for us to graduate to TLP. [2] Any
> thoughts?
> > And welcome advice from Airflow Mentors?
> >
> > Thanks,
> >
> > [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > [2]
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> Regards,
>


-- 
*Kaxil Naik*
*Big Data Consultant *@ *Data Reply UK*
*Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j
Developer
*Phone: *+44 (0) 74820 88992
*LinkedIn*: https://www.linkedin.com/in/kaxil

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Chris Riccomini <cr...@apache.org>.
+1 as well. I’m glad to see the community is thriving.

On Mon, Nov 26, 2018 at 6:11 PM Maxime Beauchemin <
maximebeauchemin@gmail.com> wrote:

> This is great to see happen, it's been a long time coming! Also count me
> in, I'll be happy to help on that last push!
>
> On Mon, Nov 26, 2018 at 5:21 PM Hitesh Shah <hi...@apache.org> wrote:
>
> > +1. The Airflow community has come a long way since its addition to the
> > Incubator and I believe it is more than ready to graduate. Based on past
> > experience around all the "paperwork", I would suggest that the earliest
> > graduation date would be the January board meeting and working backwards
> to
> > plan out filling in the various wikis and triggering the relevant votes.
> >
> > thanks
> > Hitesh
> >
> >
> >
> > On Mon, Nov 26, 2018 at 2:09 PM Bolke de Bruin <bd...@gmail.com>
> wrote:
> >
> > > Hi Jakob
> > >
> > > Thanks for the vote of confidence! That's appreciated.
> > >
> > > I linked the maturity model and already did a grading (I think :-) ) in
> > my
> > > original mail, so one thing less to worry about. It's probably a good
> > idea
> > > if some of the other committers and contributers also take a look. 2
> > items
> > > I'm unsure about.
> > >
> > > Cheers
> > > Bolke
> > >
> > >
> > >
> > > Sent from my iPhone
> > >
> > > > On 26 Nov 2018, at 22:30, Jakob Homan <jg...@gmail.com> wrote:
> > > >
> > > > With my Mentor hat on, I'm entirely confident that Airflow is ready
> to
> > > > graduate.  The community broadly gets the Apache Way and operates
> > > > within it.  The community is healthy and engaged.  The last couple
> > > > releases went well, with no hitches whatsoever for the last one.
> > > >
> > > > The graduation process is mainly paperwork[1] and running VOTEs [2]
> > > > here and on the IPMC.  Last time I suggested this had to be done by
> > > > the Champion, which wasn't correct - anyone from the PPMC can do so.
> > > > I may have some free cycles over the next few weeks, so I'll take a
> > > > look at the check list to see what we can get out of the way, but any
> > > > of the PPMCers can also take items.  The IPMC also likes it if
> > > > Podlings go through and grade themselves on the Maturity Model[2], if
> > > > someone wants to do that.
> > > >
> > > > -Jakob
> > > >
> > > > [1] http://incubator.apache.org/projects/airflow.html
> > > > [2]
> > >
> >
> http://mail-archives.apache.org/mod_mbox/airflow-dev/201809.mbox/%3CCAMdzn8vNbKQr2FF8WcJydFj16q0bgn0B42jfu5h28RS-ZQ=whA@mail.gmail.com%3E
> > > > [3]
> > >
> >
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> > > >> On Mon, Nov 26, 2018 at 1:10 PM Stefan Seelmann <
> > > mail@stefan-seelmann.de> wrote:
> > > >>
> > > >> I agree that Apache Airflow should graduate.
> > > >>
> > > >> I'm only involved since beginning of this year, but the project did
> > two
> > > >> releases during that time, once TLP releasing becomes easier :)
> > > >>
> > > >> Regarding QU30 you may consider to use the ASF wide security mailing
> > > >> list [3] and process [4].
> > > >>
> > > >> Kind Regards,
> > > >> Stefan
> > > >>
> > > >> [3] https://www.apache.org/security/
> > > >> [4] https://www.apache.org/security/committers.html
> > > >>
> > > >>
> > > >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> > > >>> Ping!
> > > >>>
> > > >>> Sent from my iPhone
> > > >>>
> > > >>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com>
> wrote:
> > > >>>>
> > > >>>> Hi All,
> > > >>>>
> > > >>>> With the Apache Airflow community healthy and growing, I think now
> > > would be a good time to
> > > >>>> discuss where we stand regarding to graduation from the Incubator,
> > > and what requirements remains.
> > > >>>>
> > > >>>> Apache Airflow entered incubation around 2 years ago, since then,
> > the
> > > Airflow community learned
> > > >>>> a lot about how to do things in Apache ways. Now we are a very
> > > helpful and engaged community,
> > > >>>> ready to help on all questions from the Airflow community. We
> > > delivered multiple releases that have
> > > >>>> been increasing in quality ever since, now we can do self-driving
> > > releases in good cadence.
> > > >>>>
> > > >>>> The community is growing, new committers and PPMC members keep
> > > joining. We addressed almost all
> > > >>>> the maturity issues stipulated by Apache Project Maturity Model
> [1].
> > > So final requirements remain, but
> > > >>>> those just need a final nudge. Committers and contributors are
> > > invited to verify the list and pick up the last
> > > >>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues
> we
> > > can see got resolved.
> > > >>>>
> > > >>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> > > Any thoughts?
> > > >>>> And welcome advice from Airflow Mentors?
> > > >>>>
> > > >>>> Thanks,
> > > >>>>
> > > >>>> [1]
> > >
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > > >>>> [2]
> > >
> >
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> > > Regards,
> > > >>
> > >
> >
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Maxime Beauchemin <ma...@gmail.com>.
This is great to see happen, it's been a long time coming! Also count me
in, I'll be happy to help on that last push!

On Mon, Nov 26, 2018 at 5:21 PM Hitesh Shah <hi...@apache.org> wrote:

> +1. The Airflow community has come a long way since its addition to the
> Incubator and I believe it is more than ready to graduate. Based on past
> experience around all the "paperwork", I would suggest that the earliest
> graduation date would be the January board meeting and working backwards to
> plan out filling in the various wikis and triggering the relevant votes.
>
> thanks
> Hitesh
>
>
>
> On Mon, Nov 26, 2018 at 2:09 PM Bolke de Bruin <bd...@gmail.com> wrote:
>
> > Hi Jakob
> >
> > Thanks for the vote of confidence! That's appreciated.
> >
> > I linked the maturity model and already did a grading (I think :-) ) in
> my
> > original mail, so one thing less to worry about. It's probably a good
> idea
> > if some of the other committers and contributers also take a look. 2
> items
> > I'm unsure about.
> >
> > Cheers
> > Bolke
> >
> >
> >
> > Sent from my iPhone
> >
> > > On 26 Nov 2018, at 22:30, Jakob Homan <jg...@gmail.com> wrote:
> > >
> > > With my Mentor hat on, I'm entirely confident that Airflow is ready to
> > > graduate.  The community broadly gets the Apache Way and operates
> > > within it.  The community is healthy and engaged.  The last couple
> > > releases went well, with no hitches whatsoever for the last one.
> > >
> > > The graduation process is mainly paperwork[1] and running VOTEs [2]
> > > here and on the IPMC.  Last time I suggested this had to be done by
> > > the Champion, which wasn't correct - anyone from the PPMC can do so.
> > > I may have some free cycles over the next few weeks, so I'll take a
> > > look at the check list to see what we can get out of the way, but any
> > > of the PPMCers can also take items.  The IPMC also likes it if
> > > Podlings go through and grade themselves on the Maturity Model[2], if
> > > someone wants to do that.
> > >
> > > -Jakob
> > >
> > > [1] http://incubator.apache.org/projects/airflow.html
> > > [2]
> >
> http://mail-archives.apache.org/mod_mbox/airflow-dev/201809.mbox/%3CCAMdzn8vNbKQr2FF8WcJydFj16q0bgn0B42jfu5h28RS-ZQ=whA@mail.gmail.com%3E
> > > [3]
> >
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> > >> On Mon, Nov 26, 2018 at 1:10 PM Stefan Seelmann <
> > mail@stefan-seelmann.de> wrote:
> > >>
> > >> I agree that Apache Airflow should graduate.
> > >>
> > >> I'm only involved since beginning of this year, but the project did
> two
> > >> releases during that time, once TLP releasing becomes easier :)
> > >>
> > >> Regarding QU30 you may consider to use the ASF wide security mailing
> > >> list [3] and process [4].
> > >>
> > >> Kind Regards,
> > >> Stefan
> > >>
> > >> [3] https://www.apache.org/security/
> > >> [4] https://www.apache.org/security/committers.html
> > >>
> > >>
> > >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> > >>> Ping!
> > >>>
> > >>> Sent from my iPhone
> > >>>
> > >>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> > >>>>
> > >>>> Hi All,
> > >>>>
> > >>>> With the Apache Airflow community healthy and growing, I think now
> > would be a good time to
> > >>>> discuss where we stand regarding to graduation from the Incubator,
> > and what requirements remains.
> > >>>>
> > >>>> Apache Airflow entered incubation around 2 years ago, since then,
> the
> > Airflow community learned
> > >>>> a lot about how to do things in Apache ways. Now we are a very
> > helpful and engaged community,
> > >>>> ready to help on all questions from the Airflow community. We
> > delivered multiple releases that have
> > >>>> been increasing in quality ever since, now we can do self-driving
> > releases in good cadence.
> > >>>>
> > >>>> The community is growing, new committers and PPMC members keep
> > joining. We addressed almost all
> > >>>> the maturity issues stipulated by Apache Project Maturity Model [1].
> > So final requirements remain, but
> > >>>> those just need a final nudge. Committers and contributors are
> > invited to verify the list and pick up the last
> > >>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> > can see got resolved.
> > >>>>
> > >>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> > Any thoughts?
> > >>>> And welcome advice from Airflow Mentors?
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> [1]
> > https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > >>>> [2]
> >
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> > Regards,
> > >>
> >
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Hitesh Shah <hi...@apache.org>.
+1. The Airflow community has come a long way since its addition to the
Incubator and I believe it is more than ready to graduate. Based on past
experience around all the "paperwork", I would suggest that the earliest
graduation date would be the January board meeting and working backwards to
plan out filling in the various wikis and triggering the relevant votes.

thanks
Hitesh



On Mon, Nov 26, 2018 at 2:09 PM Bolke de Bruin <bd...@gmail.com> wrote:

> Hi Jakob
>
> Thanks for the vote of confidence! That's appreciated.
>
> I linked the maturity model and already did a grading (I think :-) ) in my
> original mail, so one thing less to worry about. It's probably a good idea
> if some of the other committers and contributers also take a look. 2 items
> I'm unsure about.
>
> Cheers
> Bolke
>
>
>
> Sent from my iPhone
>
> > On 26 Nov 2018, at 22:30, Jakob Homan <jg...@gmail.com> wrote:
> >
> > With my Mentor hat on, I'm entirely confident that Airflow is ready to
> > graduate.  The community broadly gets the Apache Way and operates
> > within it.  The community is healthy and engaged.  The last couple
> > releases went well, with no hitches whatsoever for the last one.
> >
> > The graduation process is mainly paperwork[1] and running VOTEs [2]
> > here and on the IPMC.  Last time I suggested this had to be done by
> > the Champion, which wasn't correct - anyone from the PPMC can do so.
> > I may have some free cycles over the next few weeks, so I'll take a
> > look at the check list to see what we can get out of the way, but any
> > of the PPMCers can also take items.  The IPMC also likes it if
> > Podlings go through and grade themselves on the Maturity Model[2], if
> > someone wants to do that.
> >
> > -Jakob
> >
> > [1] http://incubator.apache.org/projects/airflow.html
> > [2]
> http://mail-archives.apache.org/mod_mbox/airflow-dev/201809.mbox/%3CCAMdzn8vNbKQr2FF8WcJydFj16q0bgn0B42jfu5h28RS-ZQ=whA@mail.gmail.com%3E
> > [3]
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> >> On Mon, Nov 26, 2018 at 1:10 PM Stefan Seelmann <
> mail@stefan-seelmann.de> wrote:
> >>
> >> I agree that Apache Airflow should graduate.
> >>
> >> I'm only involved since beginning of this year, but the project did two
> >> releases during that time, once TLP releasing becomes easier :)
> >>
> >> Regarding QU30 you may consider to use the ASF wide security mailing
> >> list [3] and process [4].
> >>
> >> Kind Regards,
> >> Stefan
> >>
> >> [3] https://www.apache.org/security/
> >> [4] https://www.apache.org/security/committers.html
> >>
> >>
> >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> >>> Ping!
> >>>
> >>> Sent from my iPhone
> >>>
> >>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >>>>
> >>>> Hi All,
> >>>>
> >>>> With the Apache Airflow community healthy and growing, I think now
> would be a good time to
> >>>> discuss where we stand regarding to graduation from the Incubator,
> and what requirements remains.
> >>>>
> >>>> Apache Airflow entered incubation around 2 years ago, since then, the
> Airflow community learned
> >>>> a lot about how to do things in Apache ways. Now we are a very
> helpful and engaged community,
> >>>> ready to help on all questions from the Airflow community. We
> delivered multiple releases that have
> >>>> been increasing in quality ever since, now we can do self-driving
> releases in good cadence.
> >>>>
> >>>> The community is growing, new committers and PPMC members keep
> joining. We addressed almost all
> >>>> the maturity issues stipulated by Apache Project Maturity Model [1].
> So final requirements remain, but
> >>>> those just need a final nudge. Committers and contributors are
> invited to verify the list and pick up the last
> >>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> can see got resolved.
> >>>>
> >>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> Any thoughts?
> >>>> And welcome advice from Airflow Mentors?
> >>>>
> >>>> Thanks,
> >>>>
> >>>> [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >>>> [2]
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> Regards,
> >>
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Bolke de Bruin <bd...@gmail.com>.
Hi Jakob

Thanks for the vote of confidence! That's appreciated. 

I linked the maturity model and already did a grading (I think :-) ) in my original mail, so one thing less to worry about. It's probably a good idea if some of the other committers and contributers also take a look. 2 items I'm unsure about. 

Cheers
Bolke



Sent from my iPhone

> On 26 Nov 2018, at 22:30, Jakob Homan <jg...@gmail.com> wrote:
> 
> With my Mentor hat on, I'm entirely confident that Airflow is ready to
> graduate.  The community broadly gets the Apache Way and operates
> within it.  The community is healthy and engaged.  The last couple
> releases went well, with no hitches whatsoever for the last one.
> 
> The graduation process is mainly paperwork[1] and running VOTEs [2]
> here and on the IPMC.  Last time I suggested this had to be done by
> the Champion, which wasn't correct - anyone from the PPMC can do so.
> I may have some free cycles over the next few weeks, so I'll take a
> look at the check list to see what we can get out of the way, but any
> of the PPMCers can also take items.  The IPMC also likes it if
> Podlings go through and grade themselves on the Maturity Model[2], if
> someone wants to do that.
> 
> -Jakob
> 
> [1] http://incubator.apache.org/projects/airflow.html
> [2] http://mail-archives.apache.org/mod_mbox/airflow-dev/201809.mbox/%3CCAMdzn8vNbKQr2FF8WcJydFj16q0bgn0B42jfu5h28RS-ZQ=whA@mail.gmail.com%3E
> [3] https://community.apache.org/apache-way/apache-project-maturity-model.html
>> On Mon, Nov 26, 2018 at 1:10 PM Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>> 
>> I agree that Apache Airflow should graduate.
>> 
>> I'm only involved since beginning of this year, but the project did two
>> releases during that time, once TLP releasing becomes easier :)
>> 
>> Regarding QU30 you may consider to use the ASF wide security mailing
>> list [3] and process [4].
>> 
>> Kind Regards,
>> Stefan
>> 
>> [3] https://www.apache.org/security/
>> [4] https://www.apache.org/security/committers.html
>> 
>> 
>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>>> Ping!
>>> 
>>> Sent from my iPhone
>>> 
>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>>> 
>>>> Hi All,
>>>> 
>>>> With the Apache Airflow community healthy and growing, I think now would be a good time to
>>>> discuss where we stand regarding to graduation from the Incubator, and what requirements remains.
>>>> 
>>>> Apache Airflow entered incubation around 2 years ago, since then, the Airflow community learned
>>>> a lot about how to do things in Apache ways. Now we are a very helpful and engaged community,
>>>> ready to help on all questions from the Airflow community. We delivered multiple releases that have
>>>> been increasing in quality ever since, now we can do self-driving releases in good cadence.
>>>> 
>>>> The community is growing, new committers and PPMC members keep joining. We addressed almost all
>>>> the maturity issues stipulated by Apache Project Maturity Model [1]. So final requirements remain, but
>>>> those just need a final nudge. Committers and contributors are invited to verify the list and pick up the last
>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can see got resolved.
>>>> 
>>>> Base on those, I believes it's time for us to graduate to TLP. [2] Any thoughts?
>>>> And welcome advice from Airflow Mentors?
>>>> 
>>>> Thanks,
>>>> 
>>>> [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>>>> [2] https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project Regards,
>>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Jakob Homan <jg...@gmail.com>.
With my Mentor hat on, I'm entirely confident that Airflow is ready to
graduate.  The community broadly gets the Apache Way and operates
within it.  The community is healthy and engaged.  The last couple
releases went well, with no hitches whatsoever for the last one.

The graduation process is mainly paperwork[1] and running VOTEs [2]
here and on the IPMC.  Last time I suggested this had to be done by
the Champion, which wasn't correct - anyone from the PPMC can do so.
I may have some free cycles over the next few weeks, so I'll take a
look at the check list to see what we can get out of the way, but any
of the PPMCers can also take items.  The IPMC also likes it if
Podlings go through and grade themselves on the Maturity Model[2], if
someone wants to do that.

-Jakob

[1] http://incubator.apache.org/projects/airflow.html
[2] http://mail-archives.apache.org/mod_mbox/airflow-dev/201809.mbox/%3CCAMdzn8vNbKQr2FF8WcJydFj16q0bgn0B42jfu5h28RS-ZQ=whA@mail.gmail.com%3E
[3] https://community.apache.org/apache-way/apache-project-maturity-model.html
On Mon, Nov 26, 2018 at 1:10 PM Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> I agree that Apache Airflow should graduate.
>
> I'm only involved since beginning of this year, but the project did two
> releases during that time, once TLP releasing becomes easier :)
>
> Regarding QU30 you may consider to use the ASF wide security mailing
> list [3] and process [4].
>
> Kind Regards,
> Stefan
>
> [3] https://www.apache.org/security/
> [4] https://www.apache.org/security/committers.html
>
>
> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> > Ping!
> >
> > Sent from my iPhone
> >
> >> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >>
> >> Hi All,
> >>
> >> With the Apache Airflow community healthy and growing, I think now would be a good time to
> >> discuss where we stand regarding to graduation from the Incubator, and what requirements remains.
> >>
> >> Apache Airflow entered incubation around 2 years ago, since then, the Airflow community learned
> >> a lot about how to do things in Apache ways. Now we are a very helpful and engaged community,
> >> ready to help on all questions from the Airflow community. We delivered multiple releases that have
> >> been increasing in quality ever since, now we can do self-driving releases in good cadence.
> >>
> >> The community is growing, new committers and PPMC members keep joining. We addressed almost all
> >> the maturity issues stipulated by Apache Project Maturity Model [1]. So final requirements remain, but
> >> those just need a final nudge. Committers and contributors are invited to verify the list and pick up the last
> >> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can see got resolved.
> >>
> >> Base on those, I believes it's time for us to graduate to TLP. [2] Any thoughts?
> >> And welcome advice from Airflow Mentors?
> >>
> >> Thanks,
> >>
> >> [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >> [2] https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project Regards,
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Kaxil Naik <ka...@gmail.com>.
I have updated http://incubator.apache.org/projects/airflow.html with news
(all our announcements since 2016), added links, add links to incubation
status reports.

@Jakob Homan <jg...@apache.org> - Let me know if we need to update
anything else.

Regards,
Kaxil

On Wed, Nov 28, 2018 at 8:00 PM Kaxil Naik <ka...@gmail.com> wrote:

> Definitely willing to pick up the paperwork at
> http://incubator.apache.org/projects/airflow.html .
>
> @Jakob Homan <jg...@apache.org>  Is there any guide on what needs to be
> filled out?
>
>
>
> On Wed, Nov 28, 2018 at 6:04 PM Bolke de Bruin <bd...@gmail.com> wrote:
>
>> Ping!
>>
>> Verstuurd vanaf mijn iPad
>>
>> > Op 27 nov. 2018 om 21:39 heeft Bolke de Bruin <bd...@gmail.com> het
>> volgende geschreven:
>> >
>> > Hi Folks,
>> >
>> > Thanks all for your responses and particularly Stefan for his
>> suggestion to use the generic Apache way to handle security issues. This
>> seems to be an accepted way for more projects, so I have added this to the
>> maturity evaluation[1] and marked is as resolved. While handling the GPL
>> library can be nicer we are already in compliance with CD30, so @Fokko and
>> @Ash if you want to help out towards graduation please spend your time
>> elsewhere like fixing CO50. This means adding a page to confluence that
>> describes how to become a committer on the project. As we are following
>> Apache many examples of other projects are around[2]
>> >
>> > Then there is the paperwork[3] as referred to by Jakob. This mainly
>> concerns filling in some items, maybe here and there creation some
>> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
>> this up? @Sid can you share how to edit that page?
>> >
>> > If we have resolved these items in my opinion we can start the voting
>> here and at the IPMC thereafter, targeting the board meeting of January for
>> graduation. How’s that for a New Year’s resolution?
>> >
>> > Cheers!
>> > Bolke
>> >
>> > P.S. Would it be nice to have updated graduation web page? Maybe one of
>> the contributors/community members likes to take a stab at this[4]
>> >
>> > [1]
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>> > [2]
>> https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
>> > [3] http://incubator.apache.org/projects/airflow.html
>> > [4] https://airflow.apache.org/
>> >
>> >
>> >
>> >> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
>> wrote:
>> >>
>> >> +1 from my side. Would be awesome to graduate Airflow
>> >>
>> >> If time allows, I'll also dive into CD30.
>> >>
>> >> Cheers, Fokko
>> >>
>> >> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <ash@apache.org
>> >:
>> >>
>> >>> Oarsome Bolke, thanks for starting this.
>> >>>
>> >>> It looks like we are closer than I thought!
>> >>>
>> >>> We can use those security lists (though having our own would be nice)
>> -
>> >>> either way we will need to make this prominent in the docs.
>> >>>
>> >>> Couple of points
>> >>>
>> >>> CS10: that github link is only visible to members of the team
>> >>>
>> >>> CD30: probably good as it is, we may want to do
>> >>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
>> >>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the
>> last
>> >>> niggle of the GPL env var at install time (but not a hard
>> requirement, just
>> >>> nice)
>> >>>
>> >>> -ash
>> >>>
>> >>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
>> >>> wrote:
>> >>>>
>> >>>> I agree that Apache Airflow should graduate.
>> >>>>
>> >>>> I'm only involved since beginning of this year, but the project did
>> two
>> >>>> releases during that time, once TLP releasing becomes easier :)
>> >>>>
>> >>>> Regarding QU30 you may consider to use the ASF wide security mailing
>> >>>> list [3] and process [4].
>> >>>>
>> >>>> Kind Regards,
>> >>>> Stefan
>> >>>>
>> >>>> [3] https://www.apache.org/security/
>> >>>> [4] https://www.apache.org/security/committers.html
>> >>>>
>> >>>>
>> >>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>> >>>>> Ping!
>> >>>>>
>> >>>>> Sent from my iPhone
>> >>>>>
>> >>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>> Hi All,
>> >>>>>>
>> >>>>>> With the Apache Airflow community healthy and growing, I think now
>> >>> would be a good time to
>> >>>>>> discuss where we stand regarding to graduation from the Incubator,
>> and
>> >>> what requirements remains.
>> >>>>>>
>> >>>>>> Apache Airflow entered incubation around 2 years ago, since then,
>> the
>> >>> Airflow community learned
>> >>>>>> a lot about how to do things in Apache ways. Now we are a very
>> helpful
>> >>> and engaged community,
>> >>>>>> ready to help on all questions from the Airflow community. We
>> >>> delivered multiple releases that have
>> >>>>>> been increasing in quality ever since, now we can do self-driving
>> >>> releases in good cadence.
>> >>>>>>
>> >>>>>> The community is growing, new committers and PPMC members keep
>> >>> joining. We addressed almost all
>> >>>>>> the maturity issues stipulated by Apache Project Maturity Model
>> [1].
>> >>> So final requirements remain, but
>> >>>>>> those just need a final nudge. Committers and contributors are
>> invited
>> >>> to verify the list and pick up the last
>> >>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues
>> we
>> >>> can see got resolved.
>> >>>>>>
>> >>>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
>> Any
>> >>> thoughts?
>> >>>>>> And welcome advice from Airflow Mentors?
>> >>>>>>
>> >>>>>> Thanks,
>> >>>>>>
>> >>>>>> [1]
>> >>>
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>> >>>>>> [2]
>> >>>
>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>> >>> Regards,
>> >>>>
>> >>>
>> >>>
>> >
>>
>
>
> --
> *Kaxil Naik*
> *Big Data Consultant *@ *Data Reply UK*
> *Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j
> Developer
> *Phone: *+44 (0) 74820 88992
> *LinkedIn*: https://www.linkedin.com/in/kaxil
>


-- 
*Kaxil Naik*
*Big Data Consultant *@ *Data Reply UK*
*Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j
Developer
*Phone: *+44 (0) 74820 88992
*LinkedIn*: https://www.linkedin.com/in/kaxil

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Kaxil Naik <ka...@gmail.com>.
Definitely willing to pick up the paperwork at
http://incubator.apache.org/projects/airflow.html .

@Jakob Homan <jg...@apache.org>  Is there any guide on what needs to be
filled out?



On Wed, Nov 28, 2018 at 6:04 PM Bolke de Bruin <bd...@gmail.com> wrote:

> Ping!
>
> Verstuurd vanaf mijn iPad
>
> > Op 27 nov. 2018 om 21:39 heeft Bolke de Bruin <bd...@gmail.com> het
> volgende geschreven:
> >
> > Hi Folks,
> >
> > Thanks all for your responses and particularly Stefan for his suggestion
> to use the generic Apache way to handle security issues. This seems to be
> an accepted way for more projects, so I have added this to the maturity
> evaluation[1] and marked is as resolved. While handling the GPL library can
> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
> want to help out towards graduation please spend your time elsewhere like
> fixing CO50. This means adding a page to confluence that describes how to
> become a committer on the project. As we are following Apache many examples
> of other projects are around[2]
> >
> > Then there is the paperwork[3] as referred to by Jakob. This mainly
> concerns filling in some items, maybe here and there creation some
> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
> this up? @Sid can you share how to edit that page?
> >
> > If we have resolved these items in my opinion we can start the voting
> here and at the IPMC thereafter, targeting the board meeting of January for
> graduation. How’s that for a New Year’s resolution?
> >
> > Cheers!
> > Bolke
> >
> > P.S. Would it be nice to have updated graduation web page? Maybe one of
> the contributors/community members likes to take a stab at this[4]
> >
> > [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > [2]
> https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> > [3] http://incubator.apache.org/projects/airflow.html
> > [4] https://airflow.apache.org/
> >
> >
> >
> >> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
> wrote:
> >>
> >> +1 from my side. Would be awesome to graduate Airflow
> >>
> >> If time allows, I'll also dive into CD30.
> >>
> >> Cheers, Fokko
> >>
> >> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
> >>
> >>> Oarsome Bolke, thanks for starting this.
> >>>
> >>> It looks like we are closer than I thought!
> >>>
> >>> We can use those security lists (though having our own would be nice) -
> >>> either way we will need to make this prominent in the docs.
> >>>
> >>> Couple of points
> >>>
> >>> CS10: that github link is only visible to members of the team
> >>>
> >>> CD30: probably good as it is, we may want to do
> >>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> >>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
> >>> niggle of the GPL env var at install time (but not a hard requirement,
> just
> >>> nice)
> >>>
> >>> -ash
> >>>
> >>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
> >>> wrote:
> >>>>
> >>>> I agree that Apache Airflow should graduate.
> >>>>
> >>>> I'm only involved since beginning of this year, but the project did
> two
> >>>> releases during that time, once TLP releasing becomes easier :)
> >>>>
> >>>> Regarding QU30 you may consider to use the ASF wide security mailing
> >>>> list [3] and process [4].
> >>>>
> >>>> Kind Regards,
> >>>> Stefan
> >>>>
> >>>> [3] https://www.apache.org/security/
> >>>> [4] https://www.apache.org/security/committers.html
> >>>>
> >>>>
> >>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> >>>>> Ping!
> >>>>>
> >>>>> Sent from my iPhone
> >>>>>
> >>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >>>>>>
> >>>>>> Hi All,
> >>>>>>
> >>>>>> With the Apache Airflow community healthy and growing, I think now
> >>> would be a good time to
> >>>>>> discuss where we stand regarding to graduation from the Incubator,
> and
> >>> what requirements remains.
> >>>>>>
> >>>>>> Apache Airflow entered incubation around 2 years ago, since then,
> the
> >>> Airflow community learned
> >>>>>> a lot about how to do things in Apache ways. Now we are a very
> helpful
> >>> and engaged community,
> >>>>>> ready to help on all questions from the Airflow community. We
> >>> delivered multiple releases that have
> >>>>>> been increasing in quality ever since, now we can do self-driving
> >>> releases in good cadence.
> >>>>>>
> >>>>>> The community is growing, new committers and PPMC members keep
> >>> joining. We addressed almost all
> >>>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
> >>> So final requirements remain, but
> >>>>>> those just need a final nudge. Committers and contributors are
> invited
> >>> to verify the list and pick up the last
> >>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> >>> can see got resolved.
> >>>>>>
> >>>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> Any
> >>> thoughts?
> >>>>>> And welcome advice from Airflow Mentors?
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> [1]
> >>>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >>>>>> [2]
> >>>
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> >>> Regards,
> >>>>
> >>>
> >>>
> >
>


-- 
*Kaxil Naik*
*Big Data Consultant *@ *Data Reply UK*
*Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j
Developer
*Phone: *+44 (0) 74820 88992
*LinkedIn*: https://www.linkedin.com/in/kaxil

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Bolke de Bruin <bd...@gmail.com>.
Ping!

Verstuurd vanaf mijn iPad

> Op 27 nov. 2018 om 21:39 heeft Bolke de Bruin <bd...@gmail.com> het volgende geschreven:
> 
> Hi Folks,
> 
> Thanks all for your responses and particularly Stefan for his suggestion to use the generic Apache way to handle security issues. This seems to be an accepted way for more projects, so I have added this to the maturity evaluation[1] and marked is as resolved. While handling the GPL library can be nicer we are already in compliance with CD30, so @Fokko and @Ash if you want to help out towards graduation please spend your time elsewhere like fixing CO50. This means adding a page to confluence that describes how to become a committer on the project. As we are following Apache many examples of other projects are around[2]
> 
> Then there is the paperwork[3] as referred to by Jakob. This mainly concerns filling in some items, maybe here and there creation some documentation but I don't think much. @Kaxil, @Tao: are you willing to pick this up? @Sid can you share how to edit that page? 
> 
> If we have resolved these items in my opinion we can start the voting here and at the IPMC thereafter, targeting the board meeting of January for graduation. How’s that for a New Year’s resolution?
> 
> Cheers!
> Bolke
> 
> P.S. Would it be nice to have updated graduation web page? Maybe one of the contributors/community members likes to take a stab at this[4]
> 
> [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> [3] http://incubator.apache.org/projects/airflow.html
> [4] https://airflow.apache.org/
> 
> 
> 
>> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl> wrote:
>> 
>> +1 from my side. Would be awesome to graduate Airflow
>> 
>> If time allows, I'll also dive into CD30.
>> 
>> Cheers, Fokko
>> 
>> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
>> 
>>> Oarsome Bolke, thanks for starting this.
>>> 
>>> It looks like we are closer than I thought!
>>> 
>>> We can use those security lists (though having our own would be nice) -
>>> either way we will need to make this prominent in the docs.
>>> 
>>> Couple of points
>>> 
>>> CS10: that github link is only visible to members of the team
>>> 
>>> CD30: probably good as it is, we may want to do
>>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
>>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
>>> niggle of the GPL env var at install time (but not a hard requirement, just
>>> nice)
>>> 
>>> -ash
>>> 
>>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
>>> wrote:
>>>> 
>>>> I agree that Apache Airflow should graduate.
>>>> 
>>>> I'm only involved since beginning of this year, but the project did two
>>>> releases during that time, once TLP releasing becomes easier :)
>>>> 
>>>> Regarding QU30 you may consider to use the ASF wide security mailing
>>>> list [3] and process [4].
>>>> 
>>>> Kind Regards,
>>>> Stefan
>>>> 
>>>> [3] https://www.apache.org/security/
>>>> [4] https://www.apache.org/security/committers.html
>>>> 
>>>> 
>>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>>>>> Ping!
>>>>> 
>>>>> Sent from my iPhone
>>>>> 
>>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>>>>> 
>>>>>> Hi All,
>>>>>> 
>>>>>> With the Apache Airflow community healthy and growing, I think now
>>> would be a good time to
>>>>>> discuss where we stand regarding to graduation from the Incubator, and
>>> what requirements remains.
>>>>>> 
>>>>>> Apache Airflow entered incubation around 2 years ago, since then, the
>>> Airflow community learned
>>>>>> a lot about how to do things in Apache ways. Now we are a very helpful
>>> and engaged community,
>>>>>> ready to help on all questions from the Airflow community. We
>>> delivered multiple releases that have
>>>>>> been increasing in quality ever since, now we can do self-driving
>>> releases in good cadence.
>>>>>> 
>>>>>> The community is growing, new committers and PPMC members keep
>>> joining. We addressed almost all
>>>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
>>> So final requirements remain, but
>>>>>> those just need a final nudge. Committers and contributors are invited
>>> to verify the list and pick up the last
>>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
>>> can see got resolved.
>>>>>> 
>>>>>> Base on those, I believes it's time for us to graduate to TLP. [2] Any
>>> thoughts?
>>>>>> And welcome advice from Airflow Mentors?
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> [1]
>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>>>>>> [2]
>>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>>> Regards,
>>>> 
>>> 
>>> 
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
Ash,

I can pick this up as early as the beginning of next week. Right now this
is what we have:
https://cwiki.apache.org/confluence/display/AIRFLOW/Committers But I might
extend it a little to make it a bit more clear.

Cheers, Fokko

Op zo 2 dec. 2018 om 12:56 schreef Sid Anand <sa...@apache.org>:

> Great!
>
> -s
>
> On Sun, Dec 2, 2018 at 5:53 AM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > I've created two tickets to add QU30 and CO50 to our docs.
> >
> > (I think even if we use sec@a.o we should still add something to our
> docs
> > saying how to do it)
> >
> > https://issues.apache.org/jira/browse/AIRFLOW-3430 -- Fokko: did you get
> > anywhere on this?
> > https://issues.apache.org/jira/browse/AIRFLOW-3431 -- I'll make a start
> > on this
> >
> > -ash
> >
> > > On 30 Nov 2018, at 22:06, Bolke de Bruin <bd...@gmail.com> wrote:
> > >
> > > Thanks Jakob!
> > >
> > > Verstuurd vanaf mijn iPad
> > >
> > >> Op 30 nov. 2018 om 22:49 heeft Jakob Homan <jg...@gmail.com> het
> > volgende geschreven:
> > >>
> > >> I've finished the paperwork.  I don't seem to have karma to trigger
> > >> the build on Jenkins, so we'll just wait for the daily rebuild.  With
> > >> that, I've opened the VOTE thread as well.  Thanks everybody.
> > >>> On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan <jg...@gmail.com>
> wrote:
> > >>>
> > >>> I'll finish up the template at
> > >>> http://incubator.apache.org/projects/airflow.html tomorrow or Friday
> > >>> (I *think* you have to be an IPMC member to update it since it lives
> > >>> in the Incubator SVN).  Looks like there's no actual work to do, just
> > >>> marking stuff that has been done but not yet recorded, and verifying
> > >>> some licenses.
> > >>>
> > >>> -Jakob
> > >>>
> > >>>
> > >>>
> > >>>> On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com>
> wrote:
> > >>>>
> > >>>> Sorry, just saw Kaxil's latest email. Kaxil, is there anything else
> I
> > could
> > >>>> help with?
> > >>>>
> > >>>> Thanks,
> > >>>> -Tao
> > >>>>
> > >>>>> On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com>
> > wrote:
> > >>>>>
> > >>>>> I would like to help on the documentation. Let me take a look at
> it.
> > I
> > >>>>> will work Kaxil on that.
> > >>>>>
> > >>>>>> On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <
> bdbruin@gmail.com>
> > wrote:
> > >>>>>>
> > >>>>>> Hi Folks,
> > >>>>>>
> > >>>>>> Thanks all for your responses and particularly Stefan for his
> > suggestion
> > >>>>>> to use the generic Apache way to handle security issues. This
> seems
> > to be
> > >>>>>> an accepted way for more projects, so I have added this to the
> > maturity
> > >>>>>> evaluation[1] and marked is as resolved. While handling the GPL
> > library can
> > >>>>>> be nicer we are already in compliance with CD30, so @Fokko and
> @Ash
> > if you
> > >>>>>> want to help out towards graduation please spend your time
> > elsewhere like
> > >>>>>> fixing CO50. This means adding a page to confluence that describes
> > how to
> > >>>>>> become a committer on the project. As we are following Apache many
> > examples
> > >>>>>> of other projects are around[2]
> > >>>>>>
> > >>>>>> Then there is the paperwork[3] as referred to by Jakob. This
> mainly
> > >>>>>> concerns filling in some items, maybe here and there creation some
> > >>>>>> documentation but I don't think much. @Kaxil, @Tao: are you
> willing
> > to pick
> > >>>>>> this up? @Sid can you share how to edit that page?
> > >>>>>>
> > >>>>>> If we have resolved these items in my opinion we can start the
> > voting
> > >>>>>> here and at the IPMC thereafter, targeting the board meeting of
> > January for
> > >>>>>> graduation. How’s that for a New Year’s resolution?
> > >>>>>>
> > >>>>>> Cheers!
> > >>>>>> Bolke
> > >>>>>>
> > >>>>>> P.S. Would it be nice to have updated graduation web page? Maybe
> > one of
> > >>>>>> the contributors/community members likes to take a stab at this[4]
> > >>>>>>
> > >>>>>> [1]
> > >>>>>>
> > https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> <
> > >>>>>>
> > https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
> > >>>>>> [2]
> > https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> > >>>>>> <
> > https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
> > >>>>>> [3] http://incubator.apache.org/projects/airflow.html <
> > >>>>>> http://incubator.apache.org/projects/airflow.html>
> > >>>>>> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fokko@driesprong.frl
> >
> > >>>>>> wrote:
> > >>>>>>>
> > >>>>>>> +1 from my side. Would be awesome to graduate Airflow
> > >>>>>>>
> > >>>>>>> If time allows, I'll also dive into CD30.
> > >>>>>>>
> > >>>>>>> Cheers, Fokko
> > >>>>>>>
> > >>>>>>> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <
> > ash@apache.org>:
> > >>>>>>>
> > >>>>>>>> Oarsome Bolke, thanks for starting this.
> > >>>>>>>>
> > >>>>>>>> It looks like we are closer than I thought!
> > >>>>>>>>
> > >>>>>>>> We can use those security lists (though having our own would be
> > nice) -
> > >>>>>>>> either way we will need to make this prominent in the docs.
> > >>>>>>>>
> > >>>>>>>> Couple of points
> > >>>>>>>>
> > >>>>>>>> CS10: that github link is only visible to members of the team
> > >>>>>>>>
> > >>>>>>>> CD30: probably good as it is, we may want to do
> > >>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> > >>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove
> > the last
> > >>>>>>>> niggle of the GPL env var at install time (but not a hard
> > requirement,
> > >>>>>> just
> > >>>>>>>> nice)
> > >>>>>>>>
> > >>>>>>>> -ash
> > >>>>>>>>
> > >>>>>>>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <
> > mail@stefan-seelmann.de>
> > >>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>> I agree that Apache Airflow should graduate.
> > >>>>>>>>>
> > >>>>>>>>> I'm only involved since beginning of this year, but the project
> > did
> > >>>>>> two
> > >>>>>>>>> releases during that time, once TLP releasing becomes easier :)
> > >>>>>>>>>
> > >>>>>>>>> Regarding QU30 you may consider to use the ASF wide security
> > mailing
> > >>>>>>>>> list [3] and process [4].
> > >>>>>>>>>
> > >>>>>>>>> Kind Regards,
> > >>>>>>>>> Stefan
> > >>>>>>>>>
> > >>>>>>>>> [3] https://www.apache.org/security/
> > >>>>>>>>> [4] https://www.apache.org/security/committers.html
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> > >>>>>>>>>> Ping!
> > >>>>>>>>>>
> > >>>>>>>>>> Sent from my iPhone
> > >>>>>>>>>>
> > >>>>>>>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com>
> > wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> Hi All,
> > >>>>>>>>>>>
> > >>>>>>>>>>> With the Apache Airflow community healthy and growing, I
> think
> > now
> > >>>>>>>> would be a good time to
> > >>>>>>>>>>> discuss where we stand regarding to graduation from the
> > Incubator,
> > >>>>>> and
> > >>>>>>>> what requirements remains.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Apache Airflow entered incubation around 2 years ago, since
> > then,
> > >>>>>> the
> > >>>>>>>> Airflow community learned
> > >>>>>>>>>>> a lot about how to do things in Apache ways. Now we are a
> very
> > >>>>>> helpful
> > >>>>>>>> and engaged community,
> > >>>>>>>>>>> ready to help on all questions from the Airflow community. We
> > >>>>>>>> delivered multiple releases that have
> > >>>>>>>>>>> been increasing in quality ever since, now we can do
> > self-driving
> > >>>>>>>> releases in good cadence.
> > >>>>>>>>>>>
> > >>>>>>>>>>> The community is growing, new committers and PPMC members
> keep
> > >>>>>>>> joining. We addressed almost all
> > >>>>>>>>>>> the maturity issues stipulated by Apache Project Maturity
> > Model [1].
> > >>>>>>>> So final requirements remain, but
> > >>>>>>>>>>> those just need a final nudge. Committers and contributors
> are
> > >>>>>> invited
> > >>>>>>>> to verify the list and pick up the last
> > >>>>>>>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP
> > issues we
> > >>>>>>>> can see got resolved.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Base on those, I believes it's time for us to graduate to
> TLP.
> > [2]
> > >>>>>> Any
> > >>>>>>>> thoughts?
> > >>>>>>>>>>> And welcome advice from Airflow Mentors?
> > >>>>>>>>>>>
> > >>>>>>>>>>> Thanks,
> > >>>>>>>>>>>
> > >>>>>>>>>>> [1]
> > >>>>>>>>
> > >>>>>>
> > https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > >>>>>>>>>>> [2]
> > >>>>>>>>
> > >>>>>>
> >
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> > >>>>>>>> Regards,
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>>
> >
> >
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Sid Anand <sa...@apache.org>.
Great!

-s

On Sun, Dec 2, 2018 at 5:53 AM Ash Berlin-Taylor <as...@apache.org> wrote:

> I've created two tickets to add QU30 and CO50 to our docs.
>
> (I think even if we use sec@a.o we should still add something to our docs
> saying how to do it)
>
> https://issues.apache.org/jira/browse/AIRFLOW-3430 -- Fokko: did you get
> anywhere on this?
> https://issues.apache.org/jira/browse/AIRFLOW-3431 -- I'll make a start
> on this
>
> -ash
>
> > On 30 Nov 2018, at 22:06, Bolke de Bruin <bd...@gmail.com> wrote:
> >
> > Thanks Jakob!
> >
> > Verstuurd vanaf mijn iPad
> >
> >> Op 30 nov. 2018 om 22:49 heeft Jakob Homan <jg...@gmail.com> het
> volgende geschreven:
> >>
> >> I've finished the paperwork.  I don't seem to have karma to trigger
> >> the build on Jenkins, so we'll just wait for the daily rebuild.  With
> >> that, I've opened the VOTE thread as well.  Thanks everybody.
> >>> On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan <jg...@gmail.com> wrote:
> >>>
> >>> I'll finish up the template at
> >>> http://incubator.apache.org/projects/airflow.html tomorrow or Friday
> >>> (I *think* you have to be an IPMC member to update it since it lives
> >>> in the Incubator SVN).  Looks like there's no actual work to do, just
> >>> marking stuff that has been done but not yet recorded, and verifying
> >>> some licenses.
> >>>
> >>> -Jakob
> >>>
> >>>
> >>>
> >>>> On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com> wrote:
> >>>>
> >>>> Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I
> could
> >>>> help with?
> >>>>
> >>>> Thanks,
> >>>> -Tao
> >>>>
> >>>>> On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com>
> wrote:
> >>>>>
> >>>>> I would like to help on the documentation. Let me take a look at it.
> I
> >>>>> will work Kaxil on that.
> >>>>>
> >>>>>> On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> Hi Folks,
> >>>>>>
> >>>>>> Thanks all for your responses and particularly Stefan for his
> suggestion
> >>>>>> to use the generic Apache way to handle security issues. This seems
> to be
> >>>>>> an accepted way for more projects, so I have added this to the
> maturity
> >>>>>> evaluation[1] and marked is as resolved. While handling the GPL
> library can
> >>>>>> be nicer we are already in compliance with CD30, so @Fokko and @Ash
> if you
> >>>>>> want to help out towards graduation please spend your time
> elsewhere like
> >>>>>> fixing CO50. This means adding a page to confluence that describes
> how to
> >>>>>> become a committer on the project. As we are following Apache many
> examples
> >>>>>> of other projects are around[2]
> >>>>>>
> >>>>>> Then there is the paperwork[3] as referred to by Jakob. This mainly
> >>>>>> concerns filling in some items, maybe here and there creation some
> >>>>>> documentation but I don't think much. @Kaxil, @Tao: are you willing
> to pick
> >>>>>> this up? @Sid can you share how to edit that page?
> >>>>>>
> >>>>>> If we have resolved these items in my opinion we can start the
> voting
> >>>>>> here and at the IPMC thereafter, targeting the board meeting of
> January for
> >>>>>> graduation. How’s that for a New Year’s resolution?
> >>>>>>
> >>>>>> Cheers!
> >>>>>> Bolke
> >>>>>>
> >>>>>> P.S. Would it be nice to have updated graduation web page? Maybe
> one of
> >>>>>> the contributors/community members likes to take a stab at this[4]
> >>>>>>
> >>>>>> [1]
> >>>>>>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
> >>>>>>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
> >>>>>> [2]
> https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> >>>>>> <
> https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
> >>>>>> [3] http://incubator.apache.org/projects/airflow.html <
> >>>>>> http://incubator.apache.org/projects/airflow.html>
> >>>>>> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> +1 from my side. Would be awesome to graduate Airflow
> >>>>>>>
> >>>>>>> If time allows, I'll also dive into CD30.
> >>>>>>>
> >>>>>>> Cheers, Fokko
> >>>>>>>
> >>>>>>> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <
> ash@apache.org>:
> >>>>>>>
> >>>>>>>> Oarsome Bolke, thanks for starting this.
> >>>>>>>>
> >>>>>>>> It looks like we are closer than I thought!
> >>>>>>>>
> >>>>>>>> We can use those security lists (though having our own would be
> nice) -
> >>>>>>>> either way we will need to make this prominent in the docs.
> >>>>>>>>
> >>>>>>>> Couple of points
> >>>>>>>>
> >>>>>>>> CS10: that github link is only visible to members of the team
> >>>>>>>>
> >>>>>>>> CD30: probably good as it is, we may want to do
> >>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> >>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove
> the last
> >>>>>>>> niggle of the GPL env var at install time (but not a hard
> requirement,
> >>>>>> just
> >>>>>>>> nice)
> >>>>>>>>
> >>>>>>>> -ash
> >>>>>>>>
> >>>>>>>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <
> mail@stefan-seelmann.de>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> I agree that Apache Airflow should graduate.
> >>>>>>>>>
> >>>>>>>>> I'm only involved since beginning of this year, but the project
> did
> >>>>>> two
> >>>>>>>>> releases during that time, once TLP releasing becomes easier :)
> >>>>>>>>>
> >>>>>>>>> Regarding QU30 you may consider to use the ASF wide security
> mailing
> >>>>>>>>> list [3] and process [4].
> >>>>>>>>>
> >>>>>>>>> Kind Regards,
> >>>>>>>>> Stefan
> >>>>>>>>>
> >>>>>>>>> [3] https://www.apache.org/security/
> >>>>>>>>> [4] https://www.apache.org/security/committers.html
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> >>>>>>>>>> Ping!
> >>>>>>>>>>
> >>>>>>>>>> Sent from my iPhone
> >>>>>>>>>>
> >>>>>>>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com>
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Hi All,
> >>>>>>>>>>>
> >>>>>>>>>>> With the Apache Airflow community healthy and growing, I think
> now
> >>>>>>>> would be a good time to
> >>>>>>>>>>> discuss where we stand regarding to graduation from the
> Incubator,
> >>>>>> and
> >>>>>>>> what requirements remains.
> >>>>>>>>>>>
> >>>>>>>>>>> Apache Airflow entered incubation around 2 years ago, since
> then,
> >>>>>> the
> >>>>>>>> Airflow community learned
> >>>>>>>>>>> a lot about how to do things in Apache ways. Now we are a very
> >>>>>> helpful
> >>>>>>>> and engaged community,
> >>>>>>>>>>> ready to help on all questions from the Airflow community. We
> >>>>>>>> delivered multiple releases that have
> >>>>>>>>>>> been increasing in quality ever since, now we can do
> self-driving
> >>>>>>>> releases in good cadence.
> >>>>>>>>>>>
> >>>>>>>>>>> The community is growing, new committers and PPMC members keep
> >>>>>>>> joining. We addressed almost all
> >>>>>>>>>>> the maturity issues stipulated by Apache Project Maturity
> Model [1].
> >>>>>>>> So final requirements remain, but
> >>>>>>>>>>> those just need a final nudge. Committers and contributors are
> >>>>>> invited
> >>>>>>>> to verify the list and pick up the last
> >>>>>>>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP
> issues we
> >>>>>>>> can see got resolved.
> >>>>>>>>>>>
> >>>>>>>>>>> Base on those, I believes it's time for us to graduate to TLP.
> [2]
> >>>>>> Any
> >>>>>>>> thoughts?
> >>>>>>>>>>> And welcome advice from Airflow Mentors?
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>>
> >>>>>>>>>>> [1]
> >>>>>>>>
> >>>>>>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >>>>>>>>>>> [2]
> >>>>>>>>
> >>>>>>
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> >>>>>>>> Regards,
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
>
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Ash Berlin-Taylor <as...@apache.org>.
I've created two tickets to add QU30 and CO50 to our docs.

(I think even if we use sec@a.o we should still add something to our docs saying how to do it)

https://issues.apache.org/jira/browse/AIRFLOW-3430 -- Fokko: did you get anywhere on this?
https://issues.apache.org/jira/browse/AIRFLOW-3431 -- I'll make a start on this

-ash

> On 30 Nov 2018, at 22:06, Bolke de Bruin <bd...@gmail.com> wrote:
> 
> Thanks Jakob!
> 
> Verstuurd vanaf mijn iPad
> 
>> Op 30 nov. 2018 om 22:49 heeft Jakob Homan <jg...@gmail.com> het volgende geschreven:
>> 
>> I've finished the paperwork.  I don't seem to have karma to trigger
>> the build on Jenkins, so we'll just wait for the daily rebuild.  With
>> that, I've opened the VOTE thread as well.  Thanks everybody.
>>> On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan <jg...@gmail.com> wrote:
>>> 
>>> I'll finish up the template at
>>> http://incubator.apache.org/projects/airflow.html tomorrow or Friday
>>> (I *think* you have to be an IPMC member to update it since it lives
>>> in the Incubator SVN).  Looks like there's no actual work to do, just
>>> marking stuff that has been done but not yet recorded, and verifying
>>> some licenses.
>>> 
>>> -Jakob
>>> 
>>> 
>>> 
>>>> On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com> wrote:
>>>> 
>>>> Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I could
>>>> help with?
>>>> 
>>>> Thanks,
>>>> -Tao
>>>> 
>>>>> On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com> wrote:
>>>>> 
>>>>> I would like to help on the documentation. Let me take a look at it. I
>>>>> will work Kaxil on that.
>>>>> 
>>>>>> On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com> wrote:
>>>>>> 
>>>>>> Hi Folks,
>>>>>> 
>>>>>> Thanks all for your responses and particularly Stefan for his suggestion
>>>>>> to use the generic Apache way to handle security issues. This seems to be
>>>>>> an accepted way for more projects, so I have added this to the maturity
>>>>>> evaluation[1] and marked is as resolved. While handling the GPL library can
>>>>>> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
>>>>>> want to help out towards graduation please spend your time elsewhere like
>>>>>> fixing CO50. This means adding a page to confluence that describes how to
>>>>>> become a committer on the project. As we are following Apache many examples
>>>>>> of other projects are around[2]
>>>>>> 
>>>>>> Then there is the paperwork[3] as referred to by Jakob. This mainly
>>>>>> concerns filling in some items, maybe here and there creation some
>>>>>> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
>>>>>> this up? @Sid can you share how to edit that page?
>>>>>> 
>>>>>> If we have resolved these items in my opinion we can start the voting
>>>>>> here and at the IPMC thereafter, targeting the board meeting of January for
>>>>>> graduation. How’s that for a New Year’s resolution?
>>>>>> 
>>>>>> Cheers!
>>>>>> Bolke
>>>>>> 
>>>>>> P.S. Would it be nice to have updated graduation web page? Maybe one of
>>>>>> the contributors/community members likes to take a stab at this[4]
>>>>>> 
>>>>>> [1]
>>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
>>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
>>>>>> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
>>>>>> <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
>>>>>> [3] http://incubator.apache.org/projects/airflow.html <
>>>>>> http://incubator.apache.org/projects/airflow.html>
>>>>>> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
>>>>>> wrote:
>>>>>>> 
>>>>>>> +1 from my side. Would be awesome to graduate Airflow
>>>>>>> 
>>>>>>> If time allows, I'll also dive into CD30.
>>>>>>> 
>>>>>>> Cheers, Fokko
>>>>>>> 
>>>>>>> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
>>>>>>> 
>>>>>>>> Oarsome Bolke, thanks for starting this.
>>>>>>>> 
>>>>>>>> It looks like we are closer than I thought!
>>>>>>>> 
>>>>>>>> We can use those security lists (though having our own would be nice) -
>>>>>>>> either way we will need to make this prominent in the docs.
>>>>>>>> 
>>>>>>>> Couple of points
>>>>>>>> 
>>>>>>>> CS10: that github link is only visible to members of the team
>>>>>>>> 
>>>>>>>> CD30: probably good as it is, we may want to do
>>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
>>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
>>>>>>>> niggle of the GPL env var at install time (but not a hard requirement,
>>>>>> just
>>>>>>>> nice)
>>>>>>>> 
>>>>>>>> -ash
>>>>>>>> 
>>>>>>>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> I agree that Apache Airflow should graduate.
>>>>>>>>> 
>>>>>>>>> I'm only involved since beginning of this year, but the project did
>>>>>> two
>>>>>>>>> releases during that time, once TLP releasing becomes easier :)
>>>>>>>>> 
>>>>>>>>> Regarding QU30 you may consider to use the ASF wide security mailing
>>>>>>>>> list [3] and process [4].
>>>>>>>>> 
>>>>>>>>> Kind Regards,
>>>>>>>>> Stefan
>>>>>>>>> 
>>>>>>>>> [3] https://www.apache.org/security/
>>>>>>>>> [4] https://www.apache.org/security/committers.html
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>>>>>>>>>> Ping!
>>>>>>>>>> 
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>> 
>>>>>>>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi All,
>>>>>>>>>>> 
>>>>>>>>>>> With the Apache Airflow community healthy and growing, I think now
>>>>>>>> would be a good time to
>>>>>>>>>>> discuss where we stand regarding to graduation from the Incubator,
>>>>>> and
>>>>>>>> what requirements remains.
>>>>>>>>>>> 
>>>>>>>>>>> Apache Airflow entered incubation around 2 years ago, since then,
>>>>>> the
>>>>>>>> Airflow community learned
>>>>>>>>>>> a lot about how to do things in Apache ways. Now we are a very
>>>>>> helpful
>>>>>>>> and engaged community,
>>>>>>>>>>> ready to help on all questions from the Airflow community. We
>>>>>>>> delivered multiple releases that have
>>>>>>>>>>> been increasing in quality ever since, now we can do self-driving
>>>>>>>> releases in good cadence.
>>>>>>>>>>> 
>>>>>>>>>>> The community is growing, new committers and PPMC members keep
>>>>>>>> joining. We addressed almost all
>>>>>>>>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
>>>>>>>> So final requirements remain, but
>>>>>>>>>>> those just need a final nudge. Committers and contributors are
>>>>>> invited
>>>>>>>> to verify the list and pick up the last
>>>>>>>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
>>>>>>>> can see got resolved.
>>>>>>>>>>> 
>>>>>>>>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
>>>>>> Any
>>>>>>>> thoughts?
>>>>>>>>>>> And welcome advice from Airflow Mentors?
>>>>>>>>>>> 
>>>>>>>>>>> Thanks,
>>>>>>>>>>> 
>>>>>>>>>>> [1]
>>>>>>>> 
>>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>>>>>>>>>>> [2]
>>>>>>>> 
>>>>>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>>>>>>>> Regards,
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Bolke de Bruin <bd...@gmail.com>.
Thanks Jakob!

Verstuurd vanaf mijn iPad

> Op 30 nov. 2018 om 22:49 heeft Jakob Homan <jg...@gmail.com> het volgende geschreven:
> 
> I've finished the paperwork.  I don't seem to have karma to trigger
> the build on Jenkins, so we'll just wait for the daily rebuild.  With
> that, I've opened the VOTE thread as well.  Thanks everybody.
>> On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan <jg...@gmail.com> wrote:
>> 
>> I'll finish up the template at
>> http://incubator.apache.org/projects/airflow.html tomorrow or Friday
>> (I *think* you have to be an IPMC member to update it since it lives
>> in the Incubator SVN).  Looks like there's no actual work to do, just
>> marking stuff that has been done but not yet recorded, and verifying
>> some licenses.
>> 
>> -Jakob
>> 
>> 
>> 
>>> On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com> wrote:
>>> 
>>> Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I could
>>> help with?
>>> 
>>> Thanks,
>>> -Tao
>>> 
>>>> On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com> wrote:
>>>> 
>>>> I would like to help on the documentation. Let me take a look at it. I
>>>> will work Kaxil on that.
>>>> 
>>>>> On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com> wrote:
>>>>> 
>>>>> Hi Folks,
>>>>> 
>>>>> Thanks all for your responses and particularly Stefan for his suggestion
>>>>> to use the generic Apache way to handle security issues. This seems to be
>>>>> an accepted way for more projects, so I have added this to the maturity
>>>>> evaluation[1] and marked is as resolved. While handling the GPL library can
>>>>> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
>>>>> want to help out towards graduation please spend your time elsewhere like
>>>>> fixing CO50. This means adding a page to confluence that describes how to
>>>>> become a committer on the project. As we are following Apache many examples
>>>>> of other projects are around[2]
>>>>> 
>>>>> Then there is the paperwork[3] as referred to by Jakob. This mainly
>>>>> concerns filling in some items, maybe here and there creation some
>>>>> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
>>>>> this up? @Sid can you share how to edit that page?
>>>>> 
>>>>> If we have resolved these items in my opinion we can start the voting
>>>>> here and at the IPMC thereafter, targeting the board meeting of January for
>>>>> graduation. How’s that for a New Year’s resolution?
>>>>> 
>>>>> Cheers!
>>>>> Bolke
>>>>> 
>>>>> P.S. Would it be nice to have updated graduation web page? Maybe one of
>>>>> the contributors/community members likes to take a stab at this[4]
>>>>> 
>>>>> [1]
>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
>>>>> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
>>>>> <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
>>>>> [3] http://incubator.apache.org/projects/airflow.html <
>>>>> http://incubator.apache.org/projects/airflow.html>
>>>>> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
>>>>> wrote:
>>>>>> 
>>>>>> +1 from my side. Would be awesome to graduate Airflow
>>>>>> 
>>>>>> If time allows, I'll also dive into CD30.
>>>>>> 
>>>>>> Cheers, Fokko
>>>>>> 
>>>>>> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
>>>>>> 
>>>>>>> Oarsome Bolke, thanks for starting this.
>>>>>>> 
>>>>>>> It looks like we are closer than I thought!
>>>>>>> 
>>>>>>> We can use those security lists (though having our own would be nice) -
>>>>>>> either way we will need to make this prominent in the docs.
>>>>>>> 
>>>>>>> Couple of points
>>>>>>> 
>>>>>>> CS10: that github link is only visible to members of the team
>>>>>>> 
>>>>>>> CD30: probably good as it is, we may want to do
>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
>>>>>>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
>>>>>>> niggle of the GPL env var at install time (but not a hard requirement,
>>>>> just
>>>>>>> nice)
>>>>>>> 
>>>>>>> -ash
>>>>>>> 
>>>>>>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> I agree that Apache Airflow should graduate.
>>>>>>>> 
>>>>>>>> I'm only involved since beginning of this year, but the project did
>>>>> two
>>>>>>>> releases during that time, once TLP releasing becomes easier :)
>>>>>>>> 
>>>>>>>> Regarding QU30 you may consider to use the ASF wide security mailing
>>>>>>>> list [3] and process [4].
>>>>>>>> 
>>>>>>>> Kind Regards,
>>>>>>>> Stefan
>>>>>>>> 
>>>>>>>> [3] https://www.apache.org/security/
>>>>>>>> [4] https://www.apache.org/security/committers.html
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>>>>>>>>> Ping!
>>>>>>>>> 
>>>>>>>>> Sent from my iPhone
>>>>>>>>> 
>>>>>>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hi All,
>>>>>>>>>> 
>>>>>>>>>> With the Apache Airflow community healthy and growing, I think now
>>>>>>> would be a good time to
>>>>>>>>>> discuss where we stand regarding to graduation from the Incubator,
>>>>> and
>>>>>>> what requirements remains.
>>>>>>>>>> 
>>>>>>>>>> Apache Airflow entered incubation around 2 years ago, since then,
>>>>> the
>>>>>>> Airflow community learned
>>>>>>>>>> a lot about how to do things in Apache ways. Now we are a very
>>>>> helpful
>>>>>>> and engaged community,
>>>>>>>>>> ready to help on all questions from the Airflow community. We
>>>>>>> delivered multiple releases that have
>>>>>>>>>> been increasing in quality ever since, now we can do self-driving
>>>>>>> releases in good cadence.
>>>>>>>>>> 
>>>>>>>>>> The community is growing, new committers and PPMC members keep
>>>>>>> joining. We addressed almost all
>>>>>>>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
>>>>>>> So final requirements remain, but
>>>>>>>>>> those just need a final nudge. Committers and contributors are
>>>>> invited
>>>>>>> to verify the list and pick up the last
>>>>>>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
>>>>>>> can see got resolved.
>>>>>>>>>> 
>>>>>>>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
>>>>> Any
>>>>>>> thoughts?
>>>>>>>>>> And welcome advice from Airflow Mentors?
>>>>>>>>>> 
>>>>>>>>>> Thanks,
>>>>>>>>>> 
>>>>>>>>>> [1]
>>>>>>> 
>>>>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>>>>>>>>>> [2]
>>>>>>> 
>>>>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>>>>>>> Regards,
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Kaxil Naik <ka...@gmail.com>.
Thanks @Jakob Homan <jg...@apache.org>

I have triggered the build now, the page should be updated in 5 minutes.

Regards,
Kaxil

On Fri, Nov 30, 2018 at 9:58 PM Jakob Homan <jg...@gmail.com> wrote:

> I've finished the paperwork.  I don't seem to have karma to trigger
> the build on Jenkins, so we'll just wait for the daily rebuild.  With
> that, I've opened the VOTE thread as well.  Thanks everybody.
> On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan <jg...@gmail.com> wrote:
> >
> > I'll finish up the template at
> > http://incubator.apache.org/projects/airflow.html tomorrow or Friday
> > (I *think* you have to be an IPMC member to update it since it lives
> > in the Incubator SVN).  Looks like there's no actual work to do, just
> > marking stuff that has been done but not yet recorded, and verifying
> > some licenses.
> >
> > -Jakob
> >
> >
> >
> > On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com> wrote:
> > >
> > > Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I
> could
> > > help with?
> > >
> > > Thanks,
> > > -Tao
> > >
> > > On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com> wrote:
> > >
> > > > I would like to help on the documentation. Let me take a look at it.
> I
> > > > will work Kaxil on that.
> > > >
> > > > On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com>
> wrote:
> > > >
> > > >> Hi Folks,
> > > >>
> > > >> Thanks all for your responses and particularly Stefan for his
> suggestion
> > > >> to use the generic Apache way to handle security issues. This seems
> to be
> > > >> an accepted way for more projects, so I have added this to the
> maturity
> > > >> evaluation[1] and marked is as resolved. While handling the GPL
> library can
> > > >> be nicer we are already in compliance with CD30, so @Fokko and @Ash
> if you
> > > >> want to help out towards graduation please spend your time
> elsewhere like
> > > >> fixing CO50. This means adding a page to confluence that describes
> how to
> > > >> become a committer on the project. As we are following Apache many
> examples
> > > >> of other projects are around[2]
> > > >>
> > > >> Then there is the paperwork[3] as referred to by Jakob. This mainly
> > > >> concerns filling in some items, maybe here and there creation some
> > > >> documentation but I don't think much. @Kaxil, @Tao: are you willing
> to pick
> > > >> this up? @Sid can you share how to edit that page?
> > > >>
> > > >> If we have resolved these items in my opinion we can start the
> voting
> > > >> here and at the IPMC thereafter, targeting the board meeting of
> January for
> > > >> graduation. How’s that for a New Year’s resolution?
> > > >>
> > > >> Cheers!
> > > >> Bolke
> > > >>
> > > >> P.S. Would it be nice to have updated graduation web page? Maybe
> one of
> > > >> the contributors/community members likes to take a stab at this[4]
> > > >>
> > > >> [1]
> > > >>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
> > > >>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
> > > >> [2]
> https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> > > >> <
> https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
> > > >> [3] http://incubator.apache.org/projects/airflow.html <
> > > >> http://incubator.apache.org/projects/airflow.html>
> > > >> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
> > > >>
> > > >>
> > > >>
> > > >> > On 27 Nov 2018, at 16:32, Driesprong, Fokko <fokko@driesprong.frl
> >
> > > >> wrote:
> > > >> >
> > > >> > +1 from my side. Would be awesome to graduate Airflow
> > > >> >
> > > >> > If time allows, I'll also dive into CD30.
> > > >> >
> > > >> > Cheers, Fokko
> > > >> >
> > > >> > Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <
> ash@apache.org>:
> > > >> >
> > > >> >> Oarsome Bolke, thanks for starting this.
> > > >> >>
> > > >> >> It looks like we are closer than I thought!
> > > >> >>
> > > >> >> We can use those security lists (though having our own would be
> nice) -
> > > >> >> either way we will need to make this prominent in the docs.
> > > >> >>
> > > >> >> Couple of points
> > > >> >>
> > > >> >> CS10: that github link is only visible to members of the team
> > > >> >>
> > > >> >> CD30: probably good as it is, we may want to do
> > > >> >> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> > > >> >> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove
> the last
> > > >> >> niggle of the GPL env var at install time (but not a hard
> requirement,
> > > >> just
> > > >> >> nice)
> > > >> >>
> > > >> >> -ash
> > > >> >>
> > > >> >>> On 26 Nov 2018, at 21:10, Stefan Seelmann <
> mail@stefan-seelmann.de>
> > > >> >> wrote:
> > > >> >>>
> > > >> >>> I agree that Apache Airflow should graduate.
> > > >> >>>
> > > >> >>> I'm only involved since beginning of this year, but the project
> did
> > > >> two
> > > >> >>> releases during that time, once TLP releasing becomes easier :)
> > > >> >>>
> > > >> >>> Regarding QU30 you may consider to use the ASF wide security
> mailing
> > > >> >>> list [3] and process [4].
> > > >> >>>
> > > >> >>> Kind Regards,
> > > >> >>> Stefan
> > > >> >>>
> > > >> >>> [3] https://www.apache.org/security/
> > > >> >>> [4] https://www.apache.org/security/committers.html
> > > >> >>>
> > > >> >>>
> > > >> >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> > > >> >>>> Ping!
> > > >> >>>>
> > > >> >>>> Sent from my iPhone
> > > >> >>>>
> > > >> >>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com>
> wrote:
> > > >> >>>>>
> > > >> >>>>> Hi All,
> > > >> >>>>>
> > > >> >>>>> With the Apache Airflow community healthy and growing, I
> think now
> > > >> >> would be a good time to
> > > >> >>>>> discuss where we stand regarding to graduation from the
> Incubator,
> > > >> and
> > > >> >> what requirements remains.
> > > >> >>>>>
> > > >> >>>>> Apache Airflow entered incubation around 2 years ago, since
> then,
> > > >> the
> > > >> >> Airflow community learned
> > > >> >>>>> a lot about how to do things in Apache ways. Now we are a very
> > > >> helpful
> > > >> >> and engaged community,
> > > >> >>>>> ready to help on all questions from the Airflow community. We
> > > >> >> delivered multiple releases that have
> > > >> >>>>> been increasing in quality ever since, now we can do
> self-driving
> > > >> >> releases in good cadence.
> > > >> >>>>>
> > > >> >>>>> The community is growing, new committers and PPMC members keep
> > > >> >> joining. We addressed almost all
> > > >> >>>>> the maturity issues stipulated by Apache Project Maturity
> Model [1].
> > > >> >> So final requirements remain, but
> > > >> >>>>> those just need a final nudge. Committers and contributors are
> > > >> invited
> > > >> >> to verify the list and pick up the last
> > > >> >>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP
> issues we
> > > >> >> can see got resolved.
> > > >> >>>>>
> > > >> >>>>> Base on those, I believes it's time for us to graduate to
> TLP. [2]
> > > >> Any
> > > >> >> thoughts?
> > > >> >>>>> And welcome advice from Airflow Mentors?
> > > >> >>>>>
> > > >> >>>>> Thanks,
> > > >> >>>>>
> > > >> >>>>> [1]
> > > >> >>
> > > >>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > > >> >>>>> [2]
> > > >> >>
> > > >>
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> > > >> >> Regards,
> > > >> >>>
> > > >> >>
> > > >> >>
> > > >>
> > > >>
>


-- 
*Kaxil Naik*
*Big Data Consultant *@ *Data Reply UK*
*Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j
Developer
*Phone: *+44 (0) 74820 88992
*LinkedIn*: https://www.linkedin.com/in/kaxil

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Jakob Homan <jg...@gmail.com>.
I've finished the paperwork.  I don't seem to have karma to trigger
the build on Jenkins, so we'll just wait for the daily rebuild.  With
that, I've opened the VOTE thread as well.  Thanks everybody.
On Wed, Nov 28, 2018 at 5:08 PM Jakob Homan <jg...@gmail.com> wrote:
>
> I'll finish up the template at
> http://incubator.apache.org/projects/airflow.html tomorrow or Friday
> (I *think* you have to be an IPMC member to update it since it lives
> in the Incubator SVN).  Looks like there's no actual work to do, just
> marking stuff that has been done but not yet recorded, and verifying
> some licenses.
>
> -Jakob
>
>
>
> On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com> wrote:
> >
> > Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I could
> > help with?
> >
> > Thanks,
> > -Tao
> >
> > On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com> wrote:
> >
> > > I would like to help on the documentation. Let me take a look at it. I
> > > will work Kaxil on that.
> > >
> > > On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com> wrote:
> > >
> > >> Hi Folks,
> > >>
> > >> Thanks all for your responses and particularly Stefan for his suggestion
> > >> to use the generic Apache way to handle security issues. This seems to be
> > >> an accepted way for more projects, so I have added this to the maturity
> > >> evaluation[1] and marked is as resolved. While handling the GPL library can
> > >> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
> > >> want to help out towards graduation please spend your time elsewhere like
> > >> fixing CO50. This means adding a page to confluence that describes how to
> > >> become a committer on the project. As we are following Apache many examples
> > >> of other projects are around[2]
> > >>
> > >> Then there is the paperwork[3] as referred to by Jakob. This mainly
> > >> concerns filling in some items, maybe here and there creation some
> > >> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
> > >> this up? @Sid can you share how to edit that page?
> > >>
> > >> If we have resolved these items in my opinion we can start the voting
> > >> here and at the IPMC thereafter, targeting the board meeting of January for
> > >> graduation. How’s that for a New Year’s resolution?
> > >>
> > >> Cheers!
> > >> Bolke
> > >>
> > >> P.S. Would it be nice to have updated graduation web page? Maybe one of
> > >> the contributors/community members likes to take a stab at this[4]
> > >>
> > >> [1]
> > >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
> > >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
> > >> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> > >> <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
> > >> [3] http://incubator.apache.org/projects/airflow.html <
> > >> http://incubator.apache.org/projects/airflow.html>
> > >> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
> > >>
> > >>
> > >>
> > >> > On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
> > >> wrote:
> > >> >
> > >> > +1 from my side. Would be awesome to graduate Airflow
> > >> >
> > >> > If time allows, I'll also dive into CD30.
> > >> >
> > >> > Cheers, Fokko
> > >> >
> > >> > Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
> > >> >
> > >> >> Oarsome Bolke, thanks for starting this.
> > >> >>
> > >> >> It looks like we are closer than I thought!
> > >> >>
> > >> >> We can use those security lists (though having our own would be nice) -
> > >> >> either way we will need to make this prominent in the docs.
> > >> >>
> > >> >> Couple of points
> > >> >>
> > >> >> CS10: that github link is only visible to members of the team
> > >> >>
> > >> >> CD30: probably good as it is, we may want to do
> > >> >> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> > >> >> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
> > >> >> niggle of the GPL env var at install time (but not a hard requirement,
> > >> just
> > >> >> nice)
> > >> >>
> > >> >> -ash
> > >> >>
> > >> >>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
> > >> >> wrote:
> > >> >>>
> > >> >>> I agree that Apache Airflow should graduate.
> > >> >>>
> > >> >>> I'm only involved since beginning of this year, but the project did
> > >> two
> > >> >>> releases during that time, once TLP releasing becomes easier :)
> > >> >>>
> > >> >>> Regarding QU30 you may consider to use the ASF wide security mailing
> > >> >>> list [3] and process [4].
> > >> >>>
> > >> >>> Kind Regards,
> > >> >>> Stefan
> > >> >>>
> > >> >>> [3] https://www.apache.org/security/
> > >> >>> [4] https://www.apache.org/security/committers.html
> > >> >>>
> > >> >>>
> > >> >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> > >> >>>> Ping!
> > >> >>>>
> > >> >>>> Sent from my iPhone
> > >> >>>>
> > >> >>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> > >> >>>>>
> > >> >>>>> Hi All,
> > >> >>>>>
> > >> >>>>> With the Apache Airflow community healthy and growing, I think now
> > >> >> would be a good time to
> > >> >>>>> discuss where we stand regarding to graduation from the Incubator,
> > >> and
> > >> >> what requirements remains.
> > >> >>>>>
> > >> >>>>> Apache Airflow entered incubation around 2 years ago, since then,
> > >> the
> > >> >> Airflow community learned
> > >> >>>>> a lot about how to do things in Apache ways. Now we are a very
> > >> helpful
> > >> >> and engaged community,
> > >> >>>>> ready to help on all questions from the Airflow community. We
> > >> >> delivered multiple releases that have
> > >> >>>>> been increasing in quality ever since, now we can do self-driving
> > >> >> releases in good cadence.
> > >> >>>>>
> > >> >>>>> The community is growing, new committers and PPMC members keep
> > >> >> joining. We addressed almost all
> > >> >>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
> > >> >> So final requirements remain, but
> > >> >>>>> those just need a final nudge. Committers and contributors are
> > >> invited
> > >> >> to verify the list and pick up the last
> > >> >>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> > >> >> can see got resolved.
> > >> >>>>>
> > >> >>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> > >> Any
> > >> >> thoughts?
> > >> >>>>> And welcome advice from Airflow Mentors?
> > >> >>>>>
> > >> >>>>> Thanks,
> > >> >>>>>
> > >> >>>>> [1]
> > >> >>
> > >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> > >> >>>>> [2]
> > >> >>
> > >> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> > >> >> Regards,
> > >> >>>
> > >> >>
> > >> >>
> > >>
> > >>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Jakob Homan <jg...@gmail.com>.
I'll finish up the template at
http://incubator.apache.org/projects/airflow.html tomorrow or Friday
(I *think* you have to be an IPMC member to update it since it lives
in the Incubator SVN).  Looks like there's no actual work to do, just
marking stuff that has been done but not yet recorded, and verifying
some licenses.

-Jakob



On Wed, Nov 28, 2018 at 2:48 PM Tao Feng <fe...@gmail.com> wrote:
>
> Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I could
> help with?
>
> Thanks,
> -Tao
>
> On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com> wrote:
>
> > I would like to help on the documentation. Let me take a look at it. I
> > will work Kaxil on that.
> >
> > On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com> wrote:
> >
> >> Hi Folks,
> >>
> >> Thanks all for your responses and particularly Stefan for his suggestion
> >> to use the generic Apache way to handle security issues. This seems to be
> >> an accepted way for more projects, so I have added this to the maturity
> >> evaluation[1] and marked is as resolved. While handling the GPL library can
> >> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
> >> want to help out towards graduation please spend your time elsewhere like
> >> fixing CO50. This means adding a page to confluence that describes how to
> >> become a committer on the project. As we are following Apache many examples
> >> of other projects are around[2]
> >>
> >> Then there is the paperwork[3] as referred to by Jakob. This mainly
> >> concerns filling in some items, maybe here and there creation some
> >> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
> >> this up? @Sid can you share how to edit that page?
> >>
> >> If we have resolved these items in my opinion we can start the voting
> >> here and at the IPMC thereafter, targeting the board meeting of January for
> >> graduation. How’s that for a New Year’s resolution?
> >>
> >> Cheers!
> >> Bolke
> >>
> >> P.S. Would it be nice to have updated graduation web page? Maybe one of
> >> the contributors/community members likes to take a stab at this[4]
> >>
> >> [1]
> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
> >> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> >> <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
> >> [3] http://incubator.apache.org/projects/airflow.html <
> >> http://incubator.apache.org/projects/airflow.html>
> >> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
> >>
> >>
> >>
> >> > On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
> >> wrote:
> >> >
> >> > +1 from my side. Would be awesome to graduate Airflow
> >> >
> >> > If time allows, I'll also dive into CD30.
> >> >
> >> > Cheers, Fokko
> >> >
> >> > Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
> >> >
> >> >> Oarsome Bolke, thanks for starting this.
> >> >>
> >> >> It looks like we are closer than I thought!
> >> >>
> >> >> We can use those security lists (though having our own would be nice) -
> >> >> either way we will need to make this prominent in the docs.
> >> >>
> >> >> Couple of points
> >> >>
> >> >> CS10: that github link is only visible to members of the team
> >> >>
> >> >> CD30: probably good as it is, we may want to do
> >> >> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> >> >> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
> >> >> niggle of the GPL env var at install time (but not a hard requirement,
> >> just
> >> >> nice)
> >> >>
> >> >> -ash
> >> >>
> >> >>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
> >> >> wrote:
> >> >>>
> >> >>> I agree that Apache Airflow should graduate.
> >> >>>
> >> >>> I'm only involved since beginning of this year, but the project did
> >> two
> >> >>> releases during that time, once TLP releasing becomes easier :)
> >> >>>
> >> >>> Regarding QU30 you may consider to use the ASF wide security mailing
> >> >>> list [3] and process [4].
> >> >>>
> >> >>> Kind Regards,
> >> >>> Stefan
> >> >>>
> >> >>> [3] https://www.apache.org/security/
> >> >>> [4] https://www.apache.org/security/committers.html
> >> >>>
> >> >>>
> >> >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> >> >>>> Ping!
> >> >>>>
> >> >>>> Sent from my iPhone
> >> >>>>
> >> >>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >> >>>>>
> >> >>>>> Hi All,
> >> >>>>>
> >> >>>>> With the Apache Airflow community healthy and growing, I think now
> >> >> would be a good time to
> >> >>>>> discuss where we stand regarding to graduation from the Incubator,
> >> and
> >> >> what requirements remains.
> >> >>>>>
> >> >>>>> Apache Airflow entered incubation around 2 years ago, since then,
> >> the
> >> >> Airflow community learned
> >> >>>>> a lot about how to do things in Apache ways. Now we are a very
> >> helpful
> >> >> and engaged community,
> >> >>>>> ready to help on all questions from the Airflow community. We
> >> >> delivered multiple releases that have
> >> >>>>> been increasing in quality ever since, now we can do self-driving
> >> >> releases in good cadence.
> >> >>>>>
> >> >>>>> The community is growing, new committers and PPMC members keep
> >> >> joining. We addressed almost all
> >> >>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
> >> >> So final requirements remain, but
> >> >>>>> those just need a final nudge. Committers and contributors are
> >> invited
> >> >> to verify the list and pick up the last
> >> >>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> >> >> can see got resolved.
> >> >>>>>
> >> >>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> >> Any
> >> >> thoughts?
> >> >>>>> And welcome advice from Airflow Mentors?
> >> >>>>>
> >> >>>>> Thanks,
> >> >>>>>
> >> >>>>> [1]
> >> >>
> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >> >>>>> [2]
> >> >>
> >> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> >> >> Regards,
> >> >>>
> >> >>
> >> >>
> >>
> >>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Tao Feng <fe...@gmail.com>.
Sorry, just saw Kaxil's latest email. Kaxil, is there anything else I could
help with?

Thanks,
-Tao

On Wed, Nov 28, 2018 at 2:40 PM Tao Feng <fe...@gmail.com> wrote:

> I would like to help on the documentation. Let me take a look at it. I
> will work Kaxil on that.
>
> On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com> wrote:
>
>> Hi Folks,
>>
>> Thanks all for your responses and particularly Stefan for his suggestion
>> to use the generic Apache way to handle security issues. This seems to be
>> an accepted way for more projects, so I have added this to the maturity
>> evaluation[1] and marked is as resolved. While handling the GPL library can
>> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
>> want to help out towards graduation please spend your time elsewhere like
>> fixing CO50. This means adding a page to confluence that describes how to
>> become a committer on the project. As we are following Apache many examples
>> of other projects are around[2]
>>
>> Then there is the paperwork[3] as referred to by Jakob. This mainly
>> concerns filling in some items, maybe here and there creation some
>> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
>> this up? @Sid can you share how to edit that page?
>>
>> If we have resolved these items in my opinion we can start the voting
>> here and at the IPMC thereafter, targeting the board meeting of January for
>> graduation. How’s that for a New Year’s resolution?
>>
>> Cheers!
>> Bolke
>>
>> P.S. Would it be nice to have updated graduation web page? Maybe one of
>> the contributors/community members likes to take a stab at this[4]
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
>> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
>> <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
>> [3] http://incubator.apache.org/projects/airflow.html <
>> http://incubator.apache.org/projects/airflow.html>
>> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
>>
>>
>>
>> > On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
>> wrote:
>> >
>> > +1 from my side. Would be awesome to graduate Airflow
>> >
>> > If time allows, I'll also dive into CD30.
>> >
>> > Cheers, Fokko
>> >
>> > Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
>> >
>> >> Oarsome Bolke, thanks for starting this.
>> >>
>> >> It looks like we are closer than I thought!
>> >>
>> >> We can use those security lists (though having our own would be nice) -
>> >> either way we will need to make this prominent in the docs.
>> >>
>> >> Couple of points
>> >>
>> >> CS10: that github link is only visible to members of the team
>> >>
>> >> CD30: probably good as it is, we may want to do
>> >> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
>> >> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
>> >> niggle of the GPL env var at install time (but not a hard requirement,
>> just
>> >> nice)
>> >>
>> >> -ash
>> >>
>> >>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
>> >> wrote:
>> >>>
>> >>> I agree that Apache Airflow should graduate.
>> >>>
>> >>> I'm only involved since beginning of this year, but the project did
>> two
>> >>> releases during that time, once TLP releasing becomes easier :)
>> >>>
>> >>> Regarding QU30 you may consider to use the ASF wide security mailing
>> >>> list [3] and process [4].
>> >>>
>> >>> Kind Regards,
>> >>> Stefan
>> >>>
>> >>> [3] https://www.apache.org/security/
>> >>> [4] https://www.apache.org/security/committers.html
>> >>>
>> >>>
>> >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>> >>>> Ping!
>> >>>>
>> >>>> Sent from my iPhone
>> >>>>
>> >>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>> >>>>>
>> >>>>> Hi All,
>> >>>>>
>> >>>>> With the Apache Airflow community healthy and growing, I think now
>> >> would be a good time to
>> >>>>> discuss where we stand regarding to graduation from the Incubator,
>> and
>> >> what requirements remains.
>> >>>>>
>> >>>>> Apache Airflow entered incubation around 2 years ago, since then,
>> the
>> >> Airflow community learned
>> >>>>> a lot about how to do things in Apache ways. Now we are a very
>> helpful
>> >> and engaged community,
>> >>>>> ready to help on all questions from the Airflow community. We
>> >> delivered multiple releases that have
>> >>>>> been increasing in quality ever since, now we can do self-driving
>> >> releases in good cadence.
>> >>>>>
>> >>>>> The community is growing, new committers and PPMC members keep
>> >> joining. We addressed almost all
>> >>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
>> >> So final requirements remain, but
>> >>>>> those just need a final nudge. Committers and contributors are
>> invited
>> >> to verify the list and pick up the last
>> >>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
>> >> can see got resolved.
>> >>>>>
>> >>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
>> Any
>> >> thoughts?
>> >>>>> And welcome advice from Airflow Mentors?
>> >>>>>
>> >>>>> Thanks,
>> >>>>>
>> >>>>> [1]
>> >>
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>> >>>>> [2]
>> >>
>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>> >> Regards,
>> >>>
>> >>
>> >>
>>
>>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Tao Feng <fe...@gmail.com>.
I would like to help on the documentation. Let me take a look at it. I will
work Kaxil on that.

On Tue, Nov 27, 2018 at 12:39 PM Bolke de Bruin <bd...@gmail.com> wrote:

> Hi Folks,
>
> Thanks all for your responses and particularly Stefan for his suggestion
> to use the generic Apache way to handle security issues. This seems to be
> an accepted way for more projects, so I have added this to the maturity
> evaluation[1] and marked is as resolved. While handling the GPL library can
> be nicer we are already in compliance with CD30, so @Fokko and @Ash if you
> want to help out towards graduation please spend your time elsewhere like
> fixing CO50. This means adding a page to confluence that describes how to
> become a committer on the project. As we are following Apache many examples
> of other projects are around[2]
>
> Then there is the paperwork[3] as referred to by Jakob. This mainly
> concerns filling in some items, maybe here and there creation some
> documentation but I don't think much. @Kaxil, @Tao: are you willing to pick
> this up? @Sid can you share how to edit that page?
>
> If we have resolved these items in my opinion we can start the voting here
> and at the IPMC thereafter, targeting the board meeting of January for
> graduation. How’s that for a New Year’s resolution?
>
> Cheers!
> Bolke
>
> P.S. Would it be nice to have updated graduation web page? Maybe one of
> the contributors/community members likes to take a stab at this[4]
>
> [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
> [2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer
> <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
> [3] http://incubator.apache.org/projects/airflow.html <
> http://incubator.apache.org/projects/airflow.html>
> [4] https://airflow.apache.org/ <https://airflow.apache.org/>
>
>
>
> > On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl>
> wrote:
> >
> > +1 from my side. Would be awesome to graduate Airflow
> >
> > If time allows, I'll also dive into CD30.
> >
> > Cheers, Fokko
> >
> > Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
> >
> >> Oarsome Bolke, thanks for starting this.
> >>
> >> It looks like we are closer than I thought!
> >>
> >> We can use those security lists (though having our own would be nice) -
> >> either way we will need to make this prominent in the docs.
> >>
> >> Couple of points
> >>
> >> CS10: that github link is only visible to members of the team
> >>
> >> CD30: probably good as it is, we may want to do
> >> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> >> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
> >> niggle of the GPL env var at install time (but not a hard requirement,
> just
> >> nice)
> >>
> >> -ash
> >>
> >>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
> >> wrote:
> >>>
> >>> I agree that Apache Airflow should graduate.
> >>>
> >>> I'm only involved since beginning of this year, but the project did two
> >>> releases during that time, once TLP releasing becomes easier :)
> >>>
> >>> Regarding QU30 you may consider to use the ASF wide security mailing
> >>> list [3] and process [4].
> >>>
> >>> Kind Regards,
> >>> Stefan
> >>>
> >>> [3] https://www.apache.org/security/
> >>> [4] https://www.apache.org/security/committers.html
> >>>
> >>>
> >>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> >>>> Ping!
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >>>>>
> >>>>> Hi All,
> >>>>>
> >>>>> With the Apache Airflow community healthy and growing, I think now
> >> would be a good time to
> >>>>> discuss where we stand regarding to graduation from the Incubator,
> and
> >> what requirements remains.
> >>>>>
> >>>>> Apache Airflow entered incubation around 2 years ago, since then, the
> >> Airflow community learned
> >>>>> a lot about how to do things in Apache ways. Now we are a very
> helpful
> >> and engaged community,
> >>>>> ready to help on all questions from the Airflow community. We
> >> delivered multiple releases that have
> >>>>> been increasing in quality ever since, now we can do self-driving
> >> releases in good cadence.
> >>>>>
> >>>>> The community is growing, new committers and PPMC members keep
> >> joining. We addressed almost all
> >>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
> >> So final requirements remain, but
> >>>>> those just need a final nudge. Committers and contributors are
> invited
> >> to verify the list and pick up the last
> >>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> >> can see got resolved.
> >>>>>
> >>>>> Base on those, I believes it's time for us to graduate to TLP. [2]
> Any
> >> thoughts?
> >>>>> And welcome advice from Airflow Mentors?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> [1]
> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >>>>> [2]
> >>
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> >> Regards,
> >>>
> >>
> >>
>
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Bolke de Bruin <bd...@gmail.com>.
Hi Folks,

Thanks all for your responses and particularly Stefan for his suggestion to use the generic Apache way to handle security issues. This seems to be an accepted way for more projects, so I have added this to the maturity evaluation[1] and marked is as resolved. While handling the GPL library can be nicer we are already in compliance with CD30, so @Fokko and @Ash if you want to help out towards graduation please spend your time elsewhere like fixing CO50. This means adding a page to confluence that describes how to become a committer on the project. As we are following Apache many examples of other projects are around[2]

Then there is the paperwork[3] as referred to by Jakob. This mainly concerns filling in some items, maybe here and there creation some documentation but I don't think much. @Kaxil, @Tao: are you willing to pick this up? @Sid can you share how to edit that page? 

If we have resolved these items in my opinion we can start the voting here and at the IPMC thereafter, targeting the board meeting of January for graduation. How’s that for a New Year’s resolution?

Cheers!
Bolke

P.S. Would it be nice to have updated graduation web page? Maybe one of the contributors/community members likes to take a stab at this[4]

[1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation <https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation>
[2] https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer <https://cwiki.apache.org/confluence/display/HAWQ/Becoming+a+committer>
[3] http://incubator.apache.org/projects/airflow.html <http://incubator.apache.org/projects/airflow.html>
[4] https://airflow.apache.org/ <https://airflow.apache.org/>



> On 27 Nov 2018, at 16:32, Driesprong, Fokko <fo...@driesprong.frl> wrote:
> 
> +1 from my side. Would be awesome to graduate Airflow
> 
> If time allows, I'll also dive into CD30.
> 
> Cheers, Fokko
> 
> Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:
> 
>> Oarsome Bolke, thanks for starting this.
>> 
>> It looks like we are closer than I thought!
>> 
>> We can use those security lists (though having our own would be nice) -
>> either way we will need to make this prominent in the docs.
>> 
>> Couple of points
>> 
>> CS10: that github link is only visible to members of the team
>> 
>> CD30: probably good as it is, we may want to do
>> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
>> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
>> niggle of the GPL env var at install time (but not a hard requirement, just
>> nice)
>> 
>> -ash
>> 
>>> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
>> wrote:
>>> 
>>> I agree that Apache Airflow should graduate.
>>> 
>>> I'm only involved since beginning of this year, but the project did two
>>> releases during that time, once TLP releasing becomes easier :)
>>> 
>>> Regarding QU30 you may consider to use the ASF wide security mailing
>>> list [3] and process [4].
>>> 
>>> Kind Regards,
>>> Stefan
>>> 
>>> [3] https://www.apache.org/security/
>>> [4] https://www.apache.org/security/committers.html
>>> 
>>> 
>>> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>>>> Ping!
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>>>> 
>>>>> Hi All,
>>>>> 
>>>>> With the Apache Airflow community healthy and growing, I think now
>> would be a good time to
>>>>> discuss where we stand regarding to graduation from the Incubator, and
>> what requirements remains.
>>>>> 
>>>>> Apache Airflow entered incubation around 2 years ago, since then, the
>> Airflow community learned
>>>>> a lot about how to do things in Apache ways. Now we are a very helpful
>> and engaged community,
>>>>> ready to help on all questions from the Airflow community. We
>> delivered multiple releases that have
>>>>> been increasing in quality ever since, now we can do self-driving
>> releases in good cadence.
>>>>> 
>>>>> The community is growing, new committers and PPMC members keep
>> joining. We addressed almost all
>>>>> the maturity issues stipulated by Apache Project Maturity Model [1].
>> So final requirements remain, but
>>>>> those just need a final nudge. Committers and contributors are invited
>> to verify the list and pick up the last
>>>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
>> can see got resolved.
>>>>> 
>>>>> Base on those, I believes it's time for us to graduate to TLP. [2] Any
>> thoughts?
>>>>> And welcome advice from Airflow Mentors?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> [1]
>> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>>>>> [2]
>> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
>> Regards,
>>> 
>> 
>>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
+1 from my side. Would be awesome to graduate Airflow

If time allows, I'll also dive into CD30.

Cheers, Fokko

Op di 27 nov. 2018 om 16:21 schreef Ash Berlin-Taylor <as...@apache.org>:

> Oarsome Bolke, thanks for starting this.
>
> It looks like we are closer than I thought!
>
> We can use those security lists (though having our own would be nice) -
> either way we will need to make this prominent in the docs.
>
> Couple of points
>
> CS10: that github link is only visible to members of the team
>
> CD30: probably good as it is, we may want to do
> https://issues.apache.org/jira/browse/AIRFLOW-3400 <
> https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last
> niggle of the GPL env var at install time (but not a hard requirement, just
> nice)
>
> -ash
>
> > On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de>
> wrote:
> >
> > I agree that Apache Airflow should graduate.
> >
> > I'm only involved since beginning of this year, but the project did two
> > releases during that time, once TLP releasing becomes easier :)
> >
> > Regarding QU30 you may consider to use the ASF wide security mailing
> > list [3] and process [4].
> >
> > Kind Regards,
> > Stefan
> >
> > [3] https://www.apache.org/security/
> > [4] https://www.apache.org/security/committers.html
> >
> >
> > On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> >> Ping!
> >>
> >> Sent from my iPhone
> >>
> >>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> With the Apache Airflow community healthy and growing, I think now
> would be a good time to
> >>> discuss where we stand regarding to graduation from the Incubator, and
> what requirements remains.
> >>>
> >>> Apache Airflow entered incubation around 2 years ago, since then, the
> Airflow community learned
> >>> a lot about how to do things in Apache ways. Now we are a very helpful
> and engaged community,
> >>> ready to help on all questions from the Airflow community. We
> delivered multiple releases that have
> >>> been increasing in quality ever since, now we can do self-driving
> releases in good cadence.
> >>>
> >>> The community is growing, new committers and PPMC members keep
> joining. We addressed almost all
> >>> the maturity issues stipulated by Apache Project Maturity Model [1].
> So final requirements remain, but
> >>> those just need a final nudge. Committers and contributors are invited
> to verify the list and pick up the last
> >>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we
> can see got resolved.
> >>>
> >>> Base on those, I believes it's time for us to graduate to TLP. [2] Any
> thoughts?
> >>> And welcome advice from Airflow Mentors?
> >>>
> >>> Thanks,
> >>>
> >>> [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >>> [2]
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> Regards,
> >
>
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Ash Berlin-Taylor <as...@apache.org>.
Oarsome Bolke, thanks for starting this.

It looks like we are closer than I thought!

We can use those security lists (though having our own would be nice) - either way we will need to make this prominent in the docs.

Couple of points

CS10: that github link is only visible to members of the team

CD30: probably good as it is, we may want to do https://issues.apache.org/jira/browse/AIRFLOW-3400 <https://issues.apache.org/jira/browse/AIRFLOW-3400> to remove the last niggle of the GPL env var at install time (but not a hard requirement, just nice)

-ash

> On 26 Nov 2018, at 21:10, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
> 
> I agree that Apache Airflow should graduate.
> 
> I'm only involved since beginning of this year, but the project did two
> releases during that time, once TLP releasing becomes easier :)
> 
> Regarding QU30 you may consider to use the ASF wide security mailing
> list [3] and process [4].
> 
> Kind Regards,
> Stefan
> 
> [3] https://www.apache.org/security/
> [4] https://www.apache.org/security/committers.html
> 
> 
> On 11/26/18 8:46 PM, Bolke de Bruin wrote:
>> Ping!
>> 
>> Sent from my iPhone
>> 
>>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>> 
>>> Hi All,
>>> 
>>> With the Apache Airflow community healthy and growing, I think now would be a good time to 
>>> discuss where we stand regarding to graduation from the Incubator, and what requirements remains. 
>>> 
>>> Apache Airflow entered incubation around 2 years ago, since then, the Airflow community learned 
>>> a lot about how to do things in Apache ways. Now we are a very helpful and engaged community, 
>>> ready to help on all questions from the Airflow community. We delivered multiple releases that have 
>>> been increasing in quality ever since, now we can do self-driving releases in good cadence. 
>>> 
>>> The community is growing, new committers and PPMC members keep joining. We addressed almost all 
>>> the maturity issues stipulated by Apache Project Maturity Model [1]. So final requirements remain, but
>>> those just need a final nudge. Committers and contributors are invited to verify the list and pick up the last 
>>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can see got resolved. 
>>> 
>>> Base on those, I believes it's time for us to graduate to TLP. [2] Any thoughts? 
>>> And welcome advice from Airflow Mentors? 
>>> 
>>> Thanks, 
>>> 
>>> [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>>> [2] https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project Regards,
>

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
I agree that Apache Airflow should graduate.

I'm only involved since beginning of this year, but the project did two
releases during that time, once TLP releasing becomes easier :)

Regarding QU30 you may consider to use the ASF wide security mailing
list [3] and process [4].

Kind Regards,
Stefan

[3] https://www.apache.org/security/
[4] https://www.apache.org/security/committers.html


On 11/26/18 8:46 PM, Bolke de Bruin wrote:
> Ping!
> 
> Sent from my iPhone
> 
>> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
>>
>> Hi All,
>>
>> With the Apache Airflow community healthy and growing, I think now would be a good time to 
>> discuss where we stand regarding to graduation from the Incubator, and what requirements remains. 
>>
>> Apache Airflow entered incubation around 2 years ago, since then, the Airflow community learned 
>> a lot about how to do things in Apache ways. Now we are a very helpful and engaged community, 
>> ready to help on all questions from the Airflow community. We delivered multiple releases that have 
>> been increasing in quality ever since, now we can do self-driving releases in good cadence. 
>>
>> The community is growing, new committers and PPMC members keep joining. We addressed almost all 
>> the maturity issues stipulated by Apache Project Maturity Model [1]. So final requirements remain, but
>> those just need a final nudge. Committers and contributors are invited to verify the list and pick up the last 
>> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can see got resolved. 
>>
>> Base on those, I believes it's time for us to graduate to TLP. [2] Any thoughts? 
>> And welcome advice from Airflow Mentors? 
>>
>> Thanks, 
>>
>> [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
>> [2] https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project Regards,

Re: [DISCUSS] Apache Airflow graduation from the incubator

Posted by Bolke de Bruin <bd...@gmail.com>.
Ping!

Sent from my iPhone

> On 24 Nov 2018, at 12:57, Bolke de Bruin <bd...@gmail.com> wrote:
> 
> Hi All,
> 
> With the Apache Airflow community healthy and growing, I think now would be a good time to 
> discuss where we stand regarding to graduation from the Incubator, and what requirements remains. 
> 
> Apache Airflow entered incubation around 2 years ago, since then, the Airflow community learned 
> a lot about how to do things in Apache ways. Now we are a very helpful and engaged community, 
> ready to help on all questions from the Airflow community. We delivered multiple releases that have 
> been increasing in quality ever since, now we can do self-driving releases in good cadence. 
> 
> The community is growing, new committers and PPMC members keep joining. We addressed almost all 
> the maturity issues stipulated by Apache Project Maturity Model [1]. So final requirements remain, but
> those just need a final nudge. Committers and contributors are invited to verify the list and pick up the last 
> bits (QU30, CO50). Finally (yahoo!) all the License and IP issues we can see got resolved. 
> 
> Base on those, I believes it's time for us to graduate to TLP. [2] Any thoughts? 
> And welcome advice from Airflow Mentors? 
> 
> Thanks, 
> 
> [1] https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> [2] https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project Regards,