From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-mm@kvack.org, ksummit@lists.linux.dev
Subject: Maintainers Summit 2023 Call for Topics
Date: Tue, 15 Aug 2023 01:29:47 -0400 [thread overview]
Message-ID: <20230815052947.GA3214753@mit.edu> (raw)
This year, the Maintainers Summit will be held in Richmond, VA on
November 16th, 2023, just after the Linux Plumber's Conference
(November 13--15th).
As in previous years, the Maintainers Summit is invite-only, where the
primary focus will be process issues around Linux Kernel Development.
It will be limited to 30 invitees and a handful of sponsored
attendees.
Linus has generated a list of people for the program committee to
consider. People who suggest topics that should be discussed at the
Maintainers Summit will also be added to the list for consideration.
To make topic suggestions for the Maintainers Summit, please send
e-mail to the ksummit@lists.linux.dev with a subject prefix of
[MAINTAINERS SUMMIT].
For an examples of past Maintainers Summit topics, please see the
these LWN articles:
* 2022 https://lwn.net/Articles/908320/
* 2021 https://lwn.net/Articles/870415/
* 2019 https://lwn.net/Articles/799060/
Invites will be sent out on a rolling basis, with the first batch
being sent out in roughly 2 weeks or so, so if you have some topics
which you are burning to discuss, why not wait and submit them today? :-)
If you were not subscribed on to the kernel mailing list from
last year (or if you had removed yourself after the kernel summit),
you can subscribe by sending an e-mail to the address:
ksummit+subscribe@lists.linux.dev
The program committee this year is composed of the following people:
Christian Brauner
Jon Corbet
Greg KH
Ted Ts'o
Rafael J. Wysocki
reply other threads:[~2023-08-15 5:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230815052947.GA3214753@mit.edu \
--to=tytso@mit.edu \
--cc=ksummit@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).