Missing timezone in SPEC calendar might be necessary?
Please describe the bug or issue including how to reproduce it.
I noticed that https://github.com/scientific-python/scientific-python.org/commit/9087000f2b1c8bf194d82d46b7d1f820ea41572a removed the timezone information.
I'm assuming that the intended time is still the same since 9:00 LA-time (previous) would correspond to 16:00 UTC time. Only, I think the missing time zone information makes clients now interpret this as local time? At least my local Thunderbird, and the calendar overview on the website seem to show it as "4p" in my local time (Berlin).
I'm guessing that adding the correct timezone information for UTC would fix this?
Add any other context about the problem here, screenshots, etc.
Hmm, this is now a new bug that I haven't noticed yet.
I have a handful of calendar and yaml2ics PRs opened, would be nice to go through them a merge and see what else is remaining as bugs and issues.
@lagru - would you be willing to review #782? That depends on the upstream PRs, for which I also seek reviews, and then planning to cut a release, too.
Calendar bugs should be fixed now. Feel free to reopen if that is not the case.