From: Michael Richardson <mcr@sandelman.ca>
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security workgroup meeting times
Date: Mon, 27 Jan 2020 19:24:48 -0500 [thread overview]
Message-ID: <16942.1580171088@localhost> (raw)
In-Reply-To: <66647c93-56c8-f64f-4e13-abe1c703f8f7@linux.ibm.com>
Joseph Reynolds <jrey@linux.ibm.com> wrote:
> Let's try again to establish another OpenBMC Security Workgroup meeting
> time. The current meeting time (every other week 10am Pacific Daylight
> Time) is working for some, but not for others. To be clear, we would
> use the same workgroup, just have alternate meeting times.
> First, let's find a time that works for Australia, Asia, and Europe.
There aren't any such times :-)
If you move to 7am PST, 10am Eastern, then it's 14:00 UTC, which is still
within the working day in Germany, Helsinki and Tel-Aviv.
In Beijing, that's 11pm. Seoul, 00:00, and Syndey, 2am.
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20200131&p1=188&p2=33&p3=235&p4=240&p5=37
Many left-coast types that I work with prefer 7am, as they can do the meeting
while still at home, before traffic, before school-drop-off, etc.
(And aren't they all supposed to be super-health-nuts who get up at 6am to do Yoga?)
> Second, I am thinking we could establish alternating meeting times. We
> will not find a time that works for everyone. I try to accommodate
> folks who cannot attend by writing a summary of the topics and
> conclusions, and by pushing the work back out into this email list.
I've been on meetings that have simply alternated the AM/PM of the meeting.
7pm California
10pm NYC
4am Berlin/5am Helsinki
11am Beijing
12:00 Seoul
2pm Syndey
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2020-01-28 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 21:23 Security working group meeting 2020-01-22 Joseph Reynolds
2020-01-24 17:19 ` bmcweb and certificate chains [WAS: Security working group meeting 2020-01-22] Alexander Tereschenko
2020-01-27 16:03 ` Joseph Reynolds
2020-01-28 18:24 ` Alexander Tereschenko
2020-01-27 17:42 ` Security workgroup meeting times Joseph Reynolds
2020-01-28 0:24 ` Michael Richardson [this message]
2020-01-28 0:29 ` Andrew Jeffery
2020-01-28 0:50 ` Bruce Mitchell
2020-01-28 10:41 ` Alexander Tereschenko
2020-01-28 16:20 ` Bruce Mitchell
2020-05-13 18:31 ` Joseph Reynolds
2020-05-13 18:43 ` Bruce Mitchell
2020-05-13 21:50 ` Joseph Reynolds
2020-05-14 15:58 ` Michael Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16942.1580171088@localhost \
--to=mcr@sandelman.ca \
--cc=jrey@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.