All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Maintainer's Summit Agenda Planning
Date: Thu, 5 Oct 2017 15:20:02 -0400	[thread overview]
Message-ID: <20171005192002.hxbjjdjhrfa4oa37@thunk.org> (raw)

This is a rough draft of a proposed agenda for the Maintainer's
Summit.

I've fliled in most of the slots with those topics that seemed to make
the most amount of sense as topics for us to talk about, with some
room intentionally blank sponts.

Please comment about topics you think we should include in the agenda;
or if you think there are topics that should not be included, please
also let us know.

Thanks!!

					- Ted

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


Appendix: Other topics that were brought up
-------------------------------------------

Documentation
Bug reporting feedback loop
Driver and/or module versions
Developing across multiple areas of the kernel
ABI feature gates
tracepoints without user space interfaces (EBPF)

Appendix: Maintainer's Summit Attendees
---------------------------------------

(Does not include the sponsored attendees; I don't have most of those
names yet.)

Andrew Morton
Arnd Bergmann
Ben Hutchings
Chris Mason
Dan Williams
Fengguang Wu
Greg KH
H. Peter Anvin
James Bottomley
Jens Axboe
Jiri Kosina
Jonathan Corbet
Kees Cook
Laura Abbott
Linus Torvalds
Martin Petersen
Michael Ellerman
Rom Lemarchand
Sean Paul
Shuah Khan
Stephen Rothwell
Takashi Iwai
Ted Ts'o
Thorsten Leemhuis

             reply	other threads:[~2017-10-05 19:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 19:20 Theodore Ts'o [this message]
2017-10-05 20:13 ` [Ksummit-discuss] Maintainer's Summit Agenda Planning Rafael J. Wysocki
2017-10-05 21:55 ` Jiri Kosina
2017-10-06 14:59 ` Takashi Iwai
2017-10-06 15:27 ` James Bottomley
2017-10-06 16:26   ` Josh Poimboeuf
2017-10-06 16:32     ` Jonathan Corbet
2017-10-06 16:51       ` Josh Poimboeuf
2017-10-06 16:56       ` James Bottomley
2017-10-06 17:16         ` Josh Poimboeuf
2017-10-06 20:11       ` Linus Walleij
2017-10-09  8:13   ` Mark Brown
2017-10-09 15:54   ` Jiri Kosina
2017-10-09 16:37     ` James Bottomley
2017-10-09 16:47       ` Joe Perches
2017-10-09 16:49       ` Julia Lawall
2017-10-09 16:56         ` James Bottomley
2017-10-09 17:04           ` Joe Perches
2017-10-11 18:51           ` Jani Nikula
2017-10-12 10:03             ` Daniel Vetter
2017-10-16 14:12             ` James Bottomley
2017-10-16 14:25               ` Jani Nikula
2017-10-16 16:07                 ` Joe Perches
2017-10-17  8:34                   ` Jani Nikula
2017-10-18  1:27                     ` Joe Perches
2017-10-18 10:41                       ` Jani Nikula
2017-10-16 18:52               ` Mark Brown
2017-10-10  8:53       ` Jiri Kosina
2017-10-24 23:03   ` Kees Cook
2017-10-24 23:41     ` Joe Perches
2017-10-25  0:54       ` Kees Cook
2017-10-25  4:21         ` Julia Lawall
2017-10-25  4:29           ` Joe Perches
2017-10-25  4:36             ` Julia Lawall
2017-10-25  6:05         ` Martin K. Petersen
2017-10-25  6:55           ` Kees Cook
2017-10-25  7:34             ` Martin K. Petersen
2017-10-25  6:45         ` Frank Rowand
2017-10-25  7:56         ` Mark Brown
2017-10-25  9:39         ` Laurent Pinchart
2017-10-31 19:19         ` Rob Herring
2017-10-31 19:28           ` Kees Cook

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=20171005192002.hxbjjdjhrfa4oa37@thunk.org \
    --to=tytso@mit.edu \
    --cc=ksummit-discuss@lists.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 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.