El 13/05/13 15:14, Gervase Markham escribió: > 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. Uhm, probably it's a good idea to have a policy, I don't see how that can be a bad thing. For me is part of being global and inclusive with the rest of the community using a standard way to express times and facilitating the work to mozillians. > > 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. Pacific time goes out of sync also when it changes with the rest of the world, there is a 2-3 weeks gap where people outside Pacific time don't have a clue the time difference. There are a lot of countries that don't change time, and the ones than change they do in a different moment than Pacific. So it's also a problem for the rest of the world.
Using UTC is consistent during the year, 6 months a meeting will be at 16UTC and the other 6 at 17UTC. For countries that change the time, it would be at the same moment most of the year (except these 2-3 weeks I talked about). Updating UTC time twice a year it's a small work compared with the work you save to the rest of the community to track pacific time. We already know in which time zone we are, which is expressed in UTC. > >> > * 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. Explained in previous comment. Regards. -- Rubén Martín [Nukeador] Mozilla Reps Mentor http://www.mozilla-hispano.org http://twitter.com/mozilla_hispano http://facebook.com/mozillahispano
signature.asc
Description: OpenPGP digital signature
_______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
