All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [Weekly meetings] Change day/hour?
Date: Fri, 9 Dec 2022 11:55:47 +0800	[thread overview]
Message-ID: <20221209035547.GA28360@localhost.localdomain> (raw)
In-Reply-To: <4097df42-95ce-e535-429d-502233f484e5@shytyi.net>

On Thu, Dec 08, 2022 at 06:54:11PM +0100, Dmytro Shytyi wrote:
> Hello,
> 
> 
> It is okay for me to changing the meeting day to Tuesday.

It's fine for me too.

Thanks,
-Geliang

> 
> Thanks.
> 
> 
> Dmytro.
> 
> 
> On 12/8/2022 6:51 PM, Matthieu Baerts wrote:
> > Hello,
> > 
> > At the last meeting, we discussed the idea of re-scheduling the weekly
> > meetings we have because some people might not be able to join or prefer
> > another moment.
> > 
> > But because we were exceptionally only 3 today because of the feast of
> > the Immaculate Conception, we didn't take any decision. Instead, we
> > would then like to hear from people who want to participate to know what
> > they think about eventually:
> > 
> > - Changing the day to Tuesday?
> >    - It might be better to avoid Monday (morning) and Friday (evening).
> >    - Wednesday was not OK for today's participants
> > 
> > - Changing the time to have it one hour later?
> >    - It means 17:00 UTC (9am PST, 6pm CET, 1am CST)
> >    - This is late for people in China but midnight is late anyway
> >    - Maybe we can also schedule less frequent meetings at a different
> > time (or on request), e.g. morning in Europe, afternoon in China?
> >    - (the BPF weekly meetings are on Thursdays at 17:00 UTC)
> > 
> > What would be OK or not OK for you? Tuesday or Thursday, same time or
> > one hour later?
> > 
> > Thanks,
> > Matt

  reply	other threads:[~2022-12-09  3:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 17:51 [Weekly meetings] Change day/hour? Matthieu Baerts
2022-12-08 17:54 ` Dmytro Shytyi
2022-12-09  3:55   ` Geliang Tang [this message]
2022-12-09 20:59 ` Christoph Paasch
2022-12-10  0:17 ` Mat Martineau
2022-12-13 15:53 ` Matthieu Baerts

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=20221209035547.GA28360@localhost.localdomain \
    --to=geliang.tang@suse.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@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 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.