Comment 17 for bug 610416

I actually just ran into this when I was adding an event. It was a little confusing because it said local time but on the events listing it says "UTC."

I think we should allow someone to pick what timezone the event is. We could prepick it maybe? like Darcy suggested but still allow it to be picked. After user picks the timezone and date/time, we could display the converted UTC via Javascript (or such). Or a preview type deal that will show what it will look like once saved.

That might exist already in that django timezone code. I am new to python and django :)

Timezone: [Dropdown of GMT/UTC like launchpad's timezone picker]
Begins: [ Calendar bit you have ] [ time ] (_what this is in UTC_)
Ends: [ Calendar bit you have ] [ time ] (_what this is in UTC_)

Then store them all UTC in the DB.

________Example________

Timezone: dropdown: value=GMT-5? US - Virginia *
Begins: 2010-10-20 16:00 EDT (2010-10-20 20:00 UTC) **
Ends: 2010-10-20 17:00 EDT (2010-10-20 21:00 UTC) **

* I picked GMT because that's what I'm familiar with but if we show the option's text that's understandable to the user like "US - Virginia" then it doesn't matter what the value is. Launchpad has that very understandable and we've used it to get to the loco.ubuntu.com so I'd stick with that :)

** Done via another dateformat on same value from db

On the events listing page maybe we can have "view in [timezone]". If we want to get really fancy, we could use the timezone from launchpad. :)