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

Aaron Parecki <aaron@parecki.com> Wed, 23 November 2022 15:21 UTC

Return-Path: <aaron@parecki.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 25B71C14CEE8 for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 07:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=parecki.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 fJx_-A-cb3yX for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 07:21:24 -0800 (PST)
Received: from mail-vk1-xa34.google.com (mail-vk1-xa34.google.com [IPv6:2607:f8b0:4864:20::a34]) (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 37DC6C14CEE3 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 07:21:24 -0800 (PST)
Received: by mail-vk1-xa34.google.com with SMTP id s204so8877107vkb.3 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 07:21:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki.com; s=google; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ILMKehovo06lpq7lKSoy69IwDosMgtDIKaoJeROPEE8=; b=S2Ov5rAcLv4biLvh2mi2dxfyzxZgg2gitftckOachDJYs/m1DbYdvwLVaj1VVr4vHZ G5q5xL0KTMPuYjqX9LfP9KjbLbJvqAg3joZreRPRL7VaOwGXtG9wq31ETOiJmDi1lkvH to8WCZwCwx79NiwJC2DiSC8ArelvzOOpKB8xAw4tLi1uLfu1B/gLk5Aj2UN2FAwWTK/B YxOwZwtu5y719RqJy2qR8n+UmYOhkJjJHtIhZnYMxgiKp8qhrLax+uWdj6kvFjAX0PEf oRoudYiAW6ADIReLUvKcYKEINRNG3PuvlqjJpeL9dmijvsvbsMbAVJhTsIK2/5P03kH8 /whg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=ILMKehovo06lpq7lKSoy69IwDosMgtDIKaoJeROPEE8=; b=zjBnse5WlLA1Ti87hpnS5dh3OxdpUsdLkZiw3qYdqkBcWIe4/09xvwjIRufgxDaWsX frRHfJ4bwcxaxHOXfp8/5OoS2oYA4uSVau0GfELTKfDJfwN548G5EAbe94ilJ78Ae1kh vPH4zlelawnnvmqtJHPGYqzrblDBr8FpQj8u3nMaM1GChNXmGkmoxSUNwutilRgxnKed VsdhEp8VUpQmHb1/n5Jlm7ytkUk5FbzogaKdqS9WyNUY4zjwYEpp6PteEj/isCzobr8Q QUDZySSm8GLe8yZhrTyRoTaovkuJ3e5nD9rN4LkWTt08DFk7bd8+NJlqN0votzDU+w18 0a4w==
X-Gm-Message-State: ANoB5pk87B2UFwoYymHuucA14ZWX7HatXWDRWwl+acZwaMReY5jp/D6T pSjLviBp0pZkBhU657vweyts/DebdHl+2Q==
X-Google-Smtp-Source: AA0mqf5nbNdEY/rLuVmFDcYzIZVSvknzkkeHuTsHuoPaJ3zdccCoCvWjUniWORtCCRRDm2UBaoliQg==
X-Received: by 2002:a05:6122:1217:b0:3a9:e4b9:c03e with SMTP id v23-20020a056122121700b003a9e4b9c03emr6586927vkc.0.1669216882412; Wed, 23 Nov 2022 07:21:22 -0800 (PST)
Received: from mail-vs1-f51.google.com (mail-vs1-f51.google.com. [209.85.217.51]) by smtp.gmail.com with ESMTPSA id f84-20020a1f3857000000b003a31fd43853sm2442881vka.3.2022.11.23.07.21.21 for <wgchairs@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Nov 2022 07:21:21 -0800 (PST)
Received: by mail-vs1-f51.google.com with SMTP id m4so17749765vsc.6 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 07:21:21 -0800 (PST)
X-Received: by 2002:a67:fd19:0:b0:398:6504:9ece with SMTP id f25-20020a67fd19000000b0039865049ecemr5479706vsr.16.1669216881043; Wed, 23 Nov 2022 07:21:21 -0800 (PST)
MIME-Version: 1.0
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie> <bea920d0-feba-2007-67b3-6af1b485d322@joelhalpern.com>
In-Reply-To: <bea920d0-feba-2007-67b3-6af1b485d322@joelhalpern.com>
From: Aaron Parecki <aaron@parecki.com>
Date: Wed, 23 Nov 2022 07:21:10 -0800
X-Gmail-Original-Message-ID: <CAGBSGjo9460n9_VXRtzcdrb6Yx_N5e3GZCuPOwjygpYtbozzHw@mail.gmail.com>
Message-ID: <CAGBSGjo9460n9_VXRtzcdrb6Yx_N5e3GZCuPOwjygpYtbozzHw@mail.gmail.com>
Subject: Re: mic lines not working as well as they used to...
To: Working Group Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003f6f7505ee24d7f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/Py_Fh5hj_Kax3iLDtB6lGVeN_DA>
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 15:21:28 -0000

As an in-person participant, I found it quite straightforward to add myself
to the queue with meetecho lite, and I appreciate the unified in-room and
virtual queue. I would not want to change that. I also appreciated being
able to remain seated until I was called up.

As a new chair, I appreciated having participants' names visible so that I
can more quickly learn names of people in the group.

If anything, what's missing is a way to highlight on the screen the name of
the person speaking at the microphone, similar to how you can always see
the name of the remote person speaking. (In practice, I noticed a mix of
people/chairs removing the person from the queue when they got to the mic,
so their name was no longer visible while speaking.)

Aaron



On Wed, Nov 23, 2022 at 7:08 AM Joel Halpern <jmh@joelhalpern.com> wrote:

> I don't think we can stop requiring the use of the queue, as otherwise
> including remote participants becomes very difficult.
>
> Having said that, maybe there are other changes that can be made to
> address the important issue that we do want discussion of topics at the
> mike.  That is generally why we are having the meeting sessions.
>
> At one point, the plenary used a dual-queue approach where comments on
> the current topic could come forward before folks who wanted to raise
> another issue.  I don't know quite how to represent that with the
> tooling, or how to make it timely enough to be effective, but I wonder
> if something like that could be helpful?
>
> Yours,
>
> Joel
>
> On 11/23/2022 10:02 AM, Stephen Farrell 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.
>
>