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 :
> Great!
>
>
Great!
-s
On Sun, Dec 2, 2018 at 5:53 AM Ash Berlin-Taylor 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:
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?
Thanks @Jakob Homan
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 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
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 wrote:
>
> I'll finish up the template at
>
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
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 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
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 wrote:
> Hi Folks,
>
> Thanks all for your responses and particularly Stefan for his suggestion
> to use the generic Apache way to handle security
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 - Let me know if we need to update
anything else.
Regards,
Kaxil
On Wed, Nov 28, 2018 at 8:00 PM Kaxil Naik wrote:
Definitely willing to pick up the paperwork at
http://incubator.apache.org/projects/airflow.html .
@Jakob Homan Is there any guide on what needs to be
filled out?
On Wed, Nov 28, 2018 at 6:04 PM Bolke de Bruin wrote:
> Ping!
>
> Verstuurd vanaf mijn iPad
>
> > Op 27 nov. 2018 om 21:39
Ping!
Verstuurd vanaf mijn iPad
> Op 27 nov. 2018 om 21:39 heeft Bolke de Bruin 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
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
+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 :
> Oarsome Bolke, thanks for starting this.
>
> It looks like we are closer than I thought!
>
> We can use those security lists
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
+1 thank you for everyone who helped drive this (especially Bolke!).
On Tue, Nov 27, 2018 at 1:02 AM Tao Feng wrote:
> And happy to help out any items for the TLP push.
>
> On Mon, Nov 26, 2018 at 9:53 PM Tao Feng wrote:
>
> > +1 as well. (do we need to start another vote thread per Jakob's
>
And happy to help out any items for the TLP push.
On Mon, Nov 26, 2018 at 9:53 PM Tao Feng 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 wrote:
>
>> Hi All,
>>
+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 wrote:
> Hi All,
>
> With the Apache Airflow community healthy and growing, I think now would
> be a good time to
> discuss where we
+1 as well. I’m glad to see the community is thriving.
On Mon, Nov 26, 2018 at 6:11 PM Maxime Beauchemin <
maximebeauche...@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
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 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
+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
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
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
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,
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 wrote:
> Ping!
>
> Sent from my iPhone
>
> > On 24 Nov 2018, at 12:57,
Ping!
Sent from my iPhone
> On 24 Nov 2018, at 12:57, Bolke de Bruin 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.
>
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
26 matches
Mail list logo
