Re: Code ownership over the provider's source code

I like your definition of "stewardship" in this case and I think it's in line with what I had in mind. From: Jarek Potiuk Sent: Monday, April 11, 2022 11:34 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL] Code ownership over the provider's source code CA

Re: Join the biggest Apache Airflow event of the year!

Can't wait! On Tue, Apr 12, 2022 at 9:20 PM Kaxil Naik wrote: > Looking forward to it 🚀 > > On Tue, 12 Apr 2022 at 19:33, Mara Ruvalcaba wrote: > >> >> * Attend the biggest Airflow event of the year! * >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> * This year’s Airflow Summit is fast appr

Re: Join the biggest Apache Airflow event of the year!

Indeed :) On Tue, Apr 12, 2022 at 9:22 PM Joanna Kasprzak < joanna.kasprzak...@gmail.com> wrote: > Can't wait! > > On Tue, Apr 12, 2022 at 9:20 PM Kaxil Naik wrote: > >> Looking forward to it 🚀 >> >> On Tue, 12 Apr 2022 at 19:33, Mara Ruvalcaba wrote: >> >>> >>> * Attend the biggest Airflow eve

Re: Join the biggest Apache Airflow event of the year!

Looking forward to it 🚀 On Tue, 12 Apr 2022 at 19:33, Mara Ruvalcaba wrote: > > * Attend the biggest Airflow event of the year! * > > > > > > > > > > > > > > > > > * This year’s Airflow Summit is fast approaching. The organizers received > over 100 talk submissions. Check out some of the sessio

Re: [ANNOUNCEMENT] Feel the (new) breeze

Very well done Bowrna and Edith and all the mentors 🎉 On Mon, 11 Apr 2022 at 18:10, Ferruzzi, Dennis wrote: > Very cool. Can't wait to play around with it. Congrats and thanks to > Bowrna, Edith, and their mentoring team! > > > > -- > *From:* Jarek Potiuk > *Sent:*

Join the biggest Apache Airflow event of the year!

* * ** *** Attend the biggest Airflow event of the year! ** This year’s Airflow Summit is fast approaching. The organizers received over 100 talk submissions. Check out some of the sessions and our amazing lineup of speakers: https://airflowsummit.org/sessions/2022/

Re: [DISCUSS] Deprecate core airflow k8s settings in KubernetesPodOperator

I just (when reviewing PRs) found a good example to illustrate my concerns: https://github.com/apache/airflow/pull/22253 I commented there why I think we need to have a good plan on what to do with the kubernetes provider before we decide what to do with the settings: https://github.com/apache/a

Re: [DISCUSSION] AIP-49 OpenTelemetry Support for Apache Airflow

> 1. I would assume the path for StatsD (dogstatsd) would be for deprecation - > we will perhaps comment or mark it as deprecation - and should follow the > established (or usual?) process of feature deprecation of Airflow, once the > opentelemetry is in place. Yep. Deprecation should be. And m

Re: [DISCUSS] Deprecate core airflow k8s settings in KubernetesPodOperator

What I am saying is that we should deprecate those settings in core - but only if it is part of decoupling Kubrenetes Executor from the core - otherwise this change gives us pretty much no improvement. In order to do that - we need to at least know what changes will be needed in the core - standa