I fully agree with Gerald – especially regarding his point that it is simpler to calculate the local meeting time based on UTC. The recent change has caused quite some confusion in the NetReady meeting schedule… Some of you have noticed. ;-)
Georg From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of morgan.richo...@orange.com Sent: Monday, December 05, 2016 10:50 AM To: Kunzmann, Gerald <kunzm...@docomolab-euro.com>; Bob Monkman <bob.monk...@arm.com>; Raymond Paik <rp...@linuxfoundation.org>; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time +1 for UTC /Morgan Le 05/12/2016 à 10:11, Kunzmann, Gerald a écrit : Hi everyone, Independent on which timezone we use, this will result in conflicts in some regions. I agree with Bob that for US/EU this would mean a shift in meeting time for months and might lead to meeting clashes with other non-OPNFV meetings. However, at the moment this problem is with Asia as they don’t have daylight saving times. So, this will mean pain for a large group of people in the one and the other case. The benefit I see for using UTC times is that it would be easier to calculate the meeting times for the individual time zones. You don’t have to worry about PST/PDT etc… Furthermore, I guess everyone knows that his timezone is UTC+X so he can easily figure out the meeting time in his zone, whereas I have to be more careful to remember what is the delta between PST/PDT and CET/CEST. If we plan to go to UTC times and adapt meeting times to daylight saving, then, which daylight saving schedule to take into account? Note that US and Europe start/end daylight saving at different weeks, which has in the past often caused some confusion for some OPNFV meetings. Best regards, Gerald From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bob Monkman Sent: Sonntag, 4. Dezember 2016 23:44 To: Raymond Paik <rp...@linuxfoundation.org><mailto:rp...@linuxfoundation.org>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time Ray, I am flexible if folks in the majority wish to switch to UTC. Like others have mentioned, all of my company meetings are pretty much set to US time. When my Armband call is set to PST, there is confusion and shift 1-3 weeks at DST times- the UTC would shift times for months and cause us to request other meetings to shift for the same period. I would prefer therefore to _not_ change. Bob From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik Sent: Friday, December 2, 2016 10:33 AM To: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time All, Another follow-up from the TSC... Over the past couple of years, we've had discussions on whether meetings like TSC or Release call times should be based on Pacific Time (as has been the tradition since OPNFV started) or if the community should move to UTC. UTC obviously has the benefit of not changing with Daylight Savings/Summer time switches twice a year in North America/Europe. When we last had the discussion, a large number of people preferred staying with Pacific Time as most of their work meetings (esp. outside of OPNFV) are based on their local timezones and not UTC. If we're to move to UTC here's how the meeting times will change for the TSC call in Pacific and Central European Timezones. Standard Time (now) * PT: 07:00 * CET: 16:00 * UTC: 15:00 * China: 23:00 Daylight Savings/Summer Time (March-November in 2017) * PT: 08:00 * CET: 17:00 * UTC: 15:00 * China: 23:00 Can you reply to the email with your comments/preference on UTC. vs Pacific Time? Thanks, Ray IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss -- Morgan Richomme Orange/ IMT/ OLN/ CNC/ NCA/ SINA Network architect for innovative services Future of the Network community member Open source Orange community manager tel. +33 (0) 296 072 106 mob. +33 (0) 637 753 326 morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
