Comment 6 for bug 610416

I think there are use cases for both local & UTC (offline vs online being a good example). However I think local is a better default.

I suggest this:
(1) Each loco team has a timezone set. Note: Timezones are not "GMT+Xhrs", but things from tzdata like "Europe/Dublin", Otherwise you won't be able to deal with summer time/daylight savings time.
(1a) What LoCo teams cover more than 1 timezone? What should we do here? Have a list of timezones for this loco team (as opposed to just one)
(2) When adding an event there's a radio button under the time that says "( ) Local time ( ) UTC", with Local time being selected by default. Changing this radio button obviously means to change the timezone of the event. Note: A LoCo might be in summer time when an event is created, but it might have changed to non-sunmner time when the event occurs, so the UTC offset might change from when the event is created and when it takes place.
(3) Events stored in the database should probably be in some timezone independent format, like UTC, but this is less important.
(4) When viewing an event, if the creator entered it in UTC, show it in UTC (with the "UTC"/"+0000" suffix), if the creator entered it in local time show it in local time.

Luckily python has decent timezone support.