Re: [VOTE] December PR of the Month

OK. Let the fight begin now :) On Wed, Jan 3, 2024 at 5:15 AM Amogh Desai wrote: > My vote goes to #35719. Having a nice UI fix come in, that too from a first > time contributor > makes it a winner for me! > > Thanks & Regards, > Amogh Desai > > On Wed, Jan 3, 2024 at 7:51 AM Wei Lee wrote: >

[PROPOSAL] let's update the community content on the landing pages

Hello all, Much of the community content on the landing pages has not been updated in a long time. Also, the approach taken to display upcoming meetups relies on hardcoding, which is hard to maintain. I’ve opened a PR to address these issues with the landing pages and would appreciate input

Re: [VOTE] December PR of the Month

My vote goes to #35719. Having a nice UI fix come in, that too from a first time contributor makes it a winner for me! Thanks & Regards, Amogh Desai On Wed, Jan 3, 2024 at 7:51 AM Wei Lee wrote: > I want to vote for https://github.com/apache/airflow/pull/35926, and > thank Jarek for bringing

Re: [DISCUSSION] Enabling `pre-commit.ci` application for Airflow

Same as Amogh. Even though I would like to fix that myself, it would make it much easier for those who aren’t familiar with these tools and still be able to contribute. But we might need to doc this behavior somewhere (GitHub PR issue might make more sense 樂). Otherwise, the contributor might

Re: [VOTE] December PR of the Month

I want to vote for https://github.com/apache/airflow/pull/35926, and thank Jarek for bringing it up. https://github.com/apache/airflow/pull/35719 is also great, so it's a difficult choice. Best, Wei > On Jan 3, 2024, at 6:04 AM, Jarek Potiuk wrote: > > I'd like to propose another one: >

Re: [DISCUSSION] Enabling `pre-commit.ci` application for Airflow

Same as Amogh. Even though I would like to fix that myself, it would make it much easier for those who aren’t familiar with these tools and still be able to contribute. But we might need to doc this behavior somewhere (GitHub PR issue might make more sense 樂). Otherwise, the contributor might

Re: [VOTE] December PR of the Month

While we have many good contenders this month. With 35719 and especially 36472 being on my watchlist, 35926 is something I've been looking forward to. Thanks for putting 35926 on the radar Jarek. On Tue, 2 Jan 2024, 23:05 Jarek Potiuk, wrote: > I'd like to propose another one: >

Re: [VOTE] December PR of the Month

I'd like to propose another one: https://github.com/apache/airflow/pull/35926 - Create FAB provider and move FAB auth manager in it I think that one is something some of us have been talking about getting rid of FAB for a long time. While FAB was really cool when Airflow started, it has not aged

Re: Looking for co-mentor in Major League Hacking Spring 2024 Fellows

Cool :) . I will come back to it later this week (been heads down and deep-diving python packaging and still got some things there :). On Tue, Jan 2, 2024 at 6:47 PM Brent Bovenzi wrote: > I'm happy to help out however I can. I used to be a part of MLH and I'm > still friends with the founder.

[PROPOSAL] Standardize Airflow Packaging and build process (modern appropriate PEP-compliant tooling)

Hello everyone. Tl;DR; I have a proposal to adopt Hatchling as a build backend (and recommend, but not require Hatch as frontend) for Airflow as our way of switching to PEP-standard compliant pyproject.toml way of installing Airflow (including local venvs) and building the Airflow package. I

Re: Looking for co-mentor in Major League Hacking Spring 2024 Fellows

I'm happy to help out however I can. I used to be a part of MLH and I'm still friends with the founder. There are a bunch of improvements we can make to the REST API that I'd love to see. On Fri, Dec 29, 2023 at 3:11 AM Jarek Potiuk wrote: > Absolutely - devlist is the best place :) > > On

Re: [VOTE] December PR of the Month

+1 for #35719 On Tue, Jan 2, 2024 at 8:59 AM Scheffler Jens (XC-AS/EAE-ADA-T) wrote: > I‘d vote for #35719 - because I like external contributions especially to > move ahead in UI! > > Sent from Outlook for iOS > > From: Briana Okyere >

Re: [VOTE] December PR of the Month

I‘d vote for #35719 - because I like external contributions especially to move ahead in UI! Sent from Outlook for iOS From: Briana Okyere Sent: Tuesday, January 2, 2024 5:51:12 PM To: dev@airflow.apache.org Subject: [VOTE] December PR of

[VOTE] December PR of the Month

Happy New Year Everyone :). It’s once again time to vote for the PR of the Month. I decided to wait to release the vote until folks were back from their holidays so that it was not missed. With the help of the `get_important_pr_candidates` script in dev/stats, we've identified the following

Re: [DISCUSSION] Enabling `pre-commit.ci` application for Airflow

I like the concept! +1 On 2023/12/30 11:16:35 Amogh Desai wrote: > I am aligning here with Pierre, but I am not against the idea of enabling > the pre commit ci application. > > I’d rather have myself fix the issue as it sometimes also lets me have > second,third or multiple passes at my code

[ANNOUNCE] Apache Airflow Providers prepared on December 31, 2023 are released

Dear Airflow community, I'm happy to announce that new versions of Airflow Providers packages prepared on December 31, 2023 were just released. Full list of PyPI packages released is added at the end of the message. The source release, as well as the binary releases, are available here:

[RESULT][VOTE] Airflow Providers - release of December 31, 2023

Hello, Apache Airflow Providers prepared on DATE OF RELEASE have been accepted. 3 "+1" binding votes received: - Jarek Potiuk (binding) - Husein Awala (binding) - Elad Kalif (binding) 5 "+1" non-binding votes received: - Utkarsh Sharma - Phani Kumar - Amogh Desai - Wei Lee - Pankaj Singh Vote

Re: [DISCUSS] Interested in joining/leaving the triage team ?

Hi Jarek, I would also want to continue being part of the team as well. Best, Wei > On Jan 2, 2024, at 10:47 PM, utkarsh sharma wrote: > > I can move out of triage team now :) > > On Tue, 2 Jan 2024 at 8:15 PM, Rahul Vats wrote: > >> Hi Jarek, >> >> As discussed in #issue-triage, I would

Re: [DISCUSS] Interested in joining/leaving the triage team ?

I can move out of triage team now :) On Tue, 2 Jan 2024 at 8:15 PM, Rahul Vats wrote: > Hi Jarek, > > As discussed in #issue-triage, I would also like to nominate myself for the > triage team. > > > Regards, > > Rahul Vats > > On Tue, 2 Jan, 2024, 18:29 Ankit Chaurasia, wrote: > > > Hi Jarek,

Re: [DISCUSS] Interested in joining/leaving the triage team ?

Hi Jarek, As discussed in #issue-triage, I would also like to nominate myself for the triage team. Regards, Rahul Vats On Tue, 2 Jan, 2024, 18:29 Ankit Chaurasia, wrote: > Hi Jarek, > > I would want to continue being a "collaborators" team for the triage. > > *Ankit Chaurasia* > HomePage

Re: [DISCUSS] Interested in joining/leaving the triage team ?

Hi Jarek, I would want to continue being a "collaborators" team for the triage. *Ankit Chaurasia* HomePage | LinkedIn On Sat, Dec 30, 2023 at 1:36 PM Jarek Potiuk wrote: > A regular question if there are people who

[Discussion] AIP-60 Standard URI representation for Airflow Datasets

Happy 2024 everyone! I’m going to kick off the new year by formally proposing a new AIP. This attempts to standardise the URI format used by Dataset events. This is driven a lot by the lack of adoption of Datasets. It turns out (maybe not surprisingly when I think about it) simply triggering

Re: [VOTE] Airflow Providers prepared on December 31, 2023

+1 (binding) On Mon, Jan 1, 2024 at 2:54 PM Jarek Potiuk wrote: > 1 more binding vote needed for Waeviate :) > > On Mon, Jan 1, 2024 at 6:11 AM Pankaj Singh > wrote: > > > +1 (non binding) > > > > On Mon, Jan 1, 2024 at 8:29 AM Wei Lee wrote: > > > > > +1 (non binding) > > > > > > Best, > > >