You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our time zone list includes "GMT", at least for creating interim meetings (likely everywhere). While pedants might applaud the distinction, it should not be an option: "UTC" should be used instead.
The list could be filtered in the form, but we should explore how we're building up the ietf.meeting.models.timezones in the top of ietf/meeting/models.py. If we can safely filter out "GMT" there, we should.
Description
Our time zone list includes "GMT", at least for creating interim meetings (likely everywhere). While pedants might applaud the distinction, it should not be an option: "UTC" should be used instead.
The list could be filtered in the form, but we should explore how we're building up the
ietf.meeting.models.timezones
in the top ofietf/meeting/models.py
. If we can safely filter out "GMT" there, we should.This is relevant to #5635 and perhaps #5683.
See also #8506, which adjusts our iCalendar renderer to handle "GMT", and #5393, which tracks refactoring how we generate iCalendar files.
Code of Conduct
The text was updated successfully, but these errors were encountered: