Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp90069pxj; Thu, 10 Jun 2021 15:45:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwx150f/L5nwO1g4t+fMfh7NuJfsp0ukPdxIrA1mavPVE8fA8A031CK5D9YHKESD8gGvbm/ X-Received: by 2002:a17:906:c791:: with SMTP id cw17mr644672ejb.329.1623365148550; Thu, 10 Jun 2021 15:45:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623365148; cv=none; d=google.com; s=arc-20160816; b=wpzPV+poLSU1h1Bs5v08lupCkaqPTmIWMVYu26qQEBc24ED3tzygbp3rKbNxPfL/Vp zBLoDm4y0CET5GpmS7otv3VJ1tFP7Oywc5/YBQwri3gZTLDKn5Vc+uN6/kYOmF028Kni MgidkEUqPVKFX8IM0QtX66IkbFfdb1EorQdtZQQGKTvyoYhEpSbOTd6yFsSiOEZ/14JV swIN5xKTKDGuW0griFfq4w6i2xYdDOIP6C9ZKQ2/N2eXx8FYcTBEIUhIPUc7AGYTJNwQ l2mozY13uwRCv90hXd8R30pK2QtBEa7AyHEEsM0L0spS+smNkZapvd9Pbev/9YNUQm4E mAEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=V5yzb21nbg0WXga74jQ6xsvVDaavF5Xwuj6ArQYTfOY=; b=T3kDfpyhAfYisnuf2ATpVt3PdadEagJlJqdAW56UzaRRFYtPLzFUkWrcqO2q/IR6i/ izTSKnB06SNEkXZzTRtDK7+YsDLKFmobX9KBfeF8Tyi6LD/5q1MZObpeLPjAXk8o6iMV 2QwjRFc89FPZ7fRC8NUuHfO5MIyTQ0RquNO9NbqhwnfsRLs9DeQ+p2WRcm8/7QcoGIXf /FLQJKf0eDoeA4w7svFon1xcgfmJGReFQ6iS6d/8ooiL7NFwQrnZUR7xSmpwEihV27le +/N9TXTiHTiljMROmKXZZHP41u2jqbxkLUo5juvoCAz7Y4fvKcz4Id/fKWA0qYA3DEYL eUrQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=M1YK6yb9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y18si3228730edv.141.2021.06.10.15.45.23; Thu, 10 Jun 2021 15:45:48 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=M1YK6yb9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230179AbhFJWpH (ORCPT + 99 others); Thu, 10 Jun 2021 18:45:07 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:28426 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230462AbhFJWpG (ORCPT ); Thu, 10 Jun 2021 18:45:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623364989; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=V5yzb21nbg0WXga74jQ6xsvVDaavF5Xwuj6ArQYTfOY=; b=M1YK6yb9pe86NT7q23TTdZXC8HIbtgqxKNSyyqoazVmHG5Mu/Lr8N+givFtOfgxrhiFqHQ 6SzzFq5UnvMGyX1e+TRf8vYJAkoyFeX+PmUjoZEUn7pKbEJVz4nr+cWH4PJ5XI2FCaIQzi kHxksnZewNzAcbwUOMCbV47xU7MYCXk= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-331-EGftjJSbPGuFZmvlRq6G3Q-1; Thu, 10 Jun 2021 18:43:08 -0400 X-MC-Unique: EGftjJSbPGuFZmvlRq6G3Q-1 Received: by mail-ed1-f71.google.com with SMTP id u26-20020a05640207dab02903935beb5c71so9192282edy.3 for ; Thu, 10 Jun 2021 15:43:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=V5yzb21nbg0WXga74jQ6xsvVDaavF5Xwuj6ArQYTfOY=; b=MzWoTB/l2xn1giG/YuTd+815tK15I/qfyYjYStG64M4aRv3VJdIeFypD1yeo3bXZEp nGbjExBLCMzR/ttbb90kuquXeVoj5Yz3c6lfkP+GCHifnPXiCHbUqA0kVGzI80TpjsB/ +Jz8raqA7m5UykEPIY1GrYYm9l71cAJbbkCnDQ6o+Yt72Yykuis8x//7LzyTmui5Tx1X 2zyzoaDcqDPp2k6smqGbV+YvsXUov9oDJ9MlIr7M21jOQH5ebZFITENMsNLrQf3LCItN cLY1n1qPyfhf1QI5XT5y5+NmzRgW7Tugh8JC+BwpV4IiLlvWyGCtw2fb1mXSOHcjf6va PZEg== X-Gm-Message-State: AOAM532CXH66RbASpASzmGP6bQChk7GSTy908ZWWpVm9fkU9zsXniUQG MgSlZaPw3gsybZbMWbjPCpmTjWhDI5HwYAlFmV3TO+DgFDdbTma+i8Hu3/sioJlbBGDz2CYPCCy WCXRedKTVKbicFXaymWwx9ZOk X-Received: by 2002:a17:906:e44:: with SMTP id q4mr686719eji.120.1623364987091; Thu, 10 Jun 2021 15:43:07 -0700 (PDT) X-Received: by 2002:a17:906:e44:: with SMTP id q4mr686706eji.120.1623364986880; Thu, 10 Jun 2021 15:43:06 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([45.145.92.2]) by smtp.gmail.com with ESMTPSA id ci12sm1489704ejc.17.2021.06.10.15.43.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Jun 2021 15:43:06 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 627F718071E; Fri, 11 Jun 2021 00:43:05 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Shuah Khan , Steven Rostedt , Laurent Pinchart Cc: Konstantin Ryabitsev , "Enrico Weigelt, metux IT consult" , David Hildenbrand , James Bottomley , Greg KH , Christoph Lameter , Theodore Ts'o , Jiri Kosina , 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 Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off In-Reply-To: <37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org> References: <5038827c-463f-232d-4dec-da56c71089bd@metux.net> <20210610182318.jrxe3avfhkqq7xqn@nitro.local> <20210610152633.7e4a7304@oasis.local.home> <37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org> X-Clacks-Overhead: GNU Terry Pratchett Date: Fri, 11 Jun 2021 00:43:05 +0200 Message-ID: <87tum5uyrq.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Shuah Khan writes: > On 6/10/21 1:26 PM, Steven Rostedt wrote: >> On Thu, 10 Jun 2021 21:39:49 +0300 >> Laurent Pinchart 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