kostika wrote:This is why I suggested just using x UK time. People know how to adjust from there.
And this is exactly why I disagree with you. It's very easy to get confused. If someone told me that something was happening at UK time, I don't always remember the offset. So, I would have to look it up. In doing so, during the summer at least, I'd have to do 2 different conversions because most of the conversion sites use GMT as their starting point.
The one redeeming fact of GMT is that it doesn't change and there are a couple of really good internet resources that will help you convert your time (regardless of which exception you are stuck with) to/from true GMT:
http://www.greenwichmeantime.com/
http://www.timezoneconverter.com/
I'm open to the idea of using the term "UTC" instead if it's common for folks in England to mis-use "GMT" during the summer. But I'm suggesting we pick something that doesn't change with the seasons because not everyone uses day light savings and some use it at the opposite time of the year (silly Aussies).
At some point,
we need someone in charge (is that Lawrence? I'm new here)
to make an executive decision and say "Thou shalt always list all events using X. You can list *additional* timezones, but you must start with X." Whatever X is, I'll live with it. But, let's get a single standard so we all know what to expect.
So, if the standard is GMT, then it's OK to list the start time for UK Time, EST and Melbourne time as long as the first thing in your announcement is GMT. If the standard is UK time, that's fine too (although I'd prefer GMT), but can we please get a standard from the moderator?
Please?
Back on topic: Saiwin, I shall endeavour to be online on time to be able to lend my healing skills to your trek (at least through the first couple of legs).