public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: "kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Subject: New open hours for AMER-EMEA timezones
Date: Fri, 6 Oct 2023 10:25:36 +0200	[thread overview]
Message-ID: <f059956c-30ac-2ada-8c19-8bacc0b8b969@collabora.com> (raw)

Hello,

As discussed previously several times in the past and more
recently with Kevin and Nikolay, the currently weekly Thursday
meetings are good for EMEA and APAC timezones but not AMER,
especially not US Pacific.  The idea is now to add an extra open
hours and it seems like Wednesdays at 17:00 UTC would be ideal.
It would be good to have at least a couple of people from EMEA
time zones attend it and help bridge the gap with the Thursday
meetings rather than just rely on written notes.

How does that sound?

I've prepared a poll to get an idea of people's preferences with
a few other options around this time window:

  https://framadate.org/6NDCHsuSbG78v5a6

Thanks,
Guillaume

             reply	other threads:[~2023-10-06  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06  8:25 Guillaume Tucker [this message]
2023-10-10 10:22 ` New open hours for AMER-EMEA timezones Guillaume Tucker

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=f059956c-30ac-2ada-8c19-8bacc0b8b969@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=kernelci@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox