ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Laura Abbott <labbott@redhat.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Kernel Summit 2017 Feedback Thread
Date: Mon, 30 Oct 2017 15:41:30 -0400	[thread overview]
Message-ID: <20171030194130.mzkd6zvxuxoumx6k@thunk.org> (raw)
In-Reply-To: <5a569d45-ef78-3ab6-1926-2359ffb2ddb9@redhat.com>

On Mon, Oct 30, 2017 at 08:26:01AM -0700, Laura Abbott wrote:
> 
> What ended up happening in the unconference anyway? I mostly didn't
> think about it but part of that was not knowing what was being
> discussed. I get the nature of the unconference makes it hard to
> plan ahead but there didn't seem to be a good way to know what was
> being discussed.

There was one unconference slot used this year, and it was a
continuation of the Linux security discussion.  People were supposed
to post proposals to the ksummit-discuss list, but this didn't seem to
work very well this year compared to last year in Santa Fe (where
roughly half of the unconference slots were used).

It could have been that between KVM Forum, ELC, and OSS Europe, there
was simply less of a need for more kernel-oriented discussions.

One of the things I've thought about doing for next year is to set up
a wiki page to make it easier for people to sign up slots.

	       	       	       	      	  - Ted

  reply	other threads:[~2017-10-30 19:41 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 [this message]
2017-10-30 20:09     ` Arnd Bergmann
2017-10-30 22:06       ` Theodore Ts'o
2017-10-30 22:19         ` Shuah Khan
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=20171030194130.mzkd6zvxuxoumx6k@thunk.org \
    --to=tytso@mit.edu \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=labbott@redhat.com \
    /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