-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a regular problem in global open source projects - what to do when people start rolling in to daylight savings time (DST). This last weekend was the rollover here in the US.
A DST change means some people in the project are going to have their meeting change relative to their local clock. Some projects choose to keep the meeting at the same local time relative to one area's DST settings. For example, when a project is largely US-based developers, the meeting tends to stay the same time on the local clock and change twice a year for those using UTC. Some projects choose to peg their meeting time to UTC always, so that never changes. The each group in a country need to deal with changing the meeting on their local clock. Honestly, there are problems with any of these methods - people are inconvenienced, usually someone can't make the adjusted meeting time, etc. So we could just pick our preference as a project, post it on our meetings page, and try to remember when DST starts/stops so we remind people of that change: A. Follow UTC and let people deal with local DST changes. B. Follow DST by keeping the time the same within one particular country. C. If yes to B., which country do we peg to? - - 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/ iD8DBQFPYLNZ2ZIOBq0ODEERAqX/AJsE56MxRLT/UmmXg6fXaSxQ8atscgCgpPFT s5LQBchDs52t87M8SXW29LA= =0NBk -----END PGP SIGNATURE----- _______________________________________________ Arch mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/arch
