Re: [Ext] Feedback from IETF 120 Vancouver post-meeting survey

Tim Wicinski <tjw.ietf@gmail.com> Mon, 02 September 2024 17:16 UTC

Return-Path: <tjw.ietf@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 88DFFC151553 for <wgchairs@ietfa.amsl.com>; Mon, 2 Sep 2024 10:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=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 VBacTBbw-xsY for <wgchairs@ietfa.amsl.com>; Mon, 2 Sep 2024 10:16:39 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF056C151556 for <wgchairs@ietf.org>; Mon, 2 Sep 2024 10:16:39 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5c24c92f699so2154056a12.2 for <wgchairs@ietf.org>; Mon, 02 Sep 2024 10:16:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725297398; x=1725902198; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=O0hoyuyzNhcOKsLmkjm6InC1T2O+Q+TzCgThoNBEQJ8=; b=bKC0lkkKXcmeO5vmVY9t3y3uHuGLQsT3uRI+DIwcTV3ChPgl79Z7PmyLVljl/YC4Mz u6Rd6zQ3+u3OZqHVWGGpmn/TCQyxsPhGopSJ6pZVjrbI2V5u/1x2q4JvGRd3orFCim2e 405u67uofXEppGnMcP+9Hj3Lf5NkbEH89ByqvuD+f1eeM/Zufx3u7XwgC5BYMCzwsdzU S7UQxXAHTKjGd2cOMB5PnKh4dN7uRC9jiPTx8iCYGx0ZSdwgwI1Uic887JBIpPCuhNSF TWEzAUovgLQDSO3UdRwLolP/b9Gk5Tcu0YRhOkzHNN7fAcOYslTCDH6k7iXnBvWNWqH8 3neQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725297398; x=1725902198; 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=O0hoyuyzNhcOKsLmkjm6InC1T2O+Q+TzCgThoNBEQJ8=; b=mRPcmashKOD7reUQpo4I3J8yVRj1hg1IMg+E85MKF24mntkm56HRZwYa/9jNozu9qd 5t7RCMLoyU3RIdcXPMEmpPihBVO2wRKWGIealdB9X/MPwK1c2Cxh+hwsqDbNQl0T04tk 3Qg1ORCwWkozIfG4sbCO0Rs5Ayf7JxgpLIxB8+bU7p2VslWV8GfjyJYaFw4m2Jik8NL9 nfnZTd79jRkkc8ccOt4YNu+6l93zCrToECAELT7ecROoyqrhmbgIjQyDQTc3gXOWHXIV CEPZE70Hv3lTroyQp5msjFXB4mqpQFvvKbxd/HFWcJxP+10JpJJlw7JpETU3ppA7CDQG qc9A==
X-Gm-Message-State: AOJu0YylOpE1TIUHmHJ4lJ00UMS6PxQmtW8TISZXX8cb2G2PnN7pcuu1 gg5YWftOoF7sd9z1SlWZcmnLVSe7DhykO70SbXV5O6v6kbupn/d9U+hg1LIkqgBeoP1Urm85nAm hjjmNZ9tJ4L3GyE0ZXxTUekztQliMwqNE
X-Google-Smtp-Source: AGHT+IGA8T6buLU7jKTzcsTCKT0Afooo8A7Yn3/0G82j+E3UFcJ2nL8zniQ+mIRNMzA5lwq76KdSmudEnZ7kkrHBA18=
X-Received: by 2002:a05:6402:2102:b0:5c2:5075:7d1 with SMTP id 4fb4d7f45d1cf-5c250750b1dmr4071708a12.7.1725297397310; Mon, 02 Sep 2024 10:16:37 -0700 (PDT)
MIME-Version: 1.0
References: <7487E6AA-A8BE-42A9-9E80-F85C49ABF026@ietf.org> <CAHbuEH72xCnM6_F+A+jP3nPkNY2sHa_zG4Skbhdu40SBgXSdcA@mail.gmail.com> <57DD1871-63C0-4884-8967-25DB8972A29B@icann.org> <9348.1725296895@obiwan.sandelman.ca>
In-Reply-To: <9348.1725296895@obiwan.sandelman.ca>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Mon, 02 Sep 2024 13:16:25 -0400
Message-ID: <CADyWQ+HL5TBzbuGjJYb2sr-cf6nMid_8HC9Xn6LN=rkYUqTVYA@mail.gmail.com>
Subject: Re: [Ext] Feedback from IETF 120 Vancouver post-meeting survey
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="0000000000007fac500621261a08"
Message-ID-Hash: 5G7FB56OLBOYUK7KPZXSVAWMJTN2ZYZH
X-Message-ID-Hash: 5G7FB56OLBOYUK7KPZXSVAWMJTN2ZYZH
X-MailFrom: tjw.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: wgchairs <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/yglKfBTWu0JS7p7p_0Ibr4mE8xA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

I am terrible at standing in the mic line so I can agree with Michael on
this.

Also, there is an oddity with the Zulip logs.  On the meeting material
pages, the link will send you the JSON blob:

https://datatracker.ietf.org/meeting/120/materials/chatlog-120-dnsop-202407251830-00

But I found (willing to bet Robert pointed it out to me) a much nicer
formatted version of the chat log:

https://datatracker.ietf.org/doc/chatlog-120-dnsop-202407221530/


tim


On Mon, Sep 2, 2024 at 1:09 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> I think that most WGs do a good job of having someone monitor the chat, and
> when things do need to get to mic, that happens.  Clarification questions,
> which can be answered by other people, are significantly useful.  Not only
> does it not take time away from the presenter, but it also might show
> whether
> the document has been reviewed, and by who.
>
> It would be useful if Jay could dig further into who complained, and which
> WGs for which this was a problem, and how new, middle or ?old? the people
> are.
>
> Secondly, going to the MIC can be a scary process; particularly for some
> neurodivegent people.  Asking the question in chat has a much lower bar.
>
> Finally, for those who are not physically present, the chat is a useful and
> significant way to connect to other participants.  For remote attendees,
> arranging windows in the right places is not hard.  I think that for many
> people, their "window manager" makes it hard for them to have any windows
> which aren't full screen, and frankly...<shuts up here>
> I think that it is the people who are trying to run meetecho on their
> laptop with the built-in client who are having problems.  The answer is to
> use the zulip web client.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
>