IETF Logo Mail Archive

Re: Feedback from IETF 120 Vancouver post-meeting survey

Wes Hardaker <wjhns1@hardakers.net> Mon, 02 September 2024 22:04 UTC

Return-Path: <wjhns1@hardakers.net>
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 2C5A6C14F6BC for <wgchairs@ietfa.amsl.com>; Mon, 2 Sep 2024 15:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (1024-bit key) header.d=hardakers.net
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 8Z1COXUw3Eys for <wgchairs@ietfa.amsl.com>; Mon, 2 Sep 2024 15:04:07 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33C2EC14F699 for <wgchairs@ietf.org>; Mon, 2 Sep 2024 15:04:07 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (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 mail.hardakers.net (Postfix) with ESMTPSA id C276F2179F; Mon, 2 Sep 2024 15:04:05 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net C276F2179F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1725314645; bh=2336eXiw+91dUpwGuh5eTuUiZbbIPxvanaI68H9F1iY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=HgYb05QIz7stJcC3+kQLX4gQoopgN4LBh1rAWc0PyBZYy01i1bgJ5iCvVbsKFu24g HEhct9bgXsg430F8sk9dx8bf9ekkNNSIqSR3iExDVNG/nYD3RJ3QBeKyb/gMew3A+J rNngXtg7Ugy8TA796n0K5Pclf3xUZDEsV2g6+Cf8=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Wouters <paul@nohats.ca>
Subject: Re: Feedback from IETF 120 Vancouver post-meeting survey
In-Reply-To: <cf22ba70-330a-a912-f838-3010fa423f6e@nohats.ca> (Paul Wouters's message of "Mon, 2 Sep 2024 14:50:44 -0400 (EDT)")
References: <7487E6AA-A8BE-42A9-9E80-F85C49ABF026@ietf.org> <CAHbuEH72xCnM6_F+A+jP3nPkNY2sHa_zG4Skbhdu40SBgXSdcA@mail.gmail.com> <cf22ba70-330a-a912-f838-3010fa423f6e@nohats.ca>
Date: Mon, 02 Sep 2024 15:04:05 -0700
Message-ID: <ybl5xrdpvai.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: 6SXTTHYYZD5YJDNJCFTR364T5LVEEZYI
X-Message-ID-Hash: 6SXTTHYYZD5YJDNJCFTR364T5LVEEZYI
X-MailFrom: wjhns1@hardakers.net
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/E11jU0q7U8Xdg_az0YKyWFf86Xg>
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>

Paul Wouters <paul@nohats.ca> writes:

> However, those engaged in the chat are missing what the meeting has
> moved on to.

One other "moved on to" example is that people wanted to keep talking
about the last presentation and frequently carry on when the agenda
itself has moved on.  It always seems like the chat is "one topic
behind" because of that, and makes me wonder if everyone is actually
following the new topic as well.

-- 
Wes Hardaker
USC/ISI

v2.40.4 | Report a Bug | By Email | System Status