Ksummit-Discuss Archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: ksummit-discuss@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
Date: Wed, 14 Jun 2017 09:29:20 -0400	[thread overview]
Message-ID: <20170614132920.csogpzkl4k5k7kaj@thunk.org> (raw)

After talking to Linus about what the next steps should be, here's the
plan that we've come up with.  The following people drawn from Linus's core
list will be extended invitations to the Maintainers Summit.

David Miller
Greg KH
Daniel Vetter
Ingo Molnar
Arnd Bergmann
Andrew Morton
Michael Ellerman
Takashi Iwai
Linus Torvalds
Ben Hutchings
Stephen Rothwell
Ted Ts'o
Shuah Kahn
James Bottomley

A mini-program committee composed of James Bottomley, Shuah Kahn, Greg
KH, and myself will pick enough names to bring the total number of
invited attendees to 30 for the Maintainers Summit, using the criteria
which Linus has described.

We will use the rest of names that Linus had mentioned as being part
of his secondary list to preseed the list of people to be considered.
People who suggest topics that should be discussed on the Maintainer's
summit will be added to the list.  Please prefix [MAINTAINERS SUMMIT]
to the subject line, and remember that we only have a half-day, and
they should be appropriate for the Maintainer's summit --- that is,
they should be focused on the development process.

For technical topics, we will have a "Kernel Summit" that will be work
much like the Technical Session days last year.  The technical
sessions will be run in parallel with the Open Source Summit Europe,
and will be open to anyone who registered with the OSS Europe.  The
goal 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 for maintainers).

To suggest a topic for the Kernel Summit, 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:

	ksummit-discuss@lists.linuxfoundation.org

We will also be reserving roughly half the slots to be scheduled on
the day of the conference, but if you know are interested in
organizing a discussion around a topic, or giving a presentation on
some topic that would be of interest to kernel developers, please send
them as soon as possible.  For each topic that is accepted and
submitted before July 8th, we will give a free admission to OSS Europe
/ Kernel Summit.  All others will have to pay the normal registration
fee.

If you were not subscribed on to the kernel-discuss mailing list from
last year (or if you had removed yourself after the kernel summit),
you can subscribe to the discuss list using mailman:

   https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

             reply	other threads:[~2017-06-14 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 13:29 Theodore Ts'o [this message]
2017-06-21  5:04 ` [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits Theodore Ts'o
2017-06-27 13:23 ` Daniel Vetter

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=20170614132920.csogpzkl4k5k7kaj@thunk.org \
    --to=tytso@mit.edu \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=linux-kernel@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).