All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: Bruce Mitchell <Bruce_Mitchell@phoenix.com>,
	openbmc <openbmc@lists.ozlabs.org>,
	Manojkiran Eda <manojeda@in.ibm.com>
Subject: Re: Security workgroup meeting times
Date: Thu, 14 May 2020 11:58:32 -0400	[thread overview]
Message-ID: <27892.1589471912@localhost> (raw)
In-Reply-To: <80674629-3a0f-3bca-d5c6-5a0efba7323c@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]


Joseph Reynolds <jrey@linux.ibm.com> wrote:
    > On 5/13/20 1:43 PM, Bruce Mitchell wrote:
    >> If you want to include Silicon Valley it seem like 22:00, 23:00,
    >> 00:00, 01:00, and 02:00 UTC/GMT are the only real options.

    > I think the current time (10:00am PDT) works for most Silicon Valley
    > folks.   I am looking for a second meeting time good for others not in
    > the Americas.   For example, we've has security collaborations from
    > folks in Switzerland Poland Russia India China and Australia, and I
    > want to find a time that work for those regions.

Perhaps the right thing is to therefore run a doodle poll which is exclusive
for those not in North America.  Then afterwards, the rest of us can opine/whine.

On days when it works, 10am PDT (1pm EDT for me) is indeed great, but last
few weeks, I'm booked into higher priority things.

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


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2020-05-14 15:58 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
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 [this message]

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=27892.1589471912@localhost \
    --to=mcr@sandelman.ca \
    --cc=Bruce_Mitchell@phoenix.com \
    --cc=jrey@linux.ibm.com \
    --cc=manojeda@in.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.