A coworker asked me about time-zone today:
Subject: Our special time zone: Jerusalem 2005
This is causing problems.
When I invite someone from a different office to a meeting, he receives the meeting time one hour earlier than what I write.
And my answer to that:
That’s not because of our unique timezone. The only thing ‘unique’ about it is that it will switch back to non-daylight saving automatically.
There are two ways to deal with DST in Israel.
- Shift your clock one hour forward.
Advantage: All future and past metings are aligned correctly.
Disadvantage: You’re not working with UTC, so you can’t sync with NTP anymore.
- Change your timezone.
Avantage:That’s the way to do it. The entire world does it and it works well, except for Israel. It keeps you on UTC, so you can send meetings to the rest of the world and they’ll be okay. Disadvantage: in Israel specifically, the dates for the time-zone change change every year, so you need to readjust it manually, hence the creation of our Jerusalem 2005 timezone.
What you are encountering is a case when you send an invite from a computer with a correct UTC (yours) to a computer with a shifted UTC (for instance Cellcom). Appointment setting is always done in UTC (so you can set up international appointments) but the other system’s UTC is different than yours, so it sets a different time. It is inevitable.
If we would have switched to a shifted-UTC scheme (which is, IMO, a bad thing) the particular company you’re working with will be okay, but companies that work with the time-zone method will get the appointment an hour early. It’s a bloody mess.
I hope this clears things up.