Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp6944pxj; Thu, 10 Jun 2021 13:07:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy9pEPeBCVP8U7X7J6pcQ8r9qcgXBZ+ECSNjaJfUmlyG+ZwAjru+h+Dsjo8yhRgUtTLWp1v X-Received: by 2002:a17:906:394:: with SMTP id b20mr307335eja.108.1623355623151; Thu, 10 Jun 2021 13:07:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623355623; cv=none; d=google.com; s=arc-20160816; b=ntm/hyfcCJ6IyxFNyiAu1OvCpyTOHAav3KPMNYduhOfai1YDRlxifcz7vV/96fJ6xt 3tNGrMNSa45kKK2GamEDigvZRr88iHkv/k0P0z0O19cWSCHZmR+1DRIu9aSMG/2hh9hF TmCZFLMJ0oajwV+E+YdToNESRl9FFxBzZ/trQd/Xez66X+M3gyt2WIQlEmo79i+CBSfZ hSaucU/xgfsKXAlSIYNsdJZq6RHPDgn+gQExToKf757w1l44CTCi3bsCjPqv7ysXbqHd Hmr0OmRobguK9/sfyMn1UvKfME637Dsf93EKL8VqSsOjUxyM0X3X0Olj+ZIulvbEzJLD BB7Q== 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; bh=nD0Pu6QW6T90aKG1qKavepOMtyrVTr/1XLXO702KRAM=; b=YGvaCrTTcoBhjBJgCXhUFZhlKlDzfn35AICdJBzbeTyo1Sv6MSUnoX8DpV3kEQvJGO uMUikKbVu4hSL86jbWQgLmfVi8uAtenxqWDTGZ9ZM3Hs7WecLCma8Q5CUW5L5eDjMUWz +6HTuO7eVU0mE+qEYwTCeqV2ocjpUAlOhxn/eH4KtW3IWACRiwcLchucknGU+/UrQAKD 4YxzvJcYT+26EEdY5ZZC0fUBvtv5G7uLd7KOs1PZ+rfvK027OremET1H8LJX5WLYmlEe V58AIWXJwXjS6aceQjEFplmgfQJ433Za77QOSMMJwPSXb153shtR/YEDUsMf7uBE2Dy+ gnxQ== 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 j18si3026737edj.276.2021.06.10.13.06.15; Thu, 10 Jun 2021 13:07:03 -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 S230366AbhFJUEq (ORCPT + 99 others); Thu, 10 Jun 2021 16:04:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:37888 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229963AbhFJUEp (ORCPT ); Thu, 10 Jun 2021 16:04:45 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BCB4D6136D; Thu, 10 Jun 2021 20:02:47 +0000 (UTC) Date: Thu, 10 Jun 2021 16:02:46 -0400 From: Steven Rostedt To: Shuah Khan Cc: 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: <20210610160246.13722775@oasis.local.home> 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-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 10 Jun 2021 13:55:23 -0600 Shuah Khan wrote: > 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. I have no problem with the above suggestion, and I envision that this may be the norm going forward. What is still missing is the interactions of the hallway track and the evening events. I was thinking about how we could get the remote folks in on what happened there right afterward, which is why I'm suggesting breakout rooms like Laurent suggested as well, but at the end of the conference, and perhaps the conversations of the previous night could continue with a remote presence. -- Steve