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

Kyle Rose <krose@krose.org> Wed, 23 November 2022 22:59 UTC

Return-Path: <krose@krose.org>
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 899AAC14CF14 for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 14:59:02 -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_DNSWL_NONE=-0.0001, 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 (1024-bit key) header.d=krose.org
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 AsHE2BPTa_jK for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 14:58:58 -0800 (PST)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 7B64CC14F74F for <wgchairs@ietf.org>; Wed, 23 Nov 2022 14:58:58 -0800 (PST)
Received: by mail-wr1-x430.google.com with SMTP id x5so27575335wrt.7 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 14:58:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kd6YnA4RO7D6bCjVzE5uBDtCGgwiMxQsVv37PniOxsA=; b=fn7JURj/1/R9brrQhJsAZGJXrUVtn6cxccMjMnww4dFhLzStRlmz3HPA3YtGZIWTR+ l3yMhwNoQ7h2z3Mq8BAEB7vdThl2xW0BfCnpmLQJxiByL0dPYUu3Svj+CKa7KSje5/ib 4zvjvuRrtQYOXYSjB+WkJd0iSsecPmAxk1MEU=
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=kd6YnA4RO7D6bCjVzE5uBDtCGgwiMxQsVv37PniOxsA=; b=TuEyxZSPJXNswBzFjWRcI/HC9X4qDHvFEwCVQS/1kfu9eEtX4mKyNwU/QhFUzm5dX6 0K+AndVSQBasYx+jW3EDSuTvBZgyPg4e4Kc1dOtu26LgHhAyBvC1lAiv4v454NMkyQ1f pBbto0k2XimxdWXBq37TsluvZQvO6ZGGKQkHtwoT56g3SWLMZRiXT9uXVHl6Vl9SjL74 PzUC/2DNgvZmph5g3z90IUtnzF8HkehdlCuQTqCO/WiW0zC0Cf3qmoEosmIIjlHHK2Am yV5pSMVo1u7zo7bJstoROI6VVNCJZv+6MMOb4YPCnHMJbN3B7k9ZyrOaNTdVvrYAk6Me S6PA==
X-Gm-Message-State: ANoB5pnYMCssiRf2tvKyp9nK4iSi6gUEYWHdWDIHECEjzX8Qwe22Ih7u Mfg33g952p2yllouKEXf9/uqUMc9/dcRER/wP8U/jg==
X-Google-Smtp-Source: AA0mqf4/f7ryudOvn0oPgE+TeODifwFkncAevH1oyvghslyaWRBxntGZgR3XQxkFAvaty+38b83qd+Jv8IuBnu0CUiw=
X-Received: by 2002:a5d:6389:0:b0:241:c5fe:f78a with SMTP id p9-20020a5d6389000000b00241c5fef78amr14730285wru.144.1669244336602; Wed, 23 Nov 2022 14:58:56 -0800 (PST)
MIME-Version: 1.0
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie> <Y36fTv6PWNxSc9gy@faui48e.informatik.uni-erlangen.de> <BYAPR11MB2757064A799D4AE792AE9E9DC20C9@BYAPR11MB2757.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB2757064A799D4AE792AE9E9DC20C9@BYAPR11MB2757.namprd11.prod.outlook.com>
From: Kyle Rose <krose@krose.org>
Date: Wed, 23 Nov 2022 17:58:47 -0500
Message-ID: <CAJU8_nX+9PiTHv_wiXfN1UWf4_WUCNNgbAq29PJDzoxfKEByxg@mail.gmail.com>
Subject: Re: mic lines not working as well as they used to...
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Cc: Toerless Eckert <tte@cs.fau.de>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Working Group Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ba159e05ee2b3b48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/iS14HpEPXAaZUA3k-X6PD8WQY0I>
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:59:02 -0000

There is no way I would pay the on-site fee without all the benefits of
being in-person. (Hell, I've even considered staying on-site but paying the
remote fee, and just avoiding the meeting rooms because the actual value
isn't in sitting in the same conference rooms with other attendees during
working group sessions.)

Kyle

On Wed, Nov 23, 2022, 5:53 PM Acee Lindem (acee) <acee=
40cisco.com@dmarc.ietf.org> wrote:

> Given the significant effort to normalize the on-site vs remote
> participation experience, perhaps the IETF should have the same (or very
> nearly the same) registration fee for both types of participation.
>
>
>
> Thanks,
>
> Acee
>
>
>
> *From: *WGChairs <wgchairs-bounces@ietf.org> on behalf of Toerless Eckert
> <tte@cs.fau.de>
> *Date: *Wednesday, November 23, 2022 at 5:32 PM
> *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...
>
> 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.
>