-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/14/2012 08:07 AM, Steve Gordon wrote: > > > ----- Original Message ----- >> From: "Karsten 'quaid' Wade" <[email protected]> > > A. Follow UTC and let people deal with local DST changes. > >> +1 to this. My main reason is we have two major groups of >> contributors in the US and in Israel, and their DST changes >> occur at different times, so I think pinning to UTC is the 'least >> bad' option.
Would we make the same choice if there were a more even spread of contributors around the globe? </devil's advocate> I think yes, since that could be a 'most good' option. In addition, if the meeting moves compared to UTC, that is really moving a meeting time, which is a good way to stab people for attending on time-but-whoops-not-in-your-timezone. I suppose all solutions have the same overhead of reminding people about the affect if they have follow DST. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPYPDS2ZIOBq0ODEERAjhvAKDMk4znMb1pmL2BXuOwQW1l25q+5gCeLxR9 +3uXbvDy/XYm+z7CNW66cr4= =TMVO -----END PGP SIGNATURE----- _______________________________________________ Arch mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/arch
