Wow!
I'm excited!
Big thanks for Po-An and Wei!

fat-catTW

Wei Lee <[email protected]> 於 2026年10月30日週五 下午3:53寫道:

> Thanks for putting this together, Po-An!
>
> Looking forward to seeing more contributors joining the community.
> Hope everyone has a great time!
>
> Best,
> Wei
>
> On 2026/10/30 07:49:38 Zhe-You(Jason) Liu wrote:
> > Nice! Thanks Po-An and Wei for organizing this meetup!
> > Looking forward to seeing you all there.
> >
> > Best,
> > Jason
> >
> > On Fri, Oct 30, 2026 at 2:41 PM PoAn Yang <[email protected]> wrote:
> >
> > > Hi everyone,
> > >
> > > We're excited to announce that Taipei.py is hosting an Apache Airflow &
> > > Magpie Development Sprint / Meetup in Taipei on November 24, 2026!
> > >
> > > The Development Sprint is a casual, drop-in contributor workshop: bring
> > > your laptop to work on issues, review PRs, improve docs, or get help
> with
> > > your first contribution. There's no fixed agenda, and you're welcome to
> > > come and go any time during the day.
> > >
> > > Event Details:
> > > - Date: Tuesday, November 24, 2026
> > > - Development Sprint: 10:00–17:00 (UTC+8)
> > >   Registration: https://www.meetup.com/taipei_py/events/317157591/
> > > - Meetup: 18:30–20:30 (UTC+8)
> > >   Registration: https://www.meetup.com/taipei_py/events/317157649/
> > > - Location: 12F., No. 206, Sec. 2, Dunhua S. Rd., Da'an District,
> Taipei
> > > City, Taiwan
> > >   (On arrival, please tell the security guard in the lobby that you're
> > > attending the "Airflow" event, then take the elevator to the 12th
> floor.)
> > > - Language: Taiwanese Mandarin / English
> > > - Hosted by: Taipei.py
> > >
> > > The sprint and the meetup have separate registrations, so feel free to
> join
> > > either or both.
> > >
> > > If you're based in Taiwan or happen to be visiting Taipei, we'd love
> to see
> > > you there!
> > >
> > > Best,
> > > Po-An
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to