The bot supports time references with time zone abbreviations, e.g. 5am in CST.
However, as noted in timezone_abbreviations.md, time zone abbreviations (1) are not standardized and (2) can be ambiguous.
For example, there are five different interpretations of CST:
Central Standard Time (North America)
Central Standard Time (Australia)
Central Summer Time (Australia)
China Standard Time
Cuba Standard Time
Nevertheless, we decided to use a subset of commonly used abbreviations.
However, we should bear in mind that the user might say "CST" but mean "China Standard Time".
Since time zone abbreviations can me ambiguous, and we internally made the decision that "CST" is interpreted as "Central Standard Time (North America)", it's important that the ephemeral message makes this explicit.
So, when the sender uses a time zone abbreviation (e.g. "5am CST"), I propose we change the left-hand side of ephemeral message from this:
"5am CST", 15 February 2023
To this:
"5am CST", 15 February 2023, Central Standard Time (North America) (UTC-06:00)
Acceptance criteria
When the sender uses a time zone abbreviation, the ephemeral message explicitly states which offset was actually used for the conversion.
Clarification and motivation
NOTE: THIS ISSUE IS BLOCKED BY #57
The bot supports time references with time zone abbreviations, e.g.
5am in CST.However, as noted in
timezone_abbreviations.md, time zone abbreviations (1) are not standardized and (2) can be ambiguous.Nevertheless, we decided to use a subset of commonly used abbreviations.
However, we should bear in mind that the user might say "CST" but mean "China Standard Time".
Since time zone abbreviations can me ambiguous, and we internally made the decision that "CST" is interpreted as "Central Standard Time (North America)", it's important that the ephemeral message makes this explicit.
So, when the sender uses a time zone abbreviation (e.g. "5am CST"), I propose we change the left-hand side of ephemeral message from this:
To this:
Acceptance criteria