-
Notifications
You must be signed in to change notification settings - Fork 4
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
A better time for community calls? #12
Comments
With Daylight Savings already scrambling my schedule, I took the opportunity to move the calls an hour before the nteract meetings to avoid conflicting with them. As of March 30, they are still on Tuesdays, but now at 8am PST. This could also make them slightly more European-time-zone-friendly. We'll see how that works. I should return to this issue to for the change time since it seems like I've resolved the day of the week/other meeting conflict problem. |
As of March 2022 (but I didn't notice right away) community calls don't have a window open on the Jupyter community calendar. This is because some calls moved with daylight savings time, and others didn't. While there are some openings around the most popular times, I'm not sure how this will impact attendance since it becomes either very early or very late for several time zones. I'm looking at solutions, but I wanted to note this issue here. Edit: I'm polling for community thoughts on cadence. https://twitter.com/isabelapf2/status/1516154732338823170 |
There's a few concerns weighing on me about scheduling community calls. I want to record them here since they've been lingering in my mind with nebulous potential solutions for months now.
Change day of the week
Right now, community call's overlap with nteract's weekly community meetings once a month on Tuesday. This feels particularly inconsiderate to me since it's one of if not the only call that conflicts with another call on the Jupyter community calendar regularly. The only days I see without regular overlap while keeping the same time are Thursday and Friday.
Change time
9am Pacific does work decently for a few timezones, but I'm wondering if I should adopt the JupyterHub team meeting and Quansight Labs happy hour approach of switching off between two times in order to provide more opportunities for pleasant meetings in different timezones. What would be the consequences of this?
The text was updated successfully, but these errors were encountered: