Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp11962pxj; Thu, 10 Jun 2021 13:16:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJydmu2S9khjmCbO95lYvT7uBpKbEGY6sfr4ivcpb1F3lv0MXmRF4A+Xw9XVHkrtrtRFH3ny X-Received: by 2002:a17:906:2c52:: with SMTP id f18mr319135ejh.258.1623356178265; Thu, 10 Jun 2021 13:16:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623356178; cv=none; d=google.com; s=arc-20160816; b=QRd7hufTJdRbV0PgrmMmHr6gxaop7H8sn+6pvKiCHMTvWHe1Dbpep1ZGMCxm2x6SnP CmeikwrGfbCR6lvzS8z27E2mq6UxZ+VyEytzH+HdFVHv/KqtkJR2aAnVg312Jp4kqS9M sorZzyzKzuzmMjeUlTHrSwmkI6OF4e1kQywK26/G8lMmxq5xZ+zfuX8i2B+uczuwION4 7T+xEGFN7MEgiauufQna2ImyG/s4qiPMapt5fMU7ltwzZdWPAB6U8Z84UQVda8qS8dbY 92DCmY0E/fNHjdJ/D7jfuBIrgn9GQ0gc/UpqrpABz/Mwv4Tme9dr/e2lYFfFe7XbsffH B1jQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=KND7DoY/09NzlHDGlCKkV1pirvEJ2hmpAejnVKY3Dhc=; b=WwtBDWgKZ93Ze6ru4AUEBomWzKl43wIHNt66vkuohEytllkqYRy1s/ZmblYUxxQuOV xqyBRjh8kY2Dq7mgiKwMqAbqGaVyEvlk5ZE0V5akgHovY1Z98Q2ZUVzkqULdrjZM6qF4 Y279XJfvh6kp/rrqfpZ1ahdjrNofP9kyBo8MtFY1QqorpQxyoHjRjLRdh2M/ddC0zgXL w1xkXLeSUgN33dP3yw6/S9X2QSYf6aMa8we9mAUqaukHnfviTqZRdBpCytkvvcaWooOV McKnELQsXyYdSOcB7ZNlN6Y8QsGO7zCAZV2m1MWCO4UJNOwqxEpSOr+CBP6u9bzwBm0R 9ONQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=google header.b=a+kj5hpo; 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=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id aq5si114926ejc.411.2021.06.10.13.15.28; Thu, 10 Jun 2021 13:16:18 -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=@linuxfoundation.org header.s=google header.b=a+kj5hpo; 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=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230130AbhFJUPq (ORCPT + 99 others); Thu, 10 Jun 2021 16:15:46 -0400 Received: from mail-qk1-f182.google.com ([209.85.222.182]:33778 "EHLO mail-qk1-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229941AbhFJUPp (ORCPT ); Thu, 10 Jun 2021 16:15:45 -0400 Received: by mail-qk1-f182.google.com with SMTP id c9so2356036qkm.0 for ; Thu, 10 Jun 2021 13:13:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=KND7DoY/09NzlHDGlCKkV1pirvEJ2hmpAejnVKY3Dhc=; b=a+kj5hpoDoIiocT8sQb4ui2hitct/vz3LCP0HlE1h6aTQr3F/X6y/t5I6nME0j9QIX BkMnFIY3Y3zcXUGpx9lxPm62SPk6b9/C67aYWoB4kHQ3D+7VAAeNFSLICUOOGXF3iEcv ESIwss4AW/PpYGkSdtOfey1/zCc5sY9k/3Row= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=KND7DoY/09NzlHDGlCKkV1pirvEJ2hmpAejnVKY3Dhc=; b=KzBNF8VuUAR8uP6An2yUO6YTEvNCzJSrN27W+2AzNlk7W2R5kl206lwSopQR6VeWbu itXdv6MR6s+b5Vk92qNUhsKEASdjwcJbv2FceHxVEeE9o018qxbN20Dk9J6LfpTjO9O4 bQ8vkCOobs6E1mU5PhATXLGUKWErVfJOJvPhWW8W2GAd+ZynCWu4I3p4cpUajkLZmHhh nO2WmivzufArz6wvniH5CusNaJKNR2TnyXRdnXYK6u5tB9r7vPCxX7lUKAXupdnoybWI mgdSGE2DBjtnAhVxGKe15N05XnjXtAIGWO3IJ58DHt3KGR85kcYQPfHPhW7t5PWKV3lY FuqQ== X-Gm-Message-State: AOAM530Ig/a5D98bRwNuHc/EWi1j2eTF9NhoWBHfO4CAbJ99FIZFBnap 0NnEVR8QcVGNqPVXvJvanX9134i789t8Y19+ X-Received: by 2002:a05:620a:1113:: with SMTP id o19mr347803qkk.229.1623355958654; Thu, 10 Jun 2021 13:12:38 -0700 (PDT) Received: from nitro.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id e128sm2890894qkd.127.2021.06.10.13.12.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Jun 2021 13:12:38 -0700 (PDT) Date: Thu, 10 Jun 2021 16:12:36 -0400 From: Konstantin Ryabitsev To: Laurent Pinchart Cc: ksummit@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off Message-ID: <20210610201236.gvxxmgl6ubjsbc3h@nitro.local> References: <5038827c-463f-232d-4dec-da56c71089bd@metux.net> <20210610182318.jrxe3avfhkqq7xqn@nitro.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (Trimming the huge CC list) On Thu, Jun 10, 2021 at 09:39:49PM +0300, Laurent Pinchart wrote: > The topic of how to best organize hybrid events to maximize > inclusiveness for remote participants is more interesting to me. LPC did > an amazing job last year with the fully remote setup, but a hybrid setup > brings new challenges. One issue I've previously experienced in hybrid > setups, especially for brainstorming-type discussions, was that on-site > attendees can very quickly break out conversations in small groups (it's > an issue for fully on-site events too). As a (high-functioning) introvert, I'd say that a lot of it depends not so much on the on-site/off-site nature of participation, but on individual communication preferences. I've presented quite a bit at conferences, and, to me, "brainstorming-type discussions" never really happen post-presentation, largely because being in a spotlight makes me uncomfortable and I generally try to slink away. I suggest that something that would help is providing information on where to ask questions in an informal setting. For example, add the following on the last slide of your presentation: Thank you! Join the discussion: 1. Mailing list: foo@lists.example.com 2. IRC: #foochan on exampleirc.com 3. Matrix: #foochan:example.com 4. My email: foo@example.com This gives enough options for folks to ask questions whether they are in the real-life audience or attending online. Listing both your individual email and a group chat option will help bridge many cultural divides -- some people will feel intimidated asking a question directly (especially if you are a luminary in your field) and will prefer to address a group. Others will feel intimidated addressing a group (what if my question is stupid) and will prefer to address you directly. > Session leads should be aware of the need to ensure even more than usual > that all speakers use microphones. I don't think we need to go as far as > specific training on these topics, but emphasizing the importance of > moderation would be useful in my opinion. I think with most sessions being recorded, people are already well conditioned to use microphones. I try to at least always repeat the question being asked if I notice that the person asking it isn't using a mic. > 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'm generally of the opinion that we should split conferences from hackathons, anyway. - conferences are great for finding about cool new things happening in your field, and work great online where there is no limit on how many people can join the stream; if the presentation is not what you thought it was going to be, switching to a different video stream is dramatically cheaper than getting out of the dark room to find a different presentation. - hackathons are great for getting things done and meeting up with folks you rarely get to see in real life -- and they work well as on-site, multi-site or hybrid events. For example, the maintainer summit is a "hackathon", even if there is no actual code hacking done. The thing being hackathoned is the development process itself and general direction of things. The LinuxCon is for sure a conference and generally has little tangible value other than a pretext to get your employer to pay for the trip. :) So, perhaps more frequent but smaller events around narrower topics as opposed to huge colocated events? I do appreciate that this is more difficult for organizers, but perhaps it would result in more tangible benefits? -K