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

"Andrew G. Malis" <agmalis@gmail.com> Wed, 23 November 2022 20:43 UTC

Return-Path: <agmalis@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 98E0FC14CEE1 for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 12:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GatFEzX1kvqj for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 12:43:23 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 96D27C14F740 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 12:43:23 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id g62so18394741pfb.10 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 12:43:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OddCpKGDrkXNxpWJ9y97nPrjUTgVekw0zrzCWnBEqNg=; b=EARtjmX8yBSGvnxkfanp70aBODA6jtwqRlko62+zwlJu+5K39Kk+QOhEQ1ALoAwa9z vrcmdF7PQXn9WzXxqNO7FSQayF5eWcVYY4mIV9vuzefzhlrgtJFA2XnibDeOD2Bb1y3X GaaTBJOSPsro/PEg6aOhjqkgFNj6D5BU/wmtQPjhw/b8portYmWrPFnNanR+KRlOn0EP NER5Je5kNYL9Tvslx5ggxR0Z/dwKMv8UWJSnq77vCJhkj3hXu9VDoKWNT+1OAope6lr9 Hp1ib63jLhDUsH3ojwkOhcxkUipFReDm6BnzTQ7dF5XBm+mcdZcDQ9BZClI4BknIxAW7 aTyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=OddCpKGDrkXNxpWJ9y97nPrjUTgVekw0zrzCWnBEqNg=; b=5NwakirGIBdKXEV4xZ3sRUE3ehSm+6dyNa/52V17O5OLzS/Ycf16mPcc2w70Yi2c2L bPdbtwYJjj5ZaPt3+9UauW0FVqBc1Kgu5iaj/2hYoVYWDzVQH3B9ivYFiSHlBc0zs7Bf DPQ3Z1MtF9PbU3Q2IpZwpDaLidGocp4URtaOXH0AiH7hTh4QutpQWSExWcxGE0c0DCkd qrwn2S1RTMsy6tBusgYAuP9MkKwbPbOGwG/RbwMD6RM8lz9o6AdNZRPeeXbQYWsJcWZD aQPFABGtLq+SZg6rm+wQFxbtKZJpA7ADBGmHpV10PMXGHodmAzJTh3VOPa1mACD1A/G/ jSzA==
X-Gm-Message-State: ANoB5plV4j5C6tnoMIk6p0HHCiF6slJX3niLODixBBhRO7y9vI7BYW86 NUZexNPtbvT91acbcku6o2Z7ZnqEb4znms6AX8NFneuv
X-Google-Smtp-Source: AA0mqf4IEpEU3GwmrXid7TaPup32xnUQAL5azbe4epGbQjnIgRoU0KxAeGOHZ4jA2Enh3yZlO6ydNkSBIQrSgSz8y4s=
X-Received: by 2002:aa7:8054:0:b0:56c:4303:a93d with SMTP id y20-20020aa78054000000b0056c4303a93dmr14823100pfm.73.1669236202975; Wed, 23 Nov 2022 12:43:22 -0800 (PST)
MIME-Version: 1.0
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie>
In-Reply-To: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 23 Nov 2022 15:43:05 -0500
Message-ID: <CAA=duU19_ifdTSt3FFAhy7xTHcZYV3fvH3DOK0GOB+Eo-EEhLw@mail.gmail.com>
Subject: Re: mic lines not working as well as they used to...
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Working Group Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ecb74505ee29567c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/M7T8wEuF6FHqa977FeqhkyzDD-4>
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 20:43:26 -0000

Stephen,

As a remote participant these days, I really appreciate the single queue.
As many have said, it's fair to everyone, and you can see the name of the
speaker. This is especially important when you're remote because the camera
being broadcast isn't always the one pointing at the person speaking at
that moment, and even when it is pointed at the speaker, you can't always
tell who it is.

The single queue also allows a remote chair if necessary, since it's
otherwise impossible to manage a line of standing people that you can't
see. :-)

Cheers,
Andy


On Wed, Nov 23, 2022 at 10:02 AM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> I think we're making a bit of a mistake in requiring people
> who are in the room at meetings to join the meetecho queue
> before they join the physical mic line. It's not an end of
> the world thing, but I think it is a bit damaging.
>
> The results of what we've done this year seem to me to be
> that:
>
> - fewer people join mic lines overall
> - there's almost no real discussion of topics raised
>    at the mic as there used be
>
> I realise that being fair to remote participants needs to
> be a hard requirement, but I think we've gone a bit too far
> and ought back off some, e.g. to where we encourage but
> don't require people (whether remote or in-person) to join
> the meetecho queue. I think we ought also encourage more
> discussion at the mic (for both remote and in-person folks)
> and not be so fixated on the order in which people appeared
> in the meetecho queue. That requires a bit more chairing
> but that's why we're supposedly at the front of the room.
>
> But, maybe others like the current rigid setup or haven't
> found the lack of mic-line discussion a problem?
>
> Cheers,
> S.
>