[GitHub] [airflow-on-k8s-operator] kaxil merged pull request #2: Fix repo - populate vendor, rename paths etc.

2020-01-21 Thread GitBox
kaxil merged pull request #2: Fix repo - populate vendor, rename paths etc. URL: https://github.com/apache/airflow-on-k8s-operator/pull/2 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [airflow-on-k8s-operator] barney-s opened a new pull request #2: Fix repo

2020-01-21 Thread GitBox
barney-s opened a new pull request #2: Fix repo URL: https://github.com/apache/airflow-on-k8s-operator/pull/2 Regenrating vendor files Updating to newer libraries renaming paths This is an automated message from the

Re: Call for presentations for ApacheCon North America 2020 now open

2020-01-21 Thread Qingping Hou
Following up on this, if we want to give a talk about Airflow, which track should it belong to? General/Other? Thanks, QP Hou On Tue, Jan 21, 2020 at 2:18 PM Sid Anand wrote: > > FYI! > > -- Forwarded message - > From: Rich Bowen > Date: Tue, Jan 21, 2020 at 7:34 AM > Subject:

Fwd: Call for presentations for ApacheCon North America 2020 now open

2020-01-21 Thread Sid Anand
FYI! -- Forwarded message - From: Rich Bowen Date: Tue, Jan 21, 2020 at 7:34 AM Subject: Call for presentations for ApacheCon North America 2020 now open To: plann...@apachecon.com Dear Apache enthusiast, (You’re receiving this message because you are subscribed to one or

Re: "Powered By" (working title) section at the official Airflow Website

2020-01-21 Thread Aizhamal Nurmamat kyzy
+1 on having both "Powered by" and "Ecosystem" sections. Another apache project example that has these two pages is Flink: --> https://flink.apache.org/poweredby.html --> https://flink.apache.org/ecosystem.html On Fri, Jan 17, 2020 at 6:44 AM Nathan Maynes wrote: > Some thoughts on adding an