25 ms·
It’s an awkward situation for sure and the timezone could have been clearer. But I also feel like if there’s no timezone for a deadline then you should assume
by sevg 2y ago
It’s an awkward situation for sure and the timezone could have been clearer.
But I also feel like if there’s no timezone for a deadline then you should assume the worst case (which here would be UTC) and make sure you submit before?
The author left it so late that in 95% of the world it was no longer the 17th Feb.
- orra 2y agoAh but UTC isn't the worst case: it's UTC+14. I agree with the author: the timezone of the organisation is what I'd expect.
- sevg 2y ago> Ah but UTC isn't the worst case: it's UTC+14. The worst _reasonable_ case is UTC. Nobody is thinking UTC+14. > I agree with the author: the timezone of the organisation is what I'd expect. If the job was a local office job, I’d expect a local time zone. But the board of directors isn’t restricted to California or even the USA.
- maxboone 2y agoAOE times are pretty common in academic and CS circles, it is the standard for IEEE 802: https://www.ieee802.org/16/aoe.html https://www.ieee802.org/16/aoe.html
- sevg 2y agoThe OSI post that the author links to specifies the voting deadline in GMT (effectively UTC) in the sentence immediately preceding the timeline diagram. So it can be reasonably inferred that they’re generally using GMT/UTC in the rest of their timeline, rather than AOE, UTC+14 or anything else out of the ordinary.