Linux Kernel Summit discussions
 help / color / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: 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: Thu, 10 Jun 2021 13:55:23 -0600
Message-ID: <37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org> (raw)
In-Reply-To: <20210610152633.7e4a7304@oasis.local.home>

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.

thanks,
-- Shuah

  reply index

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 15:28 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 [this message]
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-10 20:12                   ` Konstantin Ryabitsev
2021-06-10 18:55               ` Linus Torvalds
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=37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org \
    --to=skhan@linuxfoundation.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=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

Linux Kernel Summit discussions

Archives are clonable:
	git clone --mirror https://lore.kernel.org/ksummit/0 ksummit/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ksummit ksummit/ https://lore.kernel.org/ksummit \
		ksummit@lists.linux.dev
	public-inbox-index ksummit

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/dev.linux.lists.ksummit


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git