-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dask Demo Day 2024-04-18 #374
Comments
Given we only have one demo so far this month, I'm inclined to cancel the meeting for April and pick back up in May. Unless others have something they would like to demo or see demoed (cc @fjetter @mrocklin @jacobtomlinson @quasiben). @ahuang11 would next month (10 AM CT May 16) work for you? |
I'll be at PyCon on May 16, but I'm fine pushing it back a couple months, i.e. June. |
Just wanted to confirm, that tomorrow is cancelled? Edit: I'll assume cancelled! |
Yeah, let's go ahead and cancel this moth. I'll still show up to the first few minutes of the meeting to let anyone who shows up know about the cancellation |
I'll remove the calendar event from the community calendar (do people use
this calendar?)
…On Thu, Apr 18, 2024 at 9:36 AM James Bourbeau ***@***.***> wrote:
Yeah, let's go ahead and cancel this moth. I'll still show up to the first
few minutes of the meeting to let anyone who shows up know about the
cancellation
—
Reply to this email directly, view it on GitHub
<#374 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTFDSGLVBEEZ2R3NDMDY57K7DAVCNFSM6AAAAABGMC3FRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRUGAZTINRYGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
That'd be useful too. Not sure about others, but I use the calendar |
See you all next month |
When
Thursday, April 18, at 10am US CT.
Meeting invite below and also on the Dask calendar:
Agenda
Past demo day agendas listed in #307
Meeting Invite
Join Zoom Meeting
https://us06web.zoom.us/j/89383035703?pwd=WkRJSzNnRTh4T2R1ZjJuVVdJWlMxQT09
The text was updated successfully, but these errors were encountered: