Meeting times and DST

[Simon Grinberg]

----- Original Message -----
> From: "Steve Gordon" <sgordon at redhat.com>
> To: "Karsten 'quaid' Wade" <kwade at redhat.com>
> Cc: "arch" <arch at ovirt.org>
> Sent: Wednesday, March 14, 2012 5:07:20 PM
> Subject: Re: Meeting times and DST
> 
> 
> 
> ----- Original Message -----
> > From: "Karsten 'quaid' Wade" <kwade at redhat.com>
> > To: "<arch at ovirt.org>" <arch at ovirt.org>
> > Sent: Wednesday, March 14, 2012 11:03:53 AM
> > Subject: Meeting times and DST
> > 
> > -----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.
> 
> +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.
> 
> Steve
> 
> > B. Follow DST by keeping the time the same within one particular
> > country.
> > C. If yes to B., which country do we peg to?

We are used to be outnumbered in most of the calls thus US wins. We usually pin all multi party meetings to US ET.

IF we start pinning to UTC then it will cause conflicts with other meetings scheduled by US people as some will shift and some will not. Pinning to US ET guaranties that at least everything shifts together.  


> > 
> > - - 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
> > Arch at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/arch
> > 
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
>