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

Toerless Eckert <tte@cs.fau.de> Wed, 23 November 2022 22:31 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 A5E89C14CEE1 for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 14:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level:
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 zf2-I9LSwg-Z for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 14:31:46 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 C9D21C14F74F for <wgchairs@ietf.org>; Wed, 23 Nov 2022 14:31:46 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 2F754548632; Wed, 23 Nov 2022 23:31:42 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 18AB54EC0E8; Wed, 23 Nov 2022 23:31:42 +0100 (CET)
Date: Wed, 23 Nov 2022 23:31:42 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Working Group Chairs <wgchairs@ietf.org>
Subject: Re: mic lines not working as well as they used to...
Message-ID: <Y36fTv6PWNxSc9gy@faui48e.informatik.uni-erlangen.de>
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/hs-n9mK9ykoFHvdJYms5HdjUWeY>
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 22:31:48 -0000

This time around i had a case where i was patiently waiting on the microphone
line in a WG room for probably 10 minutes and then was simply asked by the remote
chair to step away because i had forgotten to put myself into the virtual queue.

In that chairs defense, i do not know if he could see the physical microphone line
in the room or not, but the delegate in the room also just did not say anthing,
so i could not participate in the discussion. I have seen this situation being
handled a lot more friendly in other WGs though. So there is definitely a
lot of freedom today already for WG chairs to either be sticklers to the rules
or to foster a collegial discussion atmosphere. My compromise as a WG chair
is to allow each person on the local microphone ONCE in a meeting to have missed
getting into the virtual line for example.

With that and similar experiences, i'd say its certainly an issue we struggle with.

I am very much a fan of the virtual queue given how i too never
understand peoples names when being mumbled at the microphone. Alas i do not
find the meetecho lite to be particularily easy to use tool on the mobile phone.

An actual app might help to avoid having to click through ietf web pages and typing
in login information repeatedly to use meetecho lite. At least that's what troubles
me with the phone option currently.

An nfc reader attached to the microphone in the room line would even be better.
You just pass by with whatever registered NFC you have, then you see your name
pop up on the room screen and e voila. Could have the NFC on your badge
holder. Good reason to re-use badge-holders across IETFs and avoid the waste.

Cheers
    Toerless

On Wed, Nov 23, 2022 at 03:02:27PM +0000, 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.