git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DISCUSS] Apache Airflow graduation from the incubator


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 <hitesh@xxxxxxxxxx> 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 <bdbruin@xxxxxxxxx> 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 <jghoman@xxxxxxxxx> 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@xxxxxxxxxxxxxx%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@xxxxxxxxxxxxxxxxxx> 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 <bdbruin@xxxxxxxxx> 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,
> > >>
> >
>