Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp413496pxj; Fri, 11 Jun 2021 02:15:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwhEUmzIrzfp8y9HT9orfV+31VHjT0hdhAHM2rii0jDBxJtK/IkEWE9YWM/7tNbzDL6CfTQ X-Received: by 2002:a05:6402:204:: with SMTP id t4mr2669988edv.34.1623402926515; Fri, 11 Jun 2021 02:15:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623402926; cv=none; d=google.com; s=arc-20160816; b=tYPgvY4gSe8zVgR0xqdfqk5iYK2vy/yq9xbt1llNCh23sdd7Lqk/JA6byQvrV7OiZ/ 8ihHRLv2RPprSJyrK/jLbefxfh9Fr/vgoL3VBRcVLNZhsS1G3Llx/IdQDTSufXUxm3Ei B0AU+vDffZw3FjwO/O6of1OU0DgofTRF6SL0ypnItif6jg3Gsjsj4VDb+qVHSXPQIGGC p0PF3x4FXj41hKpPXwhCFokcvVDTvwb3r0Kh/2NkLgVRwbn8aALdU6CNhXWF5ekIkPCM o7ADPoe009se0I5DYRRkD5x+xBjkoNmPkXrdyasTACd0Cz2wCw0/fZY4CNpElEB3uoG2 BNNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=Z/q1KqfiSk3RA511Rd9/7Hr7U6kPSI7L82v9DDkCQkQ=; b=dxfKx+sMnixEx/TqOg5Vlk4X18GTiUCT0werzK/kAoVTlCp8GWEEmLr4vWFo41/7cS JpCTiT1Mglaz6NaNc0aAYI5xd9b0qqhgcs7kOAvMf0wILdg3UeDw2U+RowV83DkhIQLK AbBUkPD+AiQ4PAboZrayJv1cpSshp83pLFBDKeouMXvjESX0zQxEPW78uL6UhXkCTSsN NM/zVJ+lqp5upk0MPCFAGl7ZEq9jJURyKS8bfJ7sbhwTRU4Ba9CRHfHnqEazsmwWrUJ8 SBLQUI/u9JVp5WEHQyPxcGYM+SkQJ9OF93sqP9/y1bllvzd+uTbYkpLYnHBSCZdI22H3 Cf8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=qCE0A2hE; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bx23si4656355ejc.736.2021.06.11.02.15.03; Fri, 11 Jun 2021 02:15:26 -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=@kernel.org header.s=k20201202 header.b=qCE0A2hE; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231314AbhFKJPN (ORCPT + 99 others); Fri, 11 Jun 2021 05:15:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:35134 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231609AbhFKJPM (ORCPT ); Fri, 11 Jun 2021 05:15:12 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id E431D60FDA; Fri, 11 Jun 2021 09:13:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623402794; bh=0Tv6dk09LYXtiWu3+YyS09NcTBZcnmopruN7Ttw2A3c=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=qCE0A2hE5eLvV8SAX8VsVaLsmx7G+YhwHIGuIbtiETIq98w68vFvtv3s1bhzDjAJ1 zAwEklDt1RkuJy4xO1mhyVGn5CoqoCJlfqGcOzbWGGdCb/cl21ED/qg6om4QDr6Qgw hAsXyCGbL1jtQZUE1mmW8Fz57Pe8pBJAijmfw+8qSkasiv7gs8Bn4yv5Nf3uQnoBiX zxb7Zjkljrgndxxd99Pyb9NRcFNuEpikSsPzNHA+8Ye4WGjHy7LoVAmriVbgeAzAuX sIG1CoqZMtlY/m4KJAESInsxp1yQtkOqy6u3nFjtUmy8jmmfx5n/O/lOLN4k8Jv3p4 6ODFKkgxpj1ug== Date: Fri, 11 Jun 2021 11:13:07 +0200 From: Mauro Carvalho Chehab To: Willy Tarreau Cc: Toke =?UTF-8?B?SMO4aWxhbmQtSsO4cmdlbnNlbg==?= , 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: <20210611111248.250e6da8@coco.lan> In-Reply-To: <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> <20210611025942.GE25638@1wt.eu> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Fri, 11 Jun 2021 04:59:42 +0200 Willy Tarreau escreveu: > On Fri, Jun 11, 2021 at 12:43:05AM +0200, Toke H=C3=B8iland-J=C3=B8rgense= n wrote: > > Shuah Khan writes: =20 > > > 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 ena= ble > > > 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. = =20 > >=20 > > 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 :) =20 >=20 > 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. >=20 > 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