From: Shuah Khan <shuahkhan@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Kernel Summit 2017 Feedback Thread
Date: Mon, 30 Oct 2017 16:19:57 -0600 [thread overview]
Message-ID: <CAKocOOPGx8EYgmXzEfWa4XQj+caaTt=YboDc25ct52EHXLLeEg@mail.gmail.com> (raw)
In-Reply-To: <20171030220652.mintguegkoln4vgz@thunk.org>
On Mon, Oct 30, 2017 at 4:06 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> On Mon, Oct 30, 2017 at 09:09:10PM +0100, Arnd Bergmann wrote:
>>
>> I think a lot of people were simply unaware of the new format and
>> how to use it. I heard from multiple people that were at the kernel
>> summit that they only learned on the same day that they would be
>> allowed to participate. I'm sure others didn't get the message at all
>> and just didn't show up, either to the entire event or the kernel summit
>> sessions.
>
> It was announced several months ago on the ksummit-discuss list when
> we sent out the call for Maintainer's Summit and Kernel Summit topics.
> There was also a note in the Kernel Summit Agenda sent out the week
> beforehand that the it was open to anyone with a Maintainer Summit or
> OSS Europe badge[1]) to the LKML list.
>
> I thought about cc'ing that note to LKML, but I decided against it on
> the theory it would be spamming LKML, and figured everyone who might
> be interested was on ksummit-discuss anyway. Also, this was a
> continuation of the Kernel Summit "Open Day", where the technical
> track was open to all attendees of the colocated conference (e.g.,
> Plumbers in Santa Fe, Linux Con Korea in Seoul, etc.) in previous
> years.
>
> Clearly, I had forgotten the key e-mail marketing dictum that there is
> no such thing as over-communicating (at least until you get dropped
> into people's SPAM filters :-).
>
The smaller group worked well for the regression tracking, and maintainer
discussions.
However one thing that was missing was the lightening talks. These
stemmed from a larger group interaction. If we can find a way to get
them into the current format, that would be awesome. Maybe we can
add a session to Kernel summit or make that part of unconference track.
Even so, it is important to have the right mix of people. We just got that
by default with the older format.
I am interested in summary for the session especially the discussion around
working across sub-systems Kees brought up. It would be good to send a
summary for the entire session. Anybody taking notes, I was busy listening
and talking :)
thanks,
-- Shuah
next prev parent reply other threads:[~2017-10-30 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 10:12 Theodore Ts'o
2017-10-30 12:41 ` Michael Kerrisk (man-pages)
2017-10-30 19:36 ` Theodore Ts'o
2017-10-30 15:26 ` Laura Abbott
2017-10-30 19:41 ` Theodore Ts'o
2017-10-30 20:09 ` Arnd Bergmann
2017-10-30 22:06 ` Theodore Ts'o
2017-10-30 22:19 ` Shuah Khan [this message]
2017-10-31 16:29 ` Mark Brown
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='CAKocOOPGx8EYgmXzEfWa4XQj+caaTt=YboDc25ct52EHXLLeEg@mail.gmail.com' \
--to=shuahkhan@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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