Re: Airflow: Apache Graduation
There is a maturity check that we can do. Don't have the link ready now.
But can look it up later.
To me two things need to be more mature
1. Handling of security issues
2a having ppl aware that with new dependencies updates to dependencies the
respective licenses need to be updated. Too often I need to fix some issues
at release time.
2b versions need to be added to the licenses (version of the software)
Op vr 21 sep. 2018 13:00 schreef Ash Berlin-Taylor <ash@xxxxxxxxxx>:
> Your guess is as good as mine on what is involved in graduation. I think
> that we sorted the Licensing issues in 1.10.0 (even if the way we sorted it
> was a little annoying - having to specify the environment variable at `pip
> install` time is a littlle bit un-pythonic, but I wasn't thinking of fixing
> that in 1.10.1)
> Some of the steps and requirements are listed here
> graduating_to_a_top_level_project <
> https://incubator.apache.org/guides/graduation.html>, but in summary from
> a quick read of it I think the process is:
> - Collect some information, put it on
> http://incubator.apache.org/projects/airflow.html <
> http://incubator.apache.org/projects/airflow.html> for the IPMC
> - We as a community hold a vote on if we think we're ready to graduate
> - IPMC vote on it too
> - propose motion for (monthly) Apache board meeting
> There might be a few more steps involves, such as drafting a Charter (we
> would probably start with a "stock" Apache one)
> > On 20 Sep 2018, at 18:22, Maxime Beauchemin <maximebeauchemin@xxxxxxxxx>
> > Yeah let's make it happen! I'm happy to set some time aside to help with
> > the final push.
> > Max
> > On Thu, Sep 20, 2018 at 9:53 AM Sid Anand <sanand@xxxxxxxxxx> wrote:
> >> Folks! (specifically Bolke, Fokko, Ash)
> >> What's needed to graduate from Apache?
> >> Can we make 1.10.1 be about meeting our licensing needs to allow us to
> >> graduate?
> >> -s