From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: "Ricardo B. Marliere" <rbm@suse.com>,
Xiao Yang <yangx.jy@fujitsu.com>,
Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] Meetings schedule
Date: Fri, 7 Mar 2025 10:26:06 +0100 [thread overview]
Message-ID: <20250307092606.GA263657@pevik> (raw)
In-Reply-To: <67cabd64-fb43-4d1a-a471-995fd51a0e2b@suse.com>
Hi Andrea, all,
[ Cc hopefully all relevant people ]
Thanks for raising this, I'm sorry you have to wait 2 months to reply.
> Hello everyone,
> As you may have noticed, we haven't been able to follow our regular monthly
> schedule for LTP meetings. This has been due to time constraints on my end,
> as well as holidays and other commitments. As we enter the new year, I
> believe it would be beneficial to establish a consistent schedule so we can
> meet more frequently via public video calls.
> I have a few proposals for our meeting frequency:
> - Monthly meetings
> - Meetings every two months
> - Meetings after each release
I guess once a month is OK. Or, if it's too much to somebody once every 2
months. I'm not sure if it should be aimed before the release or after the
release.
> I suggest we aim to hold our meetings during the first week of the month. If
> a meeting cannot be held due to public holidays, we can consider
> rescheduling it for the following week.
LGTM. Which day? I would prefer not Friday.
Also, I would prefer it not clash with OATS monthly call: which is *second*
Thursday in month, 14:00 UTC (15h CET).
Kind regards,
Petr
> Please feel free to share your suggestions and vote based on your
> preferences. I look forward to hearing your thoughts! :-)
> Best regards,
> Andrea Cervesato
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-03-07 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 11:37 [LTP] Meetings schedule Andrea Cervesato via ltp
2025-03-07 9:26 ` Petr Vorel [this message]
2025-03-07 9:32 ` Cyril Hrubis
2025-03-07 10:06 ` Li Wang
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=20250307092606.GA263657@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
--cc=rbm@suse.com \
--cc=yangx.jy@fujitsu.com \
/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