Re: [Mtgvenue] Was Brisbane a success to be repeated ?

Jay Daley <exec-director@ietf.org> Tue, 26 March 2024 09:48 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84B71C151553 for <mtgvenue@ietfa.amsl.com>; Tue, 26 Mar 2024 02:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=staff-ietf-org.20230601.gappssmtp.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 h_71n1xxYjpe for <mtgvenue@ietfa.amsl.com>; Tue, 26 Mar 2024 02:48:45 -0700 (PDT)
Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (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 AB615C15154E for <mtgvenue@ietf.org>; Tue, 26 Mar 2024 02:48:45 -0700 (PDT)
Received: by mail-wr1-x442.google.com with SMTP id ffacd0b85a97d-341b9f6fb2eso2601357f8f.2 for <mtgvenue@ietf.org>; Tue, 26 Mar 2024 02:48:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1711446523; x=1712051323; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=psuSvqFmJg6VmOlw9B2HvHicjjLQmNdbA2NopcKrwNo=; b=e4/UvoDxrUmop6PDWllzJAbPtGMCSPP1wVYGjJosu8rs0oP986LCH+NH1VsEdgFTzY OB8iseqkvRK5a7TWcfmJhkYAVRieKsqlfIxoK1f5Keu4Io5yc7MhJXlyhMNEREuwGBZH VSrmHpwdShFfxAtXFa+vKfX9sLQI0cg7aTzrmaeFgFd0nqeHZTM9stFyQWyNNj2MSIL7 cjwrLRfePNs8vSrS3vObGxZyTcnaixeCDm0Is1THHAEfa29Gm4DcUgAbbMwVa9dQQ1or YIck8nfHejsL7XgjysPWWLHRalVK9R2FDe1WtylnoKFOPBLIoFLB0A2ZjI0DzhOQaS/L vTbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711446523; x=1712051323; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=psuSvqFmJg6VmOlw9B2HvHicjjLQmNdbA2NopcKrwNo=; b=koTDiXY1WJCqWMv1Fm/geO3CTJ+ClVndyH392U3P8FzE1EPo/O2jfCpPkzTFmZUZjC RbBvWm/G8ioAAsP19KnDEPlBBseUmOVwa97Cs7qs60SxtSy+DW9bSTrd93upSLBaM3xi dVl1vm4CsUv3Qx7wUPNojUeg+W9h/R8vev//Lw5WEI6+TupjcyzZCgymf8FNKUzhfwV+ 2o9brjUu5o72AxisQtQ3BylLRXwnzGADMAVU1NynQlFEP940JNwTDAAHZX3VKVNT7r3B PiSuBfJn20SYE3yaPv0N8qpBarKm2GXaPVDzqZEezWAFPGKQwr6S25JpbcPnzbLGoo56 OkjQ==
X-Gm-Message-State: AOJu0YzgCkS3QLbdq2GDkgFFLna1/EXQ7AkLeyS1DKVPUnz9X4D7KPqI WlVOjZZQs5pVaY0/PRqY67TUsWNDm8o9U9spxbP7u/AMovbuOSBgA2duf+NF3CafUrAvmJlquzG k/ZPZk3CF
X-Google-Smtp-Source: AGHT+IHZPas6bu9Cz8h1gSGlK35DMUoKtdsT6t/TcYzQbuoMSzYUdkYlm+krbnEgIuGE/qv1N93J3A==
X-Received: by 2002:a5d:4d03:0:b0:33e:c070:9574 with SMTP id z3-20020a5d4d03000000b0033ec0709574mr7127832wrt.20.1711446523444; Tue, 26 Mar 2024 02:48:43 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id y17-20020adff151000000b0033e43756d11sm11696413wro.85.2024.03.26.02.48.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Mar 2024 02:48:43 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <ZgCdcWGzgESGxj8v@faui48e.informatik.uni-erlangen.de>
Date: Tue, 26 Mar 2024 09:48:32 +0000
Cc: mtgvenue@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <17E5FCB6-4ECD-4F65-BBD1-9D31F34166DA@ietf.org>
References: <ZgCdcWGzgESGxj8v@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/rNPU50zOXfz0so4m6Gip6Fdiuhs>
Subject: Re: [Mtgvenue] Was Brisbane a success to be repeated ?
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for email discussion of the IETF meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2024 09:48:49 -0000

Hi Toerless

> On 24 Mar 2024, at 21:38, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> Sorry if subject question was asked and answered elswhere/earlier, please
> provide pointers to summary thereof. If not:
> 
> Who will atually determine if Brisbane was a success to be repeted, and if so how ?

There are multiple evaluations after a meeting, and as these are basically independent of each other I can only speak about the administrative evaluation.  This evaluation has a number of parts to it:

- Financial.  It should be noted that we went into this with a budgeted deficit and so the evaluation is not about surplus/deficit but about how close to budget it was.  Of course, if it was financially better than budget then that is a bonus.  it can take several months, sometimes over a year for the actual costs of a meeting to be known, if we have local tax compliance to address.  We have only recently published final financial statements for the 2022 meetings, and are still working on those from 2023.  We hope to have a draft financial statement for Brisbane in a few months.

- Satisfaction.  As you know, we survey meeting participants with questions on a wide range of meeting features and we publish a blog post with the results of those surveys that show a comparison with previous meetings.  The goal is for a consistent upward trend of satisfaction and considerable effort is put into achieving that by changing the meeting experience in response to the feedback received.

- Operations.  While this is not something that participants see directly, there are many operational factors that are evaluated after the meeting, including the support from the venue, any incidents, the quality of the AV team, food management and so on.

One other things the LLC is doing here, is collecting data that can be used by the community and/or community leadership to evaluate a meeting.  For example, a few people asserted that this meeting had a lower level participation from civil society because of the cost of travel, and so we have added questions to the post-meeting survey that will enable this assertion to be tested once we have the data from a few meetings.

> 
> I guess it comes down to some type of evaluating whether it managed to
> pull in participants that otherwise would not go to other IETF in person;

I don’t think that it does.  Experience of exploratory meetings has shown that much more needs to happen around the meeting if this is to a goal, much of which is out of the scope of the IETF (e.g. a planned local outreach program).  This is more about spreading the pain. 

> and to an extend that justifies the lack of all the participants that did not
> come - but that would have come to other alternative locations) due to long and expensive travel.
> 
> I answered the post-meeting survey but did not think it had enough questions to
> help figuring out answeres to these questions. Especially did i not see a survey
> for those people who did not make it to Brisbane (e.g.: sent to ietf@ietf.org)
> and would like to chime in to the evaluation.

The survey does go to people who participated remotely, so this survey only excludes those that did not participate at all.  We ask those that participated remotely if they would have participated onsite and why they didn’t, with cost as one of the options.

We have a separate survey under development for people who cease participating in meetings to see why they did that. 

> 
> Btw: I very much enjoyed Brisbane, but i was privileged in having to fly in only
> from a location (SFO) that had a direct connection of <= 14 hours, whereas colleagues
> from further east in the Americas and of course in Europe did report total travel
> times even in excess of 30 hours. And i also managed to attach vacations to make
> the travel very much worthwhile. And i do collaborate a lot with folks from east asia,
> who of course also had a good presence.
> 
> That's especially why i would like to understand best how much effort the IETF puts into
> deciding for this type of locations

This meeting followed the process for an exploratory meeting in RFC 8719 - someone proposed Australia to the list, there was a discussion and the IETF Chair called consensus.  The role of the LLC/Secretariat here was to choose the city.

> and especially how it will justify it to those for
> whom it was inacceptable due to these travel issues.

I don’t think any justification is needed - every single venue we could/do choose will exclude/hinder some people.  That is just a matter of fact and one that has been discussed extensively in the context of visas.  Where would need to justify decisions, is if the same set of people are always excluded/hindered.

cheers
Jay 

> 
> Thanks a lot for any insights!
>    Toerless
> 
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org