Ksummit-Discuss Archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Megan Phillips <mphillips@linuxfoundation.org>
Subject: [Ksummit-discuss] Kernel Summit / Maintainer's Summit Agenda
Date: Mon, 23 Oct 2017 09:11:54 -0400	[thread overview]
Message-ID: <20171023131154.lrmbsfh5o44cvh4i@thunk.org> (raw)

Hi, the Kernel Summit and Maintainer's Summit is attached below.  The
sessions are subject to change; the authoratative version will be
available at:

	https://goo.gl/xUT5Er

Note that there are unconference slots available; if you are
interested in dynamically scheduling one of those slots, please send
e-mail to ksummit-discuss with "[UNCONFERENCE]" in the subject line
proposing a talking and preferred time slot.

There are still two empty maintainer's session slots.  There were a
few expressed topics that had some interest --- including two for
"feature ABI gates".  However, Linus has said, "No, no, no."  If
people want to try to convince him otherwise, feel free to jump on
that thread on ksummit-discuss from mid-August[1]...

[1] https://memegenerator.net/img/instances/500x/80611817/wait-let-me-get-some-popcorn-first-ok-go-on.jpg

    	       		       	    		      - Ted

Tuesday
========

Note: The Kernel Summit sessions are open to anyone with a Open Source
Summit or Maintainer's Summit badge.

With the exception of the OSS events noted below, the Kernel Summit
events will be held in the Athens room.

 9:00 (OSS Keynotes)
10:25 Coffee Break 
10:55 Pulling away from the tracing ABI quicksand (Mathieu Desnoyers, Steve Rostedt)
11:45 Printk redesign (Petr Mladek & Steve Rostedt)
12:25 Lunch
14:05 (OSS Kernel Panel)
14:55 Power Management (Rafael J. Wysocki)
15:35 Coffee Break 
16:05 Kernel Documentation (Mauro Carvalho, Jon Corbet)
16:55 Restartable Sequences (Mathieu Desnoyers)

Onsite Attendee reception 5:35pm

Wednesday
=========

 9:00 (OSS Keynotes)
10:15 (OSS Conversation with Linus)
10:35 Coffee break
11:05 Improve regression tracking (Thorsten Leemuis)
11:55 Kselftest use-cases (Shuah Khan)
12:35 lunch
14:15 Kernel Security (James Morris)
15:05 Kernel developer security hygiene (Konstantin Ryabitsev)
15:45 Coffee break
16:15 TBA
17:05 TAB Elections

All-Attendee reception 6pm

Topics that were discussed, maybe unconference talks?

* Mobile phones
* Improving Kconfig
* Bug reporting feedback loop
* Developing across multiple areas of the kernel?


Maintainers Summit  -- Thursday

 8:00 am Breakfast
 9:00 am Agenda Bashing
 9:30 am Improve regression tracking
10:00 am Bash the kernel maintainers
10:30 am Android Kernel Issues (drivers, long-term stable)
11:00 am What is Linus Happy/Unhappy about?
11:30 am 
12:00 am 
12:30 pm Lunch


Topics that were discussed:

Bug reporting feedback loop -- vote
Driver and/or module versions
Developing across multiple areas of the kernel -- vote
Improve regression tracking
ABI feature gates -- vote x2 (but Linus has said "absolutely not")

             reply	other threads:[~2017-10-23 13:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 13:11 Theodore Ts'o [this message]
2017-10-23 13:18 ` [Ksummit-discuss] Kernel Summit / Maintainer's Summit Agenda Jonathan Corbet
2017-10-23 14:10   ` Theodore Ts'o
2017-10-23 14:17     ` Jonathan Corbet
2017-10-23 14:48       ` Theodore Ts'o
2017-10-23 15:38         ` Megan Phillips
2017-10-23 20:08         ` Rafael J. Wysocki
2017-10-23 22:29           ` Randy Dunlap
2017-10-23 22:47             ` Rafael J. Wysocki
2017-10-24  8:22           ` Theodore Ts'o
2017-10-24  8:24             ` Megan Phillips
2017-10-24  8:43               ` Rafael J. Wysocki
2017-10-25 14:30 ` Greg KH
2017-10-25 21:31   ` Megan Phillips
2017-10-26  5:45   ` James Bottomley
2017-10-26  6:19     ` James Bottomley

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=20171023131154.lrmbsfh5o44cvh4i@thunk.org \
    --to=tytso@mit.edu \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=mphillips@linuxfoundation.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).