main@lists.openchainproject.org | Timezone management for our community

Home Messages Hashtags Subgroups

Date Date 1 - 18 of 18

Timezone management for our community

Shane Coughlan #4491 Dear all We have a community spanning three continents and a constant stream of meetings. To manage this we usually publish meeting times in Pacific Standard Time (PST), Universal Time Coordinated (UTC), Central European Time (CET), India Standard Time (IST), China Standard Time (CST), Korea Standard Time (KST) and Japan Standard Time (JST). However, an area of potential confusion has been flagged. The United States has a seasonal timezone called Central Summer Time, and they frequently use the abbreviation (CST), a direct overlap with China Standard Time. How would you like to see us resolve this to reduce the potential for confusion? Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan
More All Messages By This Member
Norio Kobota #4492 Hi Shane, How about using the following service together? https://www.worldtimebuddy.com/ Best, -- kobota toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Shane Coughlan Sent: Wednesday, March 9, 2022 12:48 PM To: OpenChain Main <main@...> Subject: [openchain] Timezone management for our community Dear all We have a community spanning three continents and a constant stream of meetings. To manage this we usually publish meeting times in Pacific Standard Time (PST), Universal Time Coordinated (UTC), Central European Time (CET), India Standard Time (IST), China Standard Time (CST), Korea Standard Time (KST) and Japan Standard Time (JST). However, an area of potential confusion has been flagged. The United States has a seasonal timezone called Central Summer Time, and they frequently use the abbreviation (CST), a direct overlap with China Standard Time. How would you like to see us resolve this to reduce the potential for confusion? Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://urldefense.com/v3/__https://meetings.hubspot.com/scoughlan__;! !JmoZiZGBv3RvKRSx!pe_a4Ojni5VrqcD2wb7jW6N4xnwy6NOiOHYwGiZYUleA -i_AfQ8LVXN3HXnSZ_Iv$ [meetings[.]hubspot[.]com]
More All Messages By This Member
Shane Coughlan #4493 It’s a great idea (and I use this service all the time on my phone), but some people wanted timezone information inside emails. So we used the current format… 🤷 In Europe we often only provide UTC and a link to something like Timebuddy. However, we tried and had questions from people about what that meant in their timezone. 🤦‍♂️ I see three possible solutions right now: 1) we do not change anything 2) we only provide UTC and a link to Timebuddy 3) we name the country of the timezone The last one would seem to solve all problems but it would make email subjects incredibly long. Example: OpenChain Regular Webinar: GPLv3 - 06:00 United States Pacific, 14:00 UTC, 15:00 Belgium, 19:30 Mumbai, 22:00 China, 23:00 Korea and Japan Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan toggle quoted message Show quoted text On Mar 9, 2022, at 12:55, Norio Kobota <norio.kobota@...> wrote: Hi Shane, How about using the following service together? https://www.worldtimebuddy.com/ Best, -- kobota -----Original Message----- From: main@... <main@...> On Behalf Of Shane Coughlan Sent: Wednesday, March 9, 2022 12:48 PM To: OpenChain Main <main@...> Subject: [openchain] Timezone management for our community Dear all We have a community spanning three continents and a constant stream of meetings. To manage this we usually publish meeting times in Pacific Standard Time (PST), Universal Time Coordinated (UTC), Central European Time (CET), India Standard Time (IST), China Standard Time (CST), Korea Standard Time (KST) and Japan Standard Time (JST). However, an area of potential confusion has been flagged. The United States has a seasonal timezone called Central Summer Time, and they frequently use the abbreviation (CST), a direct overlap with China Standard Time. How would you like to see us resolve this to reduce the potential for confusion? Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://urldefense.com/v3/__https://meetings.hubspot.com/scoughlan__;! !JmoZiZGBv3RvKRSx!pe_a4Ojni5VrqcD2wb7jW6N4xnwy6NOiOHYwGiZYUleA -i_AfQ8LVXN3HXnSZ_Iv$ [meetings[.]hubspot[.]com]
More All Messages By This Member
Martin Bührlen #4494 Dear all, I support the idea, I also had a time zone confusion once. there is another service, which I have used, which allows the selection of even more time zones than TimeBuddy (other than that it is very similar): https://www.timeanddate.com/worldclock/meeting.html One additional option is to have the time zone correctly specified in the iCal attachment, which allows us to add it to our calendars in an automatic way. kind regards Martin --- Martin Bührlen Am 09.03.2022 um 05:11 schrieb Shane Coughlan: toggle quoted message Show quoted text It’s a great idea (and I use this service all the time on my phone), but some people wanted timezone information inside emails. So we used the current format… 🤷 In Europe we often only provide UTC and a link to something like Timebuddy. However, we tried and had questions from people about what that meant in their timezone. 🤦‍♂️ I see three possible solutions right now: 1) we do not change anything 2) we only provide UTC and a link to Timebuddy 3) we name the country of the timezone The last one would seem to solve all problems but it would make email subjects incredibly long. Example: OpenChain Regular Webinar: GPLv3 - 06:00 United States Pacific, 14:00 UTC, 15:00 Belgium, 19:30 Mumbai, 22:00 China, 23:00 Korea and Japan Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan On Mar 9, 2022, at 12:55, Norio Kobota <norio.kobota@...> wrote: Hi Shane, How about using the following service together? https://www.worldtimebuddy.com/ Best, -- kobota -----Original Message----- From: main@... <main@...> On Behalf Of Shane Coughlan Sent: Wednesday, March 9, 2022 12:48 PM To: OpenChain Main <main@...> Subject: [openchain] Timezone management for our community Dear all We have a community spanning three continents and a constant stream of meetings. To manage this we usually publish meeting times in Pacific Standard Time (PST), Universal Time Coordinated (UTC), Central European Time (CET), India Standard Time (IST), China Standard Time (CST), Korea Standard Time (KST) and Japan Standard Time (JST). However, an area of potential confusion has been flagged. The United States has a seasonal timezone called Central Summer Time, and they frequently use the abbreviation (CST), a direct overlap with China Standard Time. How would you like to see us resolve this to reduce the potential for confusion? Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://urldefense.com/v3/__https://meetings.hubspot.com/scoughlan__;! !JmoZiZGBv3RvKRSx!pe_a4Ojni5VrqcD2wb7jW6N4xnwy6NOiOHYwGiZYUleA -i_AfQ8LVXN3HXnSZ_Iv$ [meetings[.]hubspot[.]com]
More All Messages By This Member
Steve Kilbane #4495 Perhaps use the current approach, but include a key of timezone names (or a link to one) further down the email as a standard footer, e.g.: OpenChain Regular Webinar: GPLv3 - 06:00 PST, 14:00 UTC, 15:00 CET, 19:30 IST, 22:00 CST, 23:00 KST and JST [...] Timezone abbreviations: PST United States Pacific UTC-08:00 UTC Coordinated Universal Time UTC CET Central European Time UTC+01:00 IST India Standard Time UTC+05:30 CST China Standard Time UTC+08:00 KST Korea Standard Time UTC+09:00 JST Japan Standard Time UTC+09:00 steve toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Shane Coughlan Sent: 09 March 2022 04:11 To: main@... Subject: Re: [openchain] Timezone management for our community [External] It’s a great idea (and I use this service all the time on my phone), but some people wanted timezone information inside emails. So we used the current format… 🤷 In Europe we often only provide UTC and a link to something like Timebuddy. However, we tried and had questions from people about what that meant in their timezone. 🤦‍♂️ I see three possible solutions right now: 1) we do not change anything 2) we only provide UTC and a link to Timebuddy 3) we name the country of the timezone The last one would seem to solve all problems but it would make email subjects incredibly long. Example: OpenChain Regular Webinar: GPLv3 - 06:00 United States Pacific, 14:00 UTC, 15:00 Belgium, 19:30 Mumbai, 22:00 China, 23:00 Korea and Japan Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://urldefense.com/v3/__https://meetings.hubspot.com/scoughlan__;!!A3Ni8CS0y2Y!ovCVonBz5czmF0pJw4JrDbxgw4DcmrwWFQ_S2PElAqnP18hC0UgpzIoltp25UEeBo2L9$ On Mar 9, 2022, at 12:55, Norio Kobota <norio.kobota@...> wrote: Hi Shane, How about using the following service together? https://urldefense.com/v3/__https://www.worldtimebuddy.com/__;!!A3Ni8C S0y2Y!ovCVonBz5czmF0pJw4JrDbxgw4DcmrwWFQ_S2PElAqnP18hC0UgpzIoltp25UPpw 9cZ1$ Best, -- kobota -----Original Message----- From: main@... <main@...> On Behalf Of Shane Coughlan Sent: Wednesday, March 9, 2022 12:48 PM To: OpenChain Main <main@...> Subject: [openchain] Timezone management for our community Dear all We have a community spanning three continents and a constant stream of meetings. To manage this we usually publish meeting times in Pacific Standard Time (PST), Universal Time Coordinated (UTC), Central European Time (CET), India Standard Time (IST), China Standard Time (CST), Korea Standard Time (KST) and Japan Standard Time (JST). However, an area of potential confusion has been flagged. The United States has a seasonal timezone called Central Summer Time, and they frequently use the abbreviation (CST), a direct overlap with China Standard Time. How would you like to see us resolve this to reduce the potential for confusion? Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://urldefense.com/v3/__https://meetings.hubspot.com/scoughlan__;! !JmoZiZGBv3RvKRSx!pe_a4Ojni5VrqcD2wb7jW6N4xnwy6NOiOHYwGiZYUleA -i_AfQ8LVXN3HXnSZ_Iv$ [meetings[.]hubspot[.]com]
More All Messages By This Member
Carlo "Kappa" Piana #4496 Shane, all, Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Therefore, the best way is to announce UTC only, unless the event is mainly for those in one or two timezones. You also avoid the usual madness of DST switching in different days even in the same timezone and in different ways north/south (se Japan/Australia, eg). And please, PLEASE!, never in am-pm. Day is of 24 hours. See above, case b, what happens if you do am-pm. So my suggestion is to have always UTC in the object line and complement that with a bunch of courtesy translation in some populuar timezones. I had even made a script that does the same thing as Worldtimebuddy or Timeandate. Cheers Carlo ----- Messaggio originale ----- toggle quoted message Show quoted text Da: "Shane Coughlan" <scoughlan@...> A: "main@..." <main@...> Inviato: Mercoledì, 9 marzo 2022 5:11:18 Oggetto: Re: [openchain] Timezone management for our community It’s a great idea (and I use this service all the time on my phone), but some people wanted timezone information inside emails. So we used the current format… 🤷 In Europe we often only provide UTC and a link to something like Timebuddy. However, we tried and had questions from people about what that meant in their timezone. 🤦‍♂️ I see three possible solutions right now: 1) we do not change anything 2) we only provide UTC and a link to Timebuddy 3) we name the country of the timezone The last one would seem to solve all problems but it would make email subjects incredibly long. Example: OpenChain Regular Webinar: GPLv3 - 06:00 United States Pacific, 14:00 UTC, 15:00 Belgium, 19:30 Mumbai, 22:00 China, 23:00 Korea and Japan Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan On Mar 9, 2022, at 12:55, Norio Kobota <norio.kobota@...> wrote: Hi Shane, How about using the following service together? https://www.worldtimebuddy.com/ Best, -- kobota -----Original Message----- From: main@... <main@...> On Behalf Of Shane Coughlan Sent: Wednesday, March 9, 2022 12:48 PM To: OpenChain Main <main@...> Subject: [openchain] Timezone management for our community Dear all We have a community spanning three continents and a constant stream of meetings. To manage this we usually publish meeting times in Pacific Standard Time (PST), Universal Time Coordinated (UTC), Central European Time (CET), India Standard Time (IST), China Standard Time (CST), Korea Standard Time (KST) and Japan Standard Time (JST). However, an area of potential confusion has been flagged. The United States has a seasonal timezone called Central Summer Time, and they frequently use the abbreviation (CST), a direct overlap with China Standard Time. How would you like to see us resolve this to reduce the potential for confusion? Regards Shane Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://urldefense.com/v3/__https://meetings.hubspot.com/scoughlan__;! !JmoZiZGBv3RvKRSx!pe_a4Ojni5VrqcD2wb7jW6N4xnwy6NOiOHYwGiZYUleA -i_AfQ8LVXN3HXnSZ_Iv$ [meetings[.]hubspot[.]com]
More All Messages By This Member
Matija Šuklje #4497 Die 9. 03. 22 et hora 10:11 scripsisti: > > Technically, there are two correct ways to announce times: +1 to everything Carlo wrote. In the increasingly digital and global world people simply need to get used to UTC. cheers, Matija -- gsm: tel:+386.41.849.552 www: https://matija.suklje.name xmpp: matija.suklje@... matrix: @silverhook:matrix.org
More All Messages By This Member
Sebastian Crane #4498 Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian
More All Messages By This Member
Jan Thielscher #4499 +1 from GER 😉 Von: main@... <main@...> im Auftrag von Sebastian Crane via lists.openchainproject.org <seabass-labrax=gmx.com@...> Datum: Mittwoch, 9. März 2022 um 17:58 An: main@... <main@...> Betreff: Re: [openchain] Timezone management for our community Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: > Technically, there are two correct ways to announce times: > > a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 > > b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian
More All Messages By This Member
Christopher Wood #4500 All I concur with option a) as well. I can deal with the math needed for “UTC only” during Standard Time and Daylight Savings time here in the United Stares. Regards Dr Wood toggle quoted message Show quoted text On Mar 9, 2022, at 10:58 AM, Sebastian Crane <seabass-labrax@...> wrote: Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian
More All Messages By This Member
Dave Marr #4501 For me having a push model where a calendar invite attachment is emailed, does all the work and is ideal. Thanks, Dave toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Christopher Wood Sent: Wednesday, March 9, 2022 10:17 AM To: main@... Subject: Re: [openchain] Timezone management for our community WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. All I concur with option a) as well. I can deal with the math needed for “UTC only” during Standard Time and Daylight Savings time here in the United Stares. Regards Dr Wood On Mar 9, 2022, at 10:58 AM, Sebastian Crane <seabass-labrax@...> wrote: Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian
More All Messages By This Member
Keiichi Seki #4502 +1 Best, Keiichi Seki toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Dave Marr Sent: Thursday, March 10, 2022 9:11 AM To: main@... Subject: Re: [openchain] Timezone management for our community For me having a push model where a calendar invite attachment is emailed, does all the work and is ideal. Thanks, Dave -----Original Message----- From: main@... <main@...> On Behalf Of Christopher Wood Sent: Wednesday, March 9, 2022 10:17 AM To: main@... Subject: Re: [openchain] Timezone management for our community WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. All I concur with option a) as well. I can deal with the math needed for “UTC only” during Standard Time and Daylight Savings time here in the United Stares. Regards Dr Wood On Mar 9, 2022, at 10:58 AM, Sebastian Crane <seabass-labrax@...> wrote: Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian smime.p7s
More All Messages By This Member
Oliver Fendt #4503 Dear all, Option a) is fine for me Ciao Oliver toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Sebastian Crane via lists.openchainproject.org Sent: Mittwoch, 9. März 2022 17:58 To: main@... Subject: Re: [openchain] Timezone management for our community Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian
More All Messages By This Member
james cloos #4504 "SC" == Shane Coughlan <scoughlan@...> writes: SC> However, an area of potential confusion has been flagged. The United SC> States has a seasonal timezone called Central Summer Time, and they SC> frequently use the abbreviation (CST), a direct overlap with China SC> Standard Time. CST is Central Standard Time, not summer. For reference, Chicago is about to switch this Sunday (20220313) from CST to CDT, since daylight savings time starts that day. -JimC -- James Cloos <cloos@...> OpenPGP: 0x997A9F17ED7DAEA6
More All Messages By This Member
Sami Atabani #4505 I agree with this but if there is a change to the meeting time as a result of rescheduling and a new attachment is sent very often you end up with two meetings as a result. Perhaps one option is to ensure that if there is a change of meeting time a cancellation is sent and a new meeting is setup instead to ensure duplication of entries. Thanks Sami toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Dave Marr via lists.openchainproject.org Sent: 10 March 2022 00:11 To: main@... Subject: Re: [openchain] Timezone management for our community For me having a push model where a calendar invite attachment is emailed, does all the work and is ideal. Thanks, Dave -----Original Message----- From: main@... <main@...> On Behalf Of Christopher Wood Sent: Wednesday, March 9, 2022 10:17 AM To: main@... Subject: Re: [openchain] Timezone management for our community WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. All I concur with option a) as well. I can deal with the math needed for “UTC only” during Standard Time and Daylight Savings time here in the United Stares. Regards Dr Wood On Mar 9, 2022, at 10:58 AM, Sebastian Crane <seabass-labrax@...> wrote: Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian 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.
More All Messages By This Member
Carlo "Kappa" Piana #4506 Indeed, this is true, Sami. Not sure why, but happened to me too, or even worse, one date with the old link to the call. To his credit, this is what Shane has done at the turn of the year, and it worked, I reckon. K ----- Messaggio originale ----- toggle quoted message Show quoted text Da: "Sami Atabani" <Sami.atabani@...> A: "main@..." <main@...> Inviato: Giovedì, 10 marzo 2022 10:36:47 Oggetto: Re: [openchain] Timezone management for our community I agree with this but if there is a change to the meeting time as a result of rescheduling and a new attachment is sent very often you end up with two meetings as a result. Perhaps one option is to ensure that if there is a change of meeting time a cancellation is sent and a new meeting is setup instead to ensure duplication of entries. Thanks Sami -----Original Message----- From: main@... <main@...> On Behalf Of Dave Marr via lists.openchainproject.org Sent: 10 March 2022 00:11 To: main@... Subject: Re: [openchain] Timezone management for our community For me having a push model where a calendar invite attachment is emailed, does all the work and is ideal. Thanks, Dave -----Original Message----- From: main@... <main@...> On Behalf Of Christopher Wood Sent: Wednesday, March 9, 2022 10:17 AM To: main@... Subject: Re: [openchain] Timezone management for our community WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. All I concur with option a) as well. I can deal with the math needed for “UTC only” during Standard Time and Daylight Savings time here in the United Stares. Regards Dr Wood On Mar 9, 2022, at 10:58 AM, Sebastian Crane <seabass-labrax@...> wrote: Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian 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.
More All Messages By This Member
Takashi NINJOUJI #4507 Dear all, "a) UTC only" is simple :) Best, Tak --- Takashi NINJOUJI Chief Specialist Advanced Collaborative Software Development and Technology Department Corporate Software Engineering & Technology Center Toshiba Corporation 1 Komukai-toshiba-cho, Saiwai-ku Kawasaki-shi, Kanagawa 212-8582, Japan email: takashi1.ninjouji@... www: http://www.toshiba.co.jp/worldwide/ 差出人: main@... <main@...> が Oliver Fendt <oliver.fendt@...> の代理で送信送信日時: 2022年3月10日 16:38 宛先: main@... <main@...> 件名: Re: [openchain] Timezone management for our community Dear all, Option a) is fine for me Ciao Oliver toggle quoted message Show quoted text -----Original Message----- From: main@... <main@...> On Behalf Of Sebastian Crane via lists.openchainproject.org Sent: Mittwoch, 9. März 2022 17:58 To: main@... Subject: Re: [openchain] Timezone management for our community Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: > Technically, there are two correct ways to announce times: > > a) UTC only. Everybody should know in which timezone they are, do the > math: 12:00 UTC - You are in UTC +1 -> 13:00 > > b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian
More All Messages By This Member
Shane Coughlan #4509 Hi everyone! Thanks for the great feedback. Consolidating it all, we will: (1) Use UTC alone in email subject lines (2) Have a push model to send calendar reminders a week ahead and a day ahead of each event (3) And include a map inside each email like this with an additional link to TimeBuddy: Timezone abbreviations: PST United States Pacific UTC-08:00 UTC Coordinated Universal Time UTC CET Central European Time UTC+01:00 IST India Standard Time UTC+05:30 CST China Standard Time UTC+08:00 KST Korea Standard Time UTC+09:00 JST Japan Standard Time UTC+09:00 Check your timezone: https://www.worldtimebuddy.com toggle quoted message Show quoted text On Mar 10, 2022, at 18:40, Carlo Piana <carlo@...> wrote: Indeed, this is true, Sami. Not sure why, but happened to me too, or even worse, one date with the old link to the call. To his credit, this is what Shane has done at the turn of the year, and it worked, I reckon. K ----- Messaggio originale ----- Da: "Sami Atabani" <Sami.atabani@...> A: "main@..." <main@...> Inviato: Giovedì, 10 marzo 2022 10:36:47 Oggetto: Re: [openchain] Timezone management for our community I agree with this but if there is a change to the meeting time as a result of rescheduling and a new attachment is sent very often you end up with two meetings as a result. Perhaps one option is to ensure that if there is a change of meeting time a cancellation is sent and a new meeting is setup instead to ensure duplication of entries. Thanks Sami -----Original Message----- From: main@... <main@...> On Behalf Of Dave Marr via lists.openchainproject.org Sent: 10 March 2022 00:11 To: main@... Subject: Re: [openchain] Timezone management for our community For me having a push model where a calendar invite attachment is emailed, does all the work and is ideal. Thanks, Dave -----Original Message----- From: main@... <main@...> On Behalf Of Christopher Wood Sent: Wednesday, March 9, 2022 10:17 AM To: main@... Subject: Re: [openchain] Timezone management for our community WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. All I concur with option a) as well. I can deal with the math needed for “UTC only” during Standard Time and Daylight Savings time here in the United Stares. Regards Dr Wood On Mar 9, 2022, at 10:58 AM, Sebastian Crane <seabass-labrax@...> wrote: Dear all, On Wed, Mar 09, 2022 at 10:11:19AM +0100, Carlo Piana wrote: Technically, there are two correct ways to announce times: a) UTC only. Everybody should know in which timezone they are, do the math: 12:00 UTC - You are in UTC +1 -> 13:00 b) UTC + timeshift. Same as above, but a bit more complicated, one should do more math: 12:00 UTC-7 - I am at UTC+1 = +8 hours = 20:00. Yes please for option A! I'm in Britain, so UTC is particularly convenient, but I prefer it even when Britain is observing Summer Time. Best wishes, Sebastian 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.
More All Messages By This Member

1 - 18 of 18

Previous Topic Next Topic

Home Hashtags Subgroups Terms