meeting start/end time uses UTC, not local time

[Rory McCann]

meeting start/end time uses UTC, not local time.

Some irc meetings are going to be local to the team, and only local members will be going. Hence those people will all be on one timezone. Thus there is no need for UTC. It should be possible to schedule meetings in local time.

(Some global IRC meetings (e.g. any of the ubuntu classroom stuff) should definitly by UTC, since they are targetted at everyone on the planet)

[Chris Johnston (cjohnston)]

The problem with this is that teams span over multiple time zones. This was discussed during development, and the current implementation was the decision that was reached. After the user profiles are completely implemented, it may be possible to display them in the users time zone, but currently, keeping meetings at UTC provides the easiest way to display times. On events, we have venues so the TZ is displayed based upon the venue.

[Michael Hall (mhall119)]

Proposed solution #1:

Add a ManyToMany field between Team and Timezone to let team admins pick which timezones apply to their team.

On Meeting update form, provide a drop-down for Timezone with the Team's chosen timezones at the top, followed by UTC, followed by all other timezones. This way teams with only one timezone will always have their's selected by default, teams without timezones will have UTC selected by default.

Convert time from timezone local to UTC when saving it in the database, like we currently do for Event times.

On Meeting details page, show a time listing for each of the team's selected timezones, plus UTC.

[Michael Hall (mhall119)]

Proposed solution #2:

Same as #1, except provide a ForeignKey for 'default timezone' or 'preferred timezone', leaving the ManyToMany for 'alternate timezones'.