Open wking opened 10 years ago
I'd be +1 on dropping everything except UTC, SF time, and NZ time (since the US meeting is always announced in SF time thanks to the Docker headquarters, and the other meeting is announced in "Sven-local" time).
ping @SvenDowideit; WDYT?
On Mon, Aug 11, 2014 at 04:34:58PM -0700, Tianon Gravi wrote:
I'd be +1 on dropping everything except UTC, SF time, and NZ time (since the US meeting is always announced in SF time thanks to the Docker headquarters, and the other meeting is announced in "Sven-local" time).
Then you'll have to bump UTC and SF/NZ as Sven and San Fran go in and out of daylight savings time. At least it's only two governments you have to keep up with, but folks in other countries may not know when to check for the DST transition.
Well, the US meeting is at 10:30am SF time, so whether we list the SF meeting time or not, even the UTC will change come DST.
On Mon, Aug 11, 2014 at 04:42:55PM -0700, Tianon Gravi wrote:
Well, the US meeting is at 10:30am SF time, so whether we list the SF meeting time or not, even the UTC will change come DST.
But the SF folks know when SF trips over the daylight savings time changes, so it's an easier transition for them if the UTC time stays constant. Vs. folks in other countries needing to learn SF's daylight savings schedule. Of course, if an overwhelming majority of participants are in the US and Canada, maybe there aren't any folks troubled by the shifting times.
The meeting time was set as such specifically to accommodate SF employee attendance, whose schedules will shift when DST does, and which is why the meeting time also shifts accordingly (from a UTC perspective).
Listing non-UTC times is more trouble than it's worth. For one, I think 5:30pm Thursday UTC is actually 11pm Thursday in India (UTC+05:30), not 11:00 pm Friday. For another, this is going to be a pain to maintain as daylight-savings cities move in and out of daylight savings time.