Meeting times are off due to daylight savings

[rossbar]

Please describe the bug or issue including how to reproduce it.

I'm not sure exactly which meetings are affected, but at least the NumPy community + triage meetings and the NetworkX community meeting are now 1 hr off after the time change. This is likely due to the fact that the meetings times are specified in UTC (+00:00 offset). I'm not sure what the appropriate syntax is for properly handling timezones.

Add any other context about the problem here, screenshots, etc.

No response

[stefanv]

Depends on whether you consider that a bug or a feature. It's correctly keeping the time according to UTC. If you want to provide it in Californian time, you have to set timezone to US/Pacific.

[rossbar]

IIRC there was an external (non-tz-related) reason why we specified them in UTC... maybe the calendar widget wasn't working with timezones? I'm not exactly sure, but I expect that the meeting times for some communities may need to be reviewed to ensure they're correct.

[tacaswell]

The calendar widget needs some sort of indicator (or selector!) for what timezone the times shown are in. It is easy to assume that it is "smart" enough to sort out the readers local timezone and grow confused .....

[tacaswell]

Actually, I take that back it looks like it should be picking up the "local" timezone, but at least for Matplotlib something is wrong with how the timezone is being read...

[stefanv]

@tacaswell Is the widget rendering your meetings differently from, say, Google Calendar then?

[QuLogic]

For some clarity, here is the monthly view:

There appear to be some times on there, but they are somewhat cut off.

And here is the list:

Matplotlib is at 9:00pm on that list. Assuming that's UTC (because it's definitely nowhere near local time for me), that's 16:00EST for me. In Google calendar, it appears at 15:00EST:

[kolibril13]

I also find the calendar quite confusing.
Maybe there can be a note saying what time zone is used?
E.g. a note stating "all times are in the time zone from your current computer time zone setting" (if that's the actual case.)

Also, I've noted that the Matplotlib community call times are one hour off: