Ben Michel

@lukaszewczak oh right, an end-time would be helpful lol. I'll add that now. Thanks for sharing your availability. Yes, we should probably set up a YouTube recording stream like other...

I think it would be advantageous for us to select an ongoing meeting time that works for everyone as soon as we can, so we can depend on it regularly....

@vanessayuenn brilliant! That sounds awesome! 🍻

@RichardLitt I'm very sorry for the confusion. The missing piece is that we finalized a meeting day, but not a time. I will be clearing that up today and we...

Thanks @RichardLitt. Absolutely true. Thanks for https://github.com/nodejs/i18n/issues/64, time to get the spark going and make it happen. 😎 After this meeting, I think it might be most beneficial to oscillate...

We can verify and nail down our reoccurring time & dates tomorrow at our [next WG meeting](https://github.com/nodejs/i18n/issues/64)! 🙌 @bnb once we do that–we'd love to get them on the calendar!...

@nodejs/i18n bumping this. Let's plan on picking back up with regular meetings on 6/18. I'm going to throw out 2pm UTC (7am PST / 16:00 CEST) as the targeted time....

@nodejs/i18n I'll get this on the Node.js calendar asap, but for now let's track this [calendar event](https://calendar.google.com/event?action=TEMPLATE&tmeid=M3NrajZrdTFoYzZhNWZ2anI4b2Flam40aGogYmVubWljaGVsQGludmlzaW9uYXBwLmNvbQ&tmsrc=benmichel%40invisionapp.com). 🗓

@zeke @srl295 @alexandrtovmach @benhalverson @joesepi @TiagoDanin @JoseJPR (et al) – hope to see y'all there! 🙌

@srl295 no problem at all, thanks for letting us know. Looking forward to catching up with you next time @srl295! 🙌