The OpenChain Korea Work Group holds its next meeting on the 16th of March at 14:00 Korea Standard Time (05:00 UTC). Check out the agenda and the dial-in details at the link

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

As many of you know, we have been covering more security issues here in OpenChain in recent times. This is largely due to demand by our audience. During our last security webinar it was flagged that

Dear all, "a) UTC only" is simple :) Best, Tak --- Takashi NINJOUJI Chief Specialist Advanced Collaborative Software Development and Technology Department Corporate Software Engineering &

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

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

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

Dear all, Option a) is fine for me Ciao Oliver

+1 Best, Keiichi Seki

For me having a push model where a calendar invite attachment is emailed, does all the work and is ideal. Thanks, Dave

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

+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@...

Dear all, 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

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

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 +

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,

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

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*

Hi Shane, How about using the following service together? https://www.worldtimebuddy.com/ Best, -- kobota

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