From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Steven Rostedt" <rostedt@goodmis.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: Fri, 11 Jun 2021 11:13:07 +0200 [thread overview]
Message-ID: <20210611111248.250e6da8@coco.lan> (raw)
In-Reply-To: <20210611025942.GE25638@1wt.eu>
Em Fri, 11 Jun 2021 04:59:42 +0200
Willy Tarreau <w@1wt.eu> escreveu:
> On Fri, Jun 11, 2021 at 12:43:05AM +0200, Toke Høiland-Jørgensen wrote:
> > Shuah Khan <skhan@linuxfoundation.org> writes:
> > > I have a
> > > couple of ideas on how we might be able to improve remote experience
> > > without restricting in-person experience.
> > >
> > > - Have one or two moderators per session to watch chat and Q&A to enable
> > > remote participants to chime in and participate.
> > > - Moderators can make sure remote participation doesn't go unnoticed and
> > > enable taking turns for remote vs. people participating in person.
> > >
> > > It will be change in the way we interact in all in-person sessions for
> > > sure, however it might enhance the experience for remote attendees.
> >
> > This is basically how IETF meetings function: At the beginning of every
> > session, a volunteer "jabber scribe" is selected to watch the chat and
> > relay any questions to a microphone in the room. And the video streaming
> > platform has a "virtual queue" that remove participants can enter and
> > the session chairs are then responsible for giving people a chance to
> > speak. Works reasonably well, I'd say :)
>
> I was about to say the same. In addition, local participants line up
> at a microphone and do not interrupt the speaker, but the organiser
> gives them the signal to ask a question. This allows to maintain a
> good balance between local and remote participants. Also it's common
> to see some locals go back to their seat because someone else just
> asked the same question. And when remote questions are asked using
> pure text, it's easy for the organiser to skip them if already
> responded as well.
>
> This method is rather efficient because it doesn't require to keep the
> questions for the end of the session, yet questions do not interrupt
> the speaker. It also solves the problem of people not speaking in the
> microphone. The only thing is that it can be quite intimidating for
> local participants who are too shy of standing up in front of a
> microphone and everyone else.
If someone is shy, he/she could simply type the question as a
remote participant would do.
This should work fine for a normal speech, but for BoFs and the
usual "round table" discussions we have at Kernel Maintainers,
this may not work well for local participants.
I guess that, for such kind of discussions, I can see two
possible alternatives:
1. everyone would use their laptop cameras/mics;
2. every round table would have their on camera/mic set.
(1) is probably simpler to implement, but may provide a worse
experience for local participants. (2) is probably harder to
implement, as the usual conference logistics company may not
have cameras.
In either case, a moderator (or some moderating software) is needed
in order queue requests for speech. So, basically, when someone
(either in a table or remote) wants to speak, it adds its name to
a queue, which will then be parsed at the queue's order. This is not
as natural as a physical meeting, but I guess it won't bring too
much burden to local people.
Thanks,
Mauro
next prev parent reply other threads:[~2021-06-11 9:13 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 [this message]
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=20210611111248.250e6da8@coco.lan \
--to=mchehab@kernel.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=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=toke@redhat.com \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/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.