On our last Dronecode coordination call on November 6th, 2018, we discussed the ever-increasing call problems with timezones, since we are a highly distributed team.
- Daylight saving changes are not uniform across time zones
- We don’t have a majority in a single timezone
- Using 1 timezone and stick with that, be uniform across all calls
The following are proposed timezones from our coordination call, please vote for whichever works best for you, please post proposals as a comment below, we will update the poll.
- Pacific Time Zone (PST)
- Central European Time Zone (CET)
- Other (Please add comment below)
UTM (London, Lisbon, Casablanca)
@rroche This seems to me more of an execution problem: The lead time zone was always CET and this was communicated like that. Given that Europe and US typically go in short sequence in/out of daylight saving changes AND the Google calendar does update accordingly, we just need to make sure that this is handled professionally.
Changing the time zone doesn’t solve the daylight saving problem. Consequently the proposal by @TSC21 also doesn’t help to address the core issue. There is really only one way to solve it: Making sure the call hygiene is good and people do get reminded about the upcoming change and it is displayed online correctly.
To explain that more concretely: Daylight saving ended in the U.S. on November 4 and in Europe already October 28. So there was a single week with a shifted call time. This shouldn’t have been an issue in the first place.