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]> 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]> 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] > > > > 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]> > >> *Date: *Saturday, August 2, 2025 at 1:12 PM > >> *To: *"Bowen, Rich" <[email protected]> > >> *Cc: *"Scheffler Jens (XC-DX/ETV5)" <[email protected]>, > Amogh > >> Desai <[email protected]>, Briana Okyere <[email protected] > >, > >> "Bishundeo, Rajeshwar" <[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. > >> > >> > >> > >> Will do :) > >> > >> > >> > >> On Sat, Aug 2, 2025 at 4:55 PM Bowen, Rich <[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]> 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]> 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]> 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]> 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]> > 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]> 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]> 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]> 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]>> 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]>> wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Jul 22, 2025, at 6:45 AM, Jarek Potiuk <[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]> > >>>>> For additional commands, e-mail: [email protected] > >> <mailto: > >>>>> [email protected]> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>> > >> > >> > >> > >> > >> > >> > >
