By posting this here, are you saying that Mozilla should have an official policy (as opposed to, say, a best practices recommendation) on the right way to do meeting announcements? If so, I'm not sure I agree with that.
However, if we are going to have such a policy, I have a counter-proposal. * Every meeting should have a time which is fixed in a particular timezone, or in UTC. How it is fixed is at the discretion of the organizer, but Pacific Time is recommended, to avoid twice-yearly clashes as one lot of meetings move and another lot don't. * Meeting announcements should specify the time in that timezone, and only that timezone. * Meeting announcements must also contain a link to timeanddate.com which decodes that time into a time in the user's local timezone, so everyone can easily find out what time it is for them. Why? * If you put multiple times in an announcement, they will get out of sync when there's a DST change somewhere. From long experience, I know this happens. Particularly unintuitive is the fact that if a meeting is fixed in (e.g.) Pacific Time, when there's a DST change in that region and everyone changes their clocks, you need to update the meeting announcement to alter the _UTC_ time. > * We'll avoid problems when time changes due daily saving, UTC is > UTC all the year. Only if all the meetings are _fixed_ in UTC time, which would be a big change for Mozilla. > Clarification: Scheduled (recurrent) meetings can be at the same local > time during the year if needed (e.g Monday meeting), it's just a matter > of remembering that UTC time will change once a year. Twice a year. Gerv _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
