Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp217480pxj; Thu, 10 Jun 2021 20:03:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzhjvTsdl0jmV10/hnkRJ+RW6UP7yo0Y6P49SAxPveYGpIm9c0LXo2hcDtGL7T7njmS/j3C X-Received: by 2002:a17:906:3016:: with SMTP id 22mr1431608ejz.28.1623380619352; Thu, 10 Jun 2021 20:03:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623380619; cv=none; d=google.com; s=arc-20160816; b=ltLx37h9uTBLzaW4TKSLWgqFTehdiU60at+FS3qtJaetbEsJo2bbkTVbbulV4qtaW0 ycAX2d8T9Aogo1XtfAEd3iN80ACqE8SF5JiBgLXdzfatybJypezbbMf8qo718fTx9LRx mPznlFJOU7C6uw3h1+5BR08geuSm1K8XBi2jKp9sYjkvL4qhtvnpNW3WbwYS7PysK/be O9ICSSRJJjmTxrBnwngEISIPB4VPtAAx2eb/YrxkjHRnnmF5qXtSgt9bHwbfjp++OlmD ijCHCtYW5fEatmATKEQS4BTloAT82pj4fJ7oWpqc9GAfMdgEAnIGwJVDImItV+QZD6N6 UYRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=n7bAKGSMtS45DapPl2t3jYmO8/AAVJRMqtlNPPvFU6Q=; b=LL5quTzebbFxN516sUMKAY+Afm+z/06KI0zo1TJPMVT9BE+IRSMLRYR3+Dbm78pGQF pJgSKXfJXsIiEpwstm8XhI1BWeVmIvM0hCs1dejut02WD18w18C+K8TfMiZJiQMoqgyq HkRBPbblXo1bcokX6894P154w/bSjKCOIACg1TSqyeS+kuTQzMHeCwiSLpWm9zrFd0Cb OUcEBFJcNOT9TsG2tJAlQ+Au62zgpqRY5K5MvDJtRQ8zPImP48FD5NPQbsJRKfr0Zvp4 Y2kcNmmzwyqxg5slF7/TECAzZgIjh5tG7cY189Myu9MsZbiI/7nV+rpHhdNpomsNCD1k CMVA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id yd14si2005695ejb.245.2021.06.10.20.03.15; Thu, 10 Jun 2021 20:03:39 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230483AbhFKDCo (ORCPT + 99 others); Thu, 10 Jun 2021 23:02:44 -0400 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:55624 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230001AbhFKDCm (ORCPT ); Thu, 10 Jun 2021 23:02:42 -0400 Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 15B2xgZD025772; Fri, 11 Jun 2021 04:59:42 +0200 Date: Fri, 11 Jun 2021 04:59:42 +0200 From: Willy Tarreau To: Toke =?iso-8859-1?Q?H=F8iland-J=F8rgensen?= Cc: Shuah Khan , Steven Rostedt , Laurent Pinchart , 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 Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off Message-ID: <20210611025942.GE25638@1wt.eu> References: <5038827c-463f-232d-4dec-da56c71089bd@metux.net> <20210610182318.jrxe3avfhkqq7xqn@nitro.local> <20210610152633.7e4a7304@oasis.local.home> <37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org> <87tum5uyrq.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87tum5uyrq.fsf@toke.dk> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 11, 2021 at 12:43:05AM +0200, Toke H?iland-J?rgensen wrote: > Shuah Khan 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. Just my two cents, Willy