From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: 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,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off
Date: Fri, 11 Jun 2021 00:43:05 +0200 [thread overview]
Message-ID: <87tum5uyrq.fsf@toke.dk> (raw)
In-Reply-To: <37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org>
Shuah Khan <skhan@linuxfoundation.org> writes:
> On 6/10/21 1:26 PM, Steven Rostedt wrote:
>> On Thu, 10 Jun 2021 21:39:49 +0300
>> Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
>>
>>> There will always be more informal discussions between on-site
>>> participants. After all, this is one of the benefits of conferences, by
>>> being all together we can easily organize ad-hoc discussions. This is
>>> traditionally done by finding a not too noisy corner in the conference
>>> center, would it be useful to have more break-out rooms with A/V
>>> equipment than usual ?
>>
>> I've been giving this quite some thought too, and I've come to the
>> understanding (and sure I can be wrong, but I don't think that I am),
>> is that when doing a hybrid event, the remote people will always be
>> "second class citizens" with respect to the communication that is going
>> on. Saying that we can make it the same is not going to happen unless
>> you start restricting what people can do that are present, and that
>> will just destroy the conference IMO.
>>
>> That said, I think we should add more to make the communication better
>> for those that are not present. Maybe an idea is to have break outs
>> followed by the presentation and evening events that include remote
>> attendees to discuss with those that are there about what they might
>> have missed. Have incentives at these break outs (free stacks and
>> beer?) to encourage the live attendees to attend and have a discussion
>> with the remote attendees.
>>
>> The presentations would have remote access, where remote attendees can
>> at the very least write in some chat their questions or comments. If
>> video and connectivity is good enough, perhaps have a screen where they
>> can show up and talk, but that may have logistical limitations.
>>
>
> You are absolutely right that the remote people will have a hard time
> participating and keeping up with in-person participants. 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 :)
-Toke
next prev parent reply other threads:[~2021-06-10 22:43 UTC|newest]
Thread overview: 59+ 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 [this message]
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 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=87tum5uyrq.fsf@toke.dk \
--to=toke@redhat.com \
--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=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).