Proposed solution #2: Same as #1, except provide a ForeignKey for 'default timezone' or 'preferred timezone', leaving the ManyToMany for 'alternate timezones'.
-- You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. https://bugs.launchpad.net/bugs/711754 Title: meeting start/end time uses UTC, not local time Status in LoCo Directory: Invalid Bug description: 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) _______________________________________________ Mailing list: https://launchpad.net/~loco-directory-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~loco-directory-dev More help : https://help.launchpad.net/ListHelp
