linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
	Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
	linux-block@vger.kernel.org, netdev@vger.kernel.org,
	linux-mm@kvack.org, ksummit@lists.linux.dev,
	linux-security-module@vger.kernel.org
Subject: Re: Maintainers Summit 2024 Call for Topics
Date: Sat, 15 Jun 2024 09:07:37 +0100	[thread overview]
Message-ID: <20240615080737.GG1906022@mit.edu> (raw)
In-Reply-To: <20240531144957.GA301668@mit.edu>

Many thanks to those who have submitted topics for the Maintainers
Summit and to the Kernel Summit track at the Linux Plumber's
Conference.

We have extended the deadline for Kernel Summit proposals by a week,
to June 23.  If you have something that you would like to share with
the kernel development community as a technical topic, or something
you'd like to porpose as a Maintainers Summit topic, please submit
your proposal in the next week!

Many thanks,

						- Ted

On Fri, May 31, 2024 at 04:49:57PM +0200, Theodore Ts'o wrote:
> This year, the Maintainers Summit will be held in Vienna, Austria on
> Tuesday, September 17th, 2024, just before the Linux Plumber's Conference
> (September 18--20th).
> 
> 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].
> 
> To get the most out of our topic discussions, folks proposing a topic
> should also suggest relevant people and desired outcomes.
> 
> For an examples of past Maintainers Summit topics, please see these
> LWN articles:
> 
>  * 2023 https://lwn.net/Articles/951847/
>  * 2022 https://lwn.net/Articles/908320/
>  * 2021 https://lwn.net/Articles/870415/
> 
> The Kernel Summit is organized as a track which is run in parallel
> with the other tracks at the Linux Plumbers Conference (LPC), and is
> open to all registered attendees of LPC.  The goal of the Kernel
> Summit track will be to provide a forum to discuss specific technical
> issues that would be easier to resolve in person than over e-mail.
> The program committee will also consider "information sharing" topics
> if they are clearly of interest to the wider development community
> (i.e., advanced training in topics that would be useful to kernel
> developers).
> 
> To suggest a topic for the Kernel Summit, please do two things. by
> June 16th, 2024.  First, please tag your e-mail with [TECH TOPIC].  As
> before, please use a separate e-mail for each topic, and send the
> topic suggestions to the ksummit discussion list.
> 
> Secondly, please create a topic at the Linux Plumbers Conference
> proposal submission site and target it to the Kernel Summit track:
> 
> 	https://lpc.events/event/18/abstracts/
> 
> Please do both steps.  I'll try to notice if someone forgets one or
> the other, but your chances of making sure your proposal gets the
> necessary attention and consideration are maximized by submitting both
> to the mailing list and the web site.
> 
> 
> 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
> Sasha Levin
> Ted Ts'o
> Rafael J. Wysocki
> 

           reply	other threads:[~2024-06-15  8:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240531144957.GA301668@mit.edu>]

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=20240615080737.GG1906022@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=linux-security-module@vger.kernel.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 NNTP newsgroup(s).