git.net

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

Re: Airflow: Apache Graduation


The big list that *has* to be filled out and correct is here:
http://incubator.apache.org/projects/airflow.html

This is usually done by the Champion, Chris Riccomini.  Chris  - are
you still interested to do this?

After that and the maturity questionnaire are in good shape, it's:
1) Graduation DISCUSS by the community.  This thread can cover that,
although an explicit DISCUSS would help too.  Example:
https://mail-archives.apache.org/mod_mbox/samza-dev/201412.mbox/%3CCADiKvVtBOPaji22Nd3927R6Tj%2BmWpxnHH%2Bk%3DyXCQEMGf_CnAqw%40mail.gmail.com%3E
2) Graduation VOTE by the community on a resolution for the new top
level project (TLP). Example:
https://mail-archives.apache.org/mod_mbox/samza-dev/201412.mbox/%3CCADiKvVt_LK9%2BBXC8eR_gb3ALOU2KFJqDDyZOLao7rm0XjuZmcg%40mail.gmail.com%3E
- most of the text is boiler plate, but be sure not leave anything in
there that shouldn't be (Jakob said with experience...)
3) Exact same text is VOTEd on by the IPMC
4) Champion adds the resolution to the Board's next monthly agenda,
where the Board approves it.  Project is officially TLP once that is
done.
5) Champion cleans up incubator resources, creates new TLP resources.
Example: https://jira.apache.org/jira/browse/INFRA-10639

-Jakob


On 21 September 2018 at 13:49, Bolke de Bruin <bdbruin@xxxxxxxxx> wrote:
> 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
> 2. Licensing.
>  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)
>
> B.
>
> 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)
>>
>> -ash
>>
>> > On 20 Sep 2018, at 18:22, Maxime Beauchemin <maximebeauchemin@xxxxxxxxx>
>> wrote:
>> >
>> > 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
>> >>
>>
>>