ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	"Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	David Hildenbrand <david@redhat.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Greg KH <greg@kroah.com>, Christoph Lameter <cl@gentwo.de>,
	Theodore Ts'o <tytso@mit.edu>, Jiri Kosina <jikos@kernel.org>,
	ksummit@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off
Date: Thu, 10 Jun 2021 16:31:58 -0400	[thread overview]
Message-ID: <20210610163158.017a9721@oasis.local.home> (raw)
In-Reply-To: <YMJ0IlYGHzwBNz2t@casper.infradead.org>

On Thu, 10 Jun 2021 21:20:50 +0100
Matthew Wilcox <willy@infradead.org> wrote:

> Perhaps we could actually _enhance_ conferences by forbidding
> direct audience questions and having a moderator select questions /
> "more of a comment actually" from an official live chat platform to
> engage the speaker directly on stage.  It would segue naturally into
> "the speaker is now done with their presentation and here's some good
> followup discussion".  So many times people have come up to me after
> a presentation and asked a question that I really wish I could have
> answered for everybody there.

For presentations, I think this is a very good idea. But it wouldn't
work for a BoF or a microconference.

I also thought about doing this for a presentations. That is, "Please
submit all questions online, and the presenter will answer them".

Of course, if you have someone that didn't bring their laptop or phone
(there are people that do that too). They should have a way to submit a
question as well. Perhaps instead of going in line to a microphone, go
in line to a public laptop to type in your question.

-- Steve

  reply	other threads:[~2021-06-10 20:32 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 15:28 Maintainers / Kernel Summit 2021 planning kick-off Theodore Ts'o
2021-04-28 10:29 ` Jiri Kosina
2021-04-30 21:48   ` Theodore Ts'o
2021-05-27 13:23     ` Christoph Lameter
2021-05-27 13:29       ` Greg KH
2021-05-28 14:58         ` James Bottomley
2021-05-28 15:11           ` Matthew Wilcox
2021-05-28 15:27             ` James Bottomley
2021-05-28 15:31               ` Laurent Pinchart
2021-05-28 15:44                 ` James Bottomley
2021-05-28 15:55                   ` Laurent Pinchart
2021-05-28 16:04                     ` James Bottomley
2021-05-28 16:31                       ` Laurent Pinchart
2021-05-28 15:42             ` Toke Høiland-Jørgensen
2021-06-09 10:37           ` David Hildenbrand
2021-06-09 19:23             ` James Bottomley
2021-06-11 10:58               ` Enrico Weigelt, metux IT consult
2021-06-10 18:07             ` Enrico Weigelt, metux IT consult
2021-06-10 18:23               ` Konstantin Ryabitsev
2021-06-10 18:39                 ` Laurent Pinchart
2021-06-10 19:26                   ` Steven Rostedt
2021-06-10 19:55                     ` Shuah Khan
2021-06-10 20:02                       ` Steven Rostedt
2021-06-10 20:20                         ` Matthew Wilcox
2021-06-10 20:31                           ` Steven Rostedt [this message]
2021-06-10 22:43                       ` Toke Høiland-Jørgensen
2021-06-11  2:59                         ` Willy Tarreau
2021-06-11  9:13                           ` Mauro Carvalho Chehab
2021-06-11  9:51                             ` Willy Tarreau
2021-06-18 13:46                       ` Laurent Pinchart
2021-06-18 14:11                         ` James Bottomley
2021-06-18 14:17                           ` Steven Rostedt
2021-06-18 14:28                           ` Geert Uytterhoeven
2021-06-18 14:32                             ` Steven Rostedt
2021-06-18 14:45                               ` Laurent Pinchart
2021-06-18 14:58                               ` Geert Uytterhoeven
2021-06-18 15:14                                 ` Matthew Wilcox
2021-06-18 15:23                                   ` Steven Rostedt
2021-06-18 15:29                                   ` Geert Uytterhoeven
2021-06-18 15:34                                     ` Steven Rostedt
2021-06-18 15:36                                       ` Steven Rostedt
2021-06-18 16:33                                       ` Mauro Carvalho Chehab
2021-06-18 15:58                               ` Mark Brown
2021-06-18 16:45                                 ` Mauro Carvalho Chehab
2021-06-18 14:46                             ` James Bottomley
2021-06-22 22:33                         ` Shuah Khan
2021-06-22 22:59                           ` Laurent Pinchart
2021-06-22 23:33                             ` Shuah Khan
2021-06-22 23:57                               ` Shuah Khan
2021-06-23  0:06                                 ` Laurent Pinchart
2021-06-23  0:15                                 ` Steven Rostedt
2021-06-10 20:12                   ` Konstantin Ryabitsev
2021-06-10 18:55               ` Linus Torvalds
2021-06-18 13:34             ` Enrico Weigelt, metux IT consult
2021-06-18 14:08               ` Steven Rostedt
2021-06-11 11:10           ` David Howells
2021-06-15 18:23             ` Enrico Weigelt, metux IT consult
2021-06-15 18:30               ` Matthew Wilcox
2021-06-15 18:34                 ` Konstantin Ryabitsev
2021-06-15 18:40                 ` Laurent Pinchart

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=20210610163158.017a9721@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=cl@gentwo.de \
    --cc=david@redhat.com \
    --cc=greg@kroah.com \
    --cc=jikos@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkml@metux.net \
    --cc=netdev@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.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 NNTP newsgroup(s).