linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	"Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	David Hildenbrand <david@redhat.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: Fri, 18 Jun 2021 07:11:44 -0700	[thread overview]
Message-ID: <cd7ffbe516255c30faab7a3ee3ee48f32e9aa797.camel@HansenPartnership.com> (raw)
In-Reply-To: <YMyjryXiAfKgS6BY@pendragon.ideasonboard.com>

On Fri, 2021-06-18 at 16:46 +0300, Laurent Pinchart wrote:
> For workshop or brainstorming types of sessions, the highest barrier
> to participation for remote attendees is local attendees not speaking
> in microphones. That's the number one rule that moderators would need
> to enforce, I think all the rest depends on it. This may require a
> larger number of microphones in the room than usual.

Plumbers has been pretty good at that.  Even before remote
participation, if people don't speak into the mic, it's not captured on
the recording, so we've spent ages developing protocols for this. 
Mostly centred around having someone in the room to remind everyone to
speak into the mic and easily throwable padded mic boxes.  Ironically,
this is the detail that meant we couldn't hold Plumbers in person under
the current hotel protocols ... the mic needs sanitizing after each
throw.

James



  reply	other threads:[~2021-06-18 14:11 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
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 [this message]
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=cd7ffbe516255c30faab7a3ee3ee48f32e9aa797.camel@HansenPartnership.com \
    --to=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=rostedt@goodmis.org \
    --cc=skhan@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;
as well as URLs for NNTP newsgroup(s).