From: "Theodore Tso" <tytso@mit.edu>
To: ksummit@lists.linux.dev
Subject: Maintainers Summit agenda
Date: Wed, 7 Oct 2026 05:21:52 -0400 [thread overview]
Message-ID: <asYNdMy-fMNOAugp@mit.edu> (raw)
Hi all,
My apologies for not sending this sooner. Things have been a little
busy during Plumbers! In the interests of transparency, here is the
planned agenda for the Maintainer Summit.
If you have strong opinions about any of our planned topics, feel free
to reply to this e-mail. If you are in the LPC in Prague, and you
happen to see me or any one else on the attendee list, you can also
give us your opinions in person.
Cheers,
- Ted
Maintainers Summit
Thursday, October 8th, 2026.
8:00 Hot breakfast and morning refreshments
9:00 Welcome and Agenda Bashing
9:30 LLM Code Review
10:00 LLM Code Generation
10:30 Break
11:00 Coping with the flood of new developers
11:30 Scaling our security process
12:00 Lunch
1:30 What are my pain points? (** See below)
2:00 Reacting to the pain points
2:30 Group Photograph
** What are my pain points? Every attendee is asked to prepare (ahead
of time) a brief, one-minute answer to the question: "What are my
pain points and what is one concrete realistic change would make my
life more pleasant" There shall be no interruptions or discussions
during the initial statements. We'll have time to react to
people's pain points and suggested changes at the following
session.
------------------
Attendee list:
Alexei Starovoitov
Arnd Bergmann
Christian Brauner
Dave Airlie
Greg KH
Jon Corbet
Linus Torvalds
Mark Brown
Miguel Ojeda
Rafael J. Wysocki
Theodore Ts'o
Konstantin Ryabitsev
Thomas Gleixner
Will Deacon
David Hildenbrand
Sasha Levin
Alice Ryhl
Christoph Hellwig
Jiri Kosina
Roman Gushchin
Eric Dumazet
Julia Lawall
Laurent Pinchart
Shuah Khan
Peter Zijlstra
Danilo Krummrich
Paolo Abeni
Eric Biggers
David Sterba
reply other threads:[~2026-10-07 9:21 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=asYNdMy-fMNOAugp@mit.edu \
--to=tytso@mit.edu \
--cc=ksummit@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.