Date   

OpenChain Call - Draft Security Specification - 06:00 UTC today

 

Our focus will be on finalizing the OpenChain Draft Security Specification:
https://1drv.ms/w/s!AsXJVqby5kpnkTt03Samssy2NYbf

We start at 06:00 UTC. Your contributions are very welcome.

Check your timezone:
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

Compare timezones:
https://www.worldtimebuddy.com

Shane Coughlan
OpenChain General Manager
+818040358083
Book a meeting:
https://meetings.hubspot.com/scoughlan


OpenChain Security, Security, Security

 

OpenChain has been leaning heavily into security recently due market conditions and demand.

You can catch up with two of our recent key events below:

OpenChain Webinar #38 – Security Today
https://www.openchainproject.org/featured/2022/03/11/webinar-38

OpenChain Bi-Weekly Global Call – 2022-02-28 – Reference Security Standard Focus
https://www.openchainproject.org/news/2022/03/07/global-call-2022-02-28

What you need to know:

In August 2021 we released a security reference guide:
https://www.openchainproject.org/security-guide

It is maturing into a reference security standard:
https://github.com/OpenChain-Project/SecurityAssuranceGuide/tree/main/Guide/2.0

We are editing this live and accepting comments:
https://1drv.ms/w/s!AsXJVqby5kpnkTt03Samssy2NYbf

Our next bi-weekly call will close off the main items on this document prior to initial release.


Invitation: OpenChain IP Summit 2022 @ 14:00 UTC 2022-03-17 @ Thu Mar 17 23:00 - Fri Mar 18, 2022 01:00 (JST) (main@lists.openchainproject.org)

 

You have been invited to the following event.

OpenChain IP Summit 2022 @ 14:00 UTC 2022-03-17

When
Thu Mar 17 23:00 – Fri Mar 18, 2022 01:00 Japan Standard Time
Calendar
main@...
Who
scoughlan@... - creator
OpenChain Germany
OpenChain India
OpenChain Japan
OpenChain Korea
OpenChain Main
OpenChain Automotive
OpenChain Partners
OpenChain Taiwan
OpenChain Telco Work Group
OpenChain UK
This event will feature:

Shane Coughlan, OpenChain GM: Open Source Copyright in 2022

Keith Bergelt, OIN CEO: Open Source Patents in 2022

Armijn Hemel, Principle at Tjaldur Software Governance Solutions: Identifying files faster with proximity matching

+ More

Free to register, free to attend, open to all.

Sign up now:
https://zoom.us/webinar/register/WN_jsnpoPFxRq6PuvL1kqvFhw

Check your timezone:
PST - United States PacificUTC-08:00
UTC - Coordinated Universal TimeUTC
CET - Central European TimeUTC+01:00
IST - India Standard TimeUTC+05:30
CST - China Standard TimeUTC+08:00
KST - Korea Standard TimeUTC+09:00
JST - Japan Standard TimeUTC+09:00

Compare timezones:
https://www.worldtimebuddy.com

Going (main@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account main@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More.


Catch up: recent work on our new training course

 

You can check out the most recent live-edit from a recent education work group call here:
https://www.openchainproject.org/news/2022/03/09/education-work-group-2022-03-01

Balakrishna, can you share the latest editing links?


Invitation: Korea Work Group Meeting #13 @ Wed Mar 16, 2022 14:00 - 15:00 (JST) (main@lists.openchainproject.org)

 

You have been invited to the following event.

Korea Work Group Meeting #13

When
Wed Mar 16, 2022 14:00 – 15:00 Japan Standard Time
Where
https://line.zoom.us/j/98865487244?pwd=UnJFMHg2ZmIxNTAwcWtGTkRzc2tJdz09 (map)
Calendar
main@...
Who
scoughlan@... - creator
OpenChain Korea
OpenChain Main
You can join the event via LINE's Zoom room:
https://line.zoom.us/j/98865487244?pwd=UnJFMHg2ZmIxNTAwcWtGTkRzc2tJdz09

Please use this password: 160322

Check your timezone:
PSTUnited States PacificUTC-08:00
UTCCoordinated Universal TimeUTC
CETCentral European TimeUTC+01:00
ISTIndia Standard TimeUTC+05:30
CSTChina Standard TimeUTC+08:00
KSTKorea Standard TimeUTC+09:00
JSTJapan Standard TimeUTC+09:00

Compare timezones:
https://www.worldtimebuddy.com

Going (main@...)?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account main@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More.


OpenChain Korea Work Group Meeting – March 16th at 05:00 UTC

 

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 below!
https://www.openchainproject.org/featured/2022/03/10/korea-wg-meeting-2022-03-16

Check your timezone:
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

Compare timezones:
https://www.worldtimebuddy.com


Re: Timezone management for our community

 

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

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.






Open source security concern: Linux escalation issue “Dirty Pipe”

 

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 the current global environment may lead to an increase in the number and intensive of vulnerabilities discovered.

An issue has been found in the Linux kernel (and therefore many Android devices as well as servers) that allows escalation to root. This allows full control over devices. It is regarded as one of the most severe security issues around the kernel in the last half decade or so. It may be worth talking to your security teams to see how they are solving in, and with your supply chain teams to see how they are ensuring suppliers are doing the same.

Issue tag: CVE-2022-0847

Linux has been bitten by its most high-severity vulnerability in years:

https://arstechnica.com/information-technology/2022/03/linux-has-been-bitten-by-its-most-high-severity-vulnerability-in-years/


Shane Coughlan
OpenChain General Manager
+818040358083
Book a meeting:
https://meetings.hubspot.com/scoughlan


Re: Timezone management for our community

takashi1.ninjouji@...
 

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

-----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










Re: Timezone management for our community

Carlo "Kappa" Piana
 

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.



Re: Timezone management for our community

Sami Atabani
 

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.


Re: Timezone management for our community

james cloos
 

"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


Re: Timezone management for our community

Oliver Fendt
 

Dear all,

Option a) is fine for me

Ciao
Oliver

-----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


Re: Timezone management for our community

Keiichi Seki
 

+1

Best,
Keiichi Seki

-----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





Re: Timezone management for our community

Dave Marr
 

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





Re: Timezone management for our community

Christopher Wood
 

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





Re: Timezone management for our community

Jan Thielscher
 

+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





Re: Timezone management for our community

Sebastian Crane
 

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


Re: Timezone management for our community

Matija Šuklje
 

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


Re: Timezone management for our community

Carlo "Kappa" Piana
 

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 -----

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]







521 - 540 of 5034