airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bolke de Bruin <bdbr...@gmail.com>
Subject Re: [DISCUSS] Apache Airflow graduation from the incubator
Date Fri, 30 Nov 2018 22:06:35 GMT
Thanks Jakob!

Verstuurd vanaf mijn iPad

> Op 30 nov. 2018 om 22:49 heeft Jakob Homan <jghoman@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 <jghoman@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 <fengtao04@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 <fengtao04@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 <bdbruin@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,
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 

Mime
View raw message