Replies: 3 comments
-
I'll admit I voted to retain the current time because I feel 4am is too harsh for participants from SDT to attend, and active international participation should be nurtured and supported. Realistically I am happy to participate asynchronously as my participation is rare to non-existent. I did like the video! - it is possible to do that more often? converter that shows daylight/summer times for a selection of timezones: |
Beta Was this translation helpful? Give feedback.
-
At this point, keeping the meeting time has a slight edge, so let's keep it the same for now. One more alternative to consider: we could alternate meetings between the two times. |
Beta Was this translation helpful? Give feedback.
-
As of the July 20, 2023 meeting, we'll try 4:00pm ET (2:00pm MT) again. |
Beta Was this translation helpful? Give feedback.
-
The current Rhombus meeting time on Thursdays accommodates East Asia (as Fridays). In particular, given that I run most meetings, it worked for me while on sabbatical in Singapore from last August through May.
The old time had the advantage, for some, of being during regular working hours in the U.S. Since I am now back from sabbatical and in the U.S. again, it works for me to revert to that meeting time.
We could start from scratch to try to pick an optional time for participants around the world, but my guess is that keeping the current time is among our best options. Let's try a poll with simple options.
(Note: Times below shift an hour earlier for some parts of the year in non-U.S. time zones due to daylight saving time. The "Thursday" part is left implicit.)
14 votes ·
Beta Was this translation helpful? Give feedback.
All reactions