Re: mic lines not working as well as they used to...

Barry Leiba <barryleiba@computer.org> Wed, 23 November 2022 16:01 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F167C1522C3 for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 08:01:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llQ9wE73yf48 for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 08:01:46 -0800 (PST)
Received: from mail-ej1-f41.google.com (mail-ej1-f41.google.com [209.85.218.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DF9BC1522B0 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 08:01:10 -0800 (PST)
Received: by mail-ej1-f41.google.com with SMTP id e27so3628930ejc.12 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 08:01:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=BZQ+tbjP50s6ucfemTMvCwLQRo3iTPhkqaLpcZCy648=; b=2k/hjdCI5giWaikWwZ9NnWeCd7JkfWbaAyZUxAdYUeUmoft3sAQnwdz+I4upyu2WOw kjBDMaDQh7+o0ZcLOWTH8FlVqOc2tYY4AwWi+SAZdMvaZ69zWvP2arAW9LQkQJ7yJneS 0Me1bsMhETdn0EQDUQb8ILxbBKb4hLCu1VmbaVoFLyx7eNJXuQuM/FkTPAkvlgdkAFQl v/YqP55GbFIf9d+K9cCgZDHY+r5Fnkb68Jw0Pcnz46TAU39DRuyFBg/D1lfK6hoGA3ri 8LSAqWuz600TRCh9bAXaUNjmtf3LLbdbj4E09iiCyxu343EL4n//ESNbPcSSBEJT7e/q nazA==
X-Gm-Message-State: ANoB5pnmfYYoqB0O5C91Ahyf3yQmeqVZQO2Qn66U27aMe2CkUmM0fC30 jSwM3GErcopmlyAXxr+HSWObPRgiFmckkJnjXEmODN+8
X-Google-Smtp-Source: AA0mqf7KO30jZjqwvNttJv0xyExv12IQYgFr5ITi1KpJtS9nX0YNDs6rQqmWhk6kCAgepm6YTqMyz+dGUd0AB2aaPPI=
X-Received: by 2002:a17:906:e2c5:b0:7b7:90e0:f63b with SMTP id gr5-20020a170906e2c500b007b790e0f63bmr9176594ejb.749.1669219268325; Wed, 23 Nov 2022 08:01:08 -0800 (PST)
MIME-Version: 1.0
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie> <CAJU8_nV_4z36Wm-b28CQY6ZW3dY6WxfX+nNA0a__+J3Zqt0xZg@mail.gmail.com>
In-Reply-To: <CAJU8_nV_4z36Wm-b28CQY6ZW3dY6WxfX+nNA0a__+J3Zqt0xZg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 23 Nov 2022 16:00:56 +0000
Message-ID: <CALaySJJ9Ptt0x=C4GrDoCnJ5fhhDk7vOgYR8md1jbqQr86wbvw@mail.gmail.com>
Subject: Re: mic lines not working as well as they used to...
To: Kyle Rose <krose@krose.org>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Working Group Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/FF3mttFG2M6AUDQrWjxk68RI0s8>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2022 16:01:48 -0000

I very strongly agree with Kyle here.

In addition, I'll note that I was in multiple working group sessions where:
- The participation is relatively small anyway.
- There were several instances of extended back-and-forth discussion
in the room.
- The chairs allowed it without requiring every interaction to enter
the queue, and they watched the remote queue.
- When a remote participant raised a hand, the chairs made sure to put
them at the mic promptly.

To me, that's working well.  When there's a larger group with larger
mic queues and remote people in the queue, it really is necessary to
be somewhat more rigid, though not absolutely so.  Chairs exercise
judgment, while keeping remote participants in mind.

Barry

On Wed, Nov 23, 2022 at 10:48 AM Kyle Rose <krose@krose.org> wrote:
>
> One big benefit of the virtual queue for everyone, local and remote, is not having to figure out what someone's name is after they've unintelligibly mumbled it. This alone justifies making the change permanent, IMO.
> But just stepping back from minutiae for a second, a requirement to join a virtual queue seems like literally the least attendees can do to make the experience marginally better for remote attendees. Literally the least. Making remote participation more viable will do more for inclusion than any other change the IETF has made or is likely to make.
>
> I'll add that it's unclear that we have enough information to know why people aren't having extended discussions in mic lines, or even if that is true in the first place. (I did not observe this in my WG, for instance.) Behavioral changes resulting from 2 years spent in greater social isolation seems to be at least as likely a cause given the zero evidence I have for either hypothesis.
>
> Kyle
>
>