Re: [119all] Result of the IETF 119 Brisbane post-meeting survey

Christian Hopps <chopps@chopps.org> Sun, 14 April 2024 11:23 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85378C14F61C; Sun, 14 Apr 2024 04:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] 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 jlkiqoPOVx-h; Sun, 14 Apr 2024 04:23:13 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 98268C14F618; Sun, 14 Apr 2024 04:23:13 -0700 (PDT)
Received: from smtpclient.apple (unknown [172.222.91.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 0365A7D00B; Sun, 14 Apr 2024 11:23:12 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: [119all] Result of the IETF 119 Brisbane post-meeting survey
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <1E1EF642-93B7-4245-B702-839B850AB369@ietf.org>
Date: Sun, 14 Apr 2024 07:23:02 -0400
Cc: Christian Hopps <chopps@chopps.org>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <15323534-6E6F-4EC8-954B-9BB6207EDF4C@chopps.org>
References: <DC6C12FF-601C-4180-9FD1-4A1589531113@ietf.org> <m2y19iinsy.fsf@ja.int.chopps.org> <B6F57D48-8E9E-409A-BD26-3706F102188B@ietf.org> <27F155AC-9B10-4FAD-ABE6-ACD79769B571@chopps.org> <1E1EF642-93B7-4245-B702-839B850AB369@ietf.org>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q_RVL_13_Yd7_3Oe-Lj8CaE2vKo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Apr 2024 11:23:15 -0000


> On Apr 14, 2024, at 07:13, Jay Daley <exec-director@ietf.org> wrote:
> 
> 
> 
>> On 14 Apr 2024, at 11:00, Christian Hopps <chopps@chopps.org> wrote:
>> 
>> 
>> 
>>> On Apr 14, 2024, at 05:37, Jay Daley <exec-director@ietf.org> wrote:
>>> 
>>> Hi Chris
>>> 
>>>> On 12 Apr 2024, at 16:16, Christian Hopps <chopps@chopps.org> wrote:
>>> 
>>>> ** On remote attendance:
>>>> 
>>>> Attendance in Brisbane Australia was down to 66% that of Prague and forced remote attendance (would have attended but couldn't fund) increased to 75% from 60%.
>>>> 
>>>> I think these results should definitely be made (more?) obvious so the community can make sure that it agrees with the IETF's choices for locations for meetings -- that we are enabling people to attend in person vs. placing barriers to the same.
>>> 
>>> The meeting policy, BCP 226 RFC 8178, explicitly states the following:
>>> 
>>> "We meet in different global locations, in order to spread the difficulty and cost of travel among active participants, balancing travel time and expense across participants based in various regions."
>>> 
>>> So yes, there will be times when some people find it much easier to attend and others find it much harder.  The question is not how to prevent that, we can’t, it is whether or not this is being done fairly given the geographic distribution of participants.   A 24 year gap between meetings in Australia seems fair.
>> 
>> I'm not saying it won't seem fair; however, not showing the data encourages biased speculation. I think we should show this data after every meeting, not just this last one; it will also show sites that are particularly effective.
> 
> I agree that this is a good measure of "pain" and worth plotting over time but "particularly effective" - how so?  Without knowing for sure, it seems to me that the effectiveness of a meeting is much more complex than this and I’m not sure anyone understands it well enough to identify all the dimensions to measure. 

The context here is on-site participation vs forced/unwanted remote participation, and so "particularly effective" was meant in that context not in some broader one. To be explicit "particularly effective at enabling on-site participation (and not hindering it)".

Thanks,
Chris.

> 
> The data you highlight might be a proxy for effectiveness but I doubt it.  One key indicator  in the survey that may possibly serve as a proxy for effectiveness to a limited degree, is the overall satisfaction score and that is clearly highlighted.  
> 
> Jay
> 
> -- 
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org