This is Thursday, October 9th, right? And the 8:30 time works for me. The 5:30 time does not.
—Rich Yes, the 1pm time works for me. > On Oct 5, 2025, at 5:23 AM, Jarek Potiuk <[email protected]> wrote: > > I am (almost) back from vacation - but I thought maybe then we should do > it **slightly** differently (and better). Rich - I am quite sure you will > love this idea. > > We have the Airflow Summit next week. And we are all there. Same time zone > (Pacific Time), same place (seattle, Hyatt). We could likely find a place > to connect with Rich, and likely arrange it as **live from the Summit" - > and we could then arrange a group of us sitting together in front of a > camera with the Airflow Summit banner behind us or smth. > > And on top of just talking about Airflow 3.0 - we could share impressions > from the Summit happening. > > That would be even more powerful when it comes to the collaboration, team > spirit, Airflow 3, Airflow Summit and so on. > > I think maybe Thursday lunch time (?) might be a good idea - Airflow > Summit will be ALMOST over and most of us will be maybe tired but also with > most of our Summit duties done and with heads full of impressions. And we > will have time to prepare and test it before > > Rich - WDYT? Would you be able to find time on Thu lunch time (we have > lunch break 1pm - 2pm (Pacific Time)? > Another option is Wed 5.30pm, or maybe (if there will be no other options > and might be painful - we could likely do it in the morning Thu - we start > at 9.15 - so it would have to be 8.30). Possibly we can arrange other times > as well if there are no other options. > > J. > > > > On Thu, Sep 25, 2025 at 8:14 AM Bishundeo, Rajeshwar <[email protected]> > wrote: > >> All, >> I had intent to try to set this up this week but due to an emergent >> situation I am unable to participate this week. If we can push this to next >> week (latter half), I may have some free time to join. If it is an >> inconvenience to most, then I will have to withdraw and I can have Niko >> take my place as he is very familiar with our involvement for AF3 and can >> represent AWS in the discussion. >> >> >> -- Rajesh >> >> >> >> From: Bowen, Rich <[email protected]> >> Date: Thursday, September 25, 2025 at 11:09 AM >> To: Scheffler Jens (XC-AS/EAE-ADA-T) <[email protected]> >> Cc: [email protected] <[email protected]>, Bishundeo, Rajeshwar >> <[email protected]>, Amogh Desai <[email protected]>, Briana Okyere >> <[email protected]>, [email protected] <[email protected]> >> Subject: RE: [EXT] [DISCUSS] Apache Airflow 3.0 Feathercast (was Re: >> [ANNOUNCE] Apache Airflow 3.0.3 Released) >> >> CAUTION: This email originated from outside of the organization. Do not >> click links or open attachments unless you can confirm the sender and know >> the content is safe. >> >> >> >> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. >> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez >> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que >> le contenu ne présente aucun risque. >> >> >> >>> On Sep 25, 2025, at 11:03 AM, Scheffler Jens (XC-AS/EAE-ADA-T) < >> [email protected]> wrote: >>> >>> Hi Rich, >>> >>> as I remember all named persons in CC were addressed. >>> >>> I can offer tomorrow or Mon-Wed next week after 5PM CEST, Thursday next >> week post 6PM and Friday next week (anytime) >> >> My availability is here: >> https://prelude.amazon.com/s/fG7MuGadD/W8iImF/-/rcbowen >> >> Today is already pretty much shot, but tomorrow I’m available almost all >> day, and Monday and Tuesday next week have a lot of openings, too. >> >> I’m in Eastern US time, and so my mornings sound like they’d be the best >> intersection with CEST available time. >> >> —Rich >>> >>> From: Bowen, Rich <[email protected] <mailto:[email protected]>> >>> Sent: Donnerstag, 25. September 2025 16:06 >>> To: [email protected] <mailto:[email protected]>; >> [email protected] <mailto:[email protected]> >>> Cc: Bishundeo, Rajeshwar <[email protected] <mailto: >> [email protected]>>; Scheffler Jens (XC-AS/EAE-ADA-T) < >> [email protected] <mailto:[email protected]>>; Amogh >> Desai <[email protected] <mailto:[email protected]>>; Briana >> Okyere <[email protected] <mailto:[email protected]>> >>> Subject: Re: [DISCUSS] Apache Airflow 3.0 Feathercast (was Re: >> [ANNOUNCE] Apache Airflow 3.0.3 Released) >>> >>> Hey, folks, now that I’m all caught up from travels, I’d really like to >> get this scheduled and recorded. Do you have any times in mind? Do we know >> for sure who’s going to be on this recording? >>> >>> >>> >>> On Sep 17, 2025, at 1:08 PM, Bowen, Rich <[email protected] <mailto: >> [email protected]>> wrote: >>> >>> Excellent. Rajesh has access to my internal Amazon calendar. If y’all >> want to arrange a time and have Rajesh put something on my calendar, I’ll >> be ready. >>> >>> Thanks! >>> >>> >>> >>> On Sep 17, 2025, at 11:51 AM, Bishundeo, Rajeshwar <[email protected] >> <mailto:[email protected]>> wrote: >>> >>> I can make time next week. >>> >>> -- Rajesh >>> >>> From: Scheffler Jens (XC-AS/EAE-ADA-T) <[email protected] >> <mailto:[email protected]>> >>> Date: Wednesday, September 17, 2025 at 2:30 AM >>> To: Amogh Desai <[email protected] <mailto:[email protected]>>, >> Bowen, Rich <[email protected] <mailto:[email protected]>> >>> Cc: [email protected] <mailto:[email protected]> < >> [email protected] <mailto:[email protected]>>, Bishundeo, >> Rajeshwar <[email protected] <mailto:[email protected]>>, Briana >> Okyere <[email protected] <mailto:[email protected]>> >>> Subject: RE: [EXT] [DISCUSS] Apache Airflow 3.0 Feathercast (was Re: >> [ANNOUNCE] Apache Airflow 3.0.3 Released) >>> >>> CAUTION: This email originated from outside of the organization. Do not >> click links or open attachments unless you can confirm the sender and know >> the content is safe. >>> >>> >>> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur >> externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous >> ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas >> certain que le contenu ne présente aucun risque. >>> >>> >>> Works for me except that I have a couple of training in the evening. >> Monday or Friday would be best. Wednesday will be possible if it is late in >> Germany (post 8PM CET) >>> >>> From: Amogh Desai <[email protected] <mailto:[email protected]>> >>> Sent: Mittwoch, 17. September 2025 08:11 >>> To: Bowen, Rich <[email protected] <mailto:[email protected]>> >>> Cc: [email protected] <mailto:[email protected]>; Bishundeo, >> Rajeshwar <[email protected] <mailto:[email protected]>>; Scheffler >> Jens (XC-AS/EAE-ADA-T) <[email protected] <mailto: >> [email protected]>>; Briana Okyere <[email protected] >> <mailto:[email protected]>> >>> Subject: Re: [DISCUSS] Apache Airflow 3.0 Feathercast (was Re: >> [ANNOUNCE] Apache Airflow 3.0.3 Released) >>> >>> Right, let's not wait too long. It's always hard to get the entire squad >> together! >>> >>> Rich -- I could do it as early as next week if that works. >>> >>> Rajesh, Jens, Briana -- does that work for you? >>> >>> >>> Thanks & Regards, >>> Amogh Desai >>> >>> >>> On Sat, Sep 13, 2025 at 7:15 PM Bowen, Rich <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> Or, we could do it with those of you who are here, if you like? >>> >>> >>> On Sep 12, 2025, at 4:35 PM, Jarek Potiuk <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> How about you just ... go and do it... I dropped the ball on coordinating >>> it - mostly because of all the Airflow 3.0 + 3.1 prep and Community Over >>> Code/Airflow summit preps - but .. you actually don't need me to prepare >> :D >>> - and I am going for vacations after CoC (heading off to Canada) - so I >> do >>> not want to hold that any longer. >>> >>> Rich is here at the Community Over Code but I guess one of you might want >>> to lead the setup with Rich while I am on vacation after the Community >> Over >>> Code. >>> >>> Just to copy my initial idea for the feathercast... And maybe you can >> make >>> it happen :). >>> >>> -------------- >>> >>> I think it might be a good idea if several of the people (4?) who were >>> working with Airflow 3 - individual community members, and stakeholders >>> representatives - could record feathercast with Rich - but not about the >>> "technical" part of Airflow 3 and what we've done, but more about "how" >>> we've done it. >>> >>> I don't think there were many Feathercasts with multiple people in the >>> past, but I think the biggest value - and something that we can talk >> about, >>> is how we worked as a community together on Airflow 3 and how we managed >> to >>> basically rebuild "Airflow 3 plane" with the "new AI world" in mind - >> while >>> actually "flying it". >>> >>> We did it while continuing to support Airflow 2 and the great community >> of >>> users we had - all with the cooperation and collaboration between the >>> individual community members, and - most importantly - with all the >>> commercial stakeholders leading and driving and participating in it, all >>> with the "Apache Way" as our guiding principle. >>> >>> All that while continuously growing (with accelerating speed it seems) of >>> both the contributors and users community. This is - I think - by far the >>> biggest achievement we can be proud of and something we can talk about. >>> >>> We will have a lot of "use case", "tech talks", "vision" things - at >>> Airflow Summit, but we had an idea in the PMC that we should also talk >>> about "how" this all was possible with collaboration and community and >>> Apache Way, and Feathercast / PlusOne seems to be like a perfect fit for >> it. >>> >>> J. >>> >>> On Thu, Aug 7, 2025 at 9:03 AM Bishundeo, Rajeshwar <[email protected] >> <mailto:[email protected]> <mailto:[email protected]>> >>> wrote: >>> >>> >>> Sorry folks for not responding sooner, it’s been pretty busy for me at >>> work. I am out of office next week (Aug10-17) and will be back Aug 18-21. >>> Then I’m out again Au22-26. I will make time for the few days I’m back >> for >>> the interview – if that aligns with everyone. >>> >>> >>> >>> -- Rajesh >>> >>> >>> >>> >>> >>> *From: *Jarek Potiuk <[email protected] <mailto:[email protected]> >> <mailto:[email protected]>> >>> *Date: *Saturday, August 2, 2025 at 1:12 PM >>> *To: *"Bowen, Rich" <[email protected] <mailto:[email protected]> >> <mailto:[email protected]>> >>> *Cc: *"Scheffler Jens (XC-DX/ETV5)" <[email protected] >> <mailto:[email protected]> <mailto:[email protected]>>, >> Amogh >>> Desai <[email protected] <mailto:[email protected]> >> <mailto:[email protected]>>, Briana Okyere <[email protected] >> <mailto:[email protected]> <mailto:[email protected]>>, >>> "Bishundeo, Rajeshwar" <[email protected] <mailto:[email protected]> >> <mailto:[email protected]>>, "[email protected] <mailto: >> [email protected]><mailto:[email protected]>" < >>> [email protected] <mailto:[email protected]> <mailto: >> [email protected]>> >>> *Subject: *RE: [EXT] [DISCUSS] Apache Airflow 3.0 Feathercast (was Re: >>> [ANNOUNCE] Apache Airflow 3.0.3 Released) >>> >>> >>> >>> *CAUTION*: This email originated from outside of the organization. Do not >>> click links or open attachments unless you can confirm the sender and >> know >>> the content is safe. >>> >>> >>> >>> *AVERTISSEMENT*: Ce courrier électronique provient d’un expéditeur >>> externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si >> vous >>> ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas >>> certain que le contenu ne présente aucun risque. >>> >>> >>> >>> Will do :) >>> >>> >>> >>> On Sat, Aug 2, 2025 at 4:55 PM Bowen, Rich <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> Thank you. Please let me know when you’re ready to proceed. >>> >>> >>> >>> For myself, I’ll be “on the road” until about August 18th, but can find >>> time to do an interview during most of that time, with a little advance >>> notice. I’ll be taking my gear everywhere with me, although the >> microphone >>> and “studio” is a lot better, acoustically, at home. >>> >>> >>> >>> —Rich >>> >>> >>> >>> On Aug 1, 2025, at 11:36 PM, Jarek Potiuk <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> >>> >>> Holiday season - now Briana is on holidays :).... So we will wait until >>> she is back :) >>> >>> >>> >>> On Fri, Jul 25, 2025 at 8:48 PM Bowen, Rich <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> On Wednesday I’m going to Fossy, and will be back in the office the >>> following Wednesday. I can presumably do a recording while I’m there, but >>> my schedule at conferences is always a little unpredictable. >>> >>> >>> >>> —Rich >>> >>> >>> >>> On Jul 25, 2025, at 1:46 PM, Jarek Potiuk <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> >>> >>> I just realized Jens is on vacations - we might want to do it after he is >>> back, so let's wait till he is back (unless others plan vacations in the >>> next 2 weeks :) >>> >>> >>> >>> On Thu, Jul 24, 2025 at 9:25 AM Jarek Potiuk <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> Proposal: let's do a "prep" session first .... I am happy to facilitate >>> it and play Rich's role - and we can do a dry run :). I think it will be >>> much more efficient and smooth if we do a short walk through on what You >>> want to say. >>> >>> >>> >>> Rich - this is not yet for you -> we will make a second doodle where the >>> team will find a good time :) >>> >>> >>> >>> Vote by. Friday please :) >>> >>> >>> >>> https://doodle.com/group-poll/participate/aAKwxgpd >>> >>> >>> >>> J. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On Thu, Jul 24, 2025 at 7:38 AM Amogh Desai <[email protected] >> <mailto:[email protected]> <mailto:[email protected]>> wrote: >>> >>> Nice, so I think we have a quorum here! >>> >>> Rich -- feel free to initiate something. >>> >>> Thanks & Regards, >>> Amogh Desai >>> >>> >>> On Wed, Jul 23, 2025 at 10:23 PM Briana Okyere >>> <[email protected] <mailto:[email protected]> >> <mailto:[email protected]>.invalid> wrote: >>> >>> >>> Happy to join (if you all think it makes sense) to give a brief overview >>> of >>> >>> our community initiatives like; meetups, PR of the month, monthly >>> towhall, >>> >>> engaging broader community >>> >>> On Tue, Jul 22, 2025 at 8:14 AM Jarek Potiuk <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >>> >>> >>> Just to be clear, I didn’t mean to cut you out of it, necessarily, >>> but >>> >>> a >>> >>> large part of this work is to “humanize” ASF projects, and the more new >>> faces we can show, the better. >>> >>> Perfectly understood :) . And it was my own idea to remove myself from >>> such >>> >>> things and leave space for others. I am learning that (it's hard for >>> me) >>> >>> but ... it's getting better :D. >>> >>> >>> You were a big part of AF3 and maybe you can still work with us to >>> ensure >>> >>> we don’t forget anything as we plan on what we want to cover? >>> >>> To be honest - not sure if you still remember - I was also the biggest >>> sceptic before we all committed to it and started the discussion >>> "should >>> >>> we?"... Happy to have a brainstorm together and leave space for others >>> to >>> >>> show up. >>> >>> Besides - If you look at Jens, we share a lot of "features", and he >>> already >>> >>> got "Jarek" as a caption at the few dev calls, so we can go half-way >>> and >>> >>> have Jens speaking with "Jarek" caption ;) >>> >>> J. >>> >>> >>> >>> >>> >>> On Tue, Jul 22, 2025 at 4:14 PM Bishundeo, Rajeshwar >>> <[email protected] <mailto:[email protected]> >> <mailto:[email protected]>> wrote: >>> >>> >>> Jarek, >>> You were a big part of AF3 and maybe you can still work with us to >>> ensure >>> >>> we don’t forget anything as we plan on what we want to cover? >>> >>> >>> -- Rajesh >>> >>> >>> >>> >>> >>> >>> On 2025-07-22, 8:44 AM, "Jarek Potiuk" <[email protected] <mailto: >> [email protected]> <mailto:[email protected]> <mailto: >>> [email protected] <mailto:[email protected]> <mailto:[email protected]>>> >> wrote: >>> >>> >>> CAUTION: This email originated from outside of the organization. Do >>> not >>> >>> click links or open attachments unless you can confirm the sender and >>> know >>> >>> the content is safe. >>> >>> >>> >>> >>> >>> >>> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur >>> externe. >>> >>> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne >>> pouvez >>> >>> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas >>> certain >>> >>> que >>> >>> le contenu ne présente aucun risque. >>> >>> >>> >>> >>> >>> >>> Ok. So we might limit it.. I am happy to drop out - as Rich mentioned >>> - <I already have a lot of "airtime"> - and I am sure the others will >>> do fantastic job :) >>> >>> >>> On Tue, Jul 22, 2025 at 1:58 PM Bowen, Rich <[email protected] <mailto: >> [email protected]> <mailto:[email protected]> >>> <mailto: <mailto:%0b> >>> >>> [email protected] <mailto:[email protected]> <mailto:[email protected]>>> >> wrote: >>> >>> >>> >>> >>> On Jul 22, 2025, at 6:45 AM, Jarek Potiuk <[email protected] <mailto: >> [email protected]> <mailto:[email protected]> >>> <mailto: <mailto:%0b> >>> >>> [email protected] <mailto:[email protected]> <mailto:[email protected]>>> >> wrote: >>> >>> >>> Yeah. I think we can do recording - the 4 of us: Jarek, Jens, Raj, >>> Amogh. >>> >>> >>> >>> FWIW, 4 people is a *LOT* for a 10 minute interview. Please be sure >>> to >>> >>> give some thought ahead of time to who will be covering which parts, >>> so >>> >>> that we don’t have anyone left out, or any voice(s) dominating. >>> >>> >>> Please have a look at >>> https://plusone.apache.org/preparing-for-an-interview/ < >>> https://plusone.apache.org/preparing-for-an-interview/> ahead of >>> time >>> >>> for >>> >>> some tips about how it’s going to go. >>> >>> >>> Thanks! >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] <mailto: >> [email protected]> <mailto: >> [email protected]> <mailto: <mailto:%0b> >>> [email protected] <mailto: >> [email protected]> <mailto: >> [email protected]>> >>> For additional commands, e-mail: [email protected] <mailto: >> [email protected]> <mailto:[email protected]> >>> <mailto: <mailto:%0b> >>> >>> [email protected] <mailto:[email protected]> >> <mailto:[email protected]>> >>> >> >> — Rich Bowen [email protected]
