From: Richard Palethorpe <rpalethorpe@suse.de>
To: LTP List <ltp@lists.linux.it>
Subject: [LTP] [RFC] LTP open monthly meeting
Date: Thu, 19 Oct 2023 10:31:10 +0100 [thread overview]
Message-ID: <875y33vsks.fsf@suse.de> (raw)
Hello,
I propose a meeting once a month to discuss non-technical things such as
patch review policy, overall direction and bike shed discussions. Anyone
is welcome who is interested in that.
Originally I thought just to include myself and some SUSE colleagues in
an ad-hoc meeting to deal with Reviewed-by tag delegation. However I
think the real problem is we have no LTP meeting in which to discuss
these things and chat. The ML is not adequate for this IMO.
For me any time and day would be fine excluding 22:00 to 09:00
UTC/GMT. Probably Monday to Friday would be best for most.
The agenda for the first meeting would be to discuss how to deal with
the situation where someone reviews the V1 of a patch, but does not add
their Reviewed-by tag in subsequent versions.
After that just introductions, questions and anything someone would like
to bring up.
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2023-10-19 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:31 Richard Palethorpe [this message]
2023-10-19 11:03 ` [LTP] [RFC] LTP open monthly meeting Andrea Cervesato via ltp
2023-10-19 11:08 ` Petr Vorel
2023-10-19 11:30 ` Marius Kittler
2023-10-19 12:59 ` Petr Vorel
2023-10-26 10:01 ` Richard Palethorpe
2023-10-19 11:39 ` Wei Gao via ltp
2023-10-19 12:28 ` Cyril Hrubis
2023-10-20 3:04 ` Li Wang
2023-10-20 11:56 ` Cyril Hrubis
2023-10-23 8:10 ` Richard Palethorpe
2023-10-23 8:51 ` Li Wang
2023-10-26 10:16 ` [LTP] Open monthly meeting 1st of November 09:00 UTC Richard Palethorpe
2023-10-27 2:34 ` Li Wang
2023-11-01 9:33 ` Richard Palethorpe
2023-11-01 10:00 ` Cyril Hrubis
2023-11-01 10:12 ` Petr Vorel
2023-11-01 14:14 ` Jan Stancek
2023-11-03 6:56 ` Petr Vorel
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=875y33vsks.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
/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