Re: limiting our set of cities

Christian Hopps <> Thu, 20 February 2020 14:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9A59C1200D5 for <>; Thu, 20 Feb 2020 06:13:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Tea5JwOZ0FJK for <>; Thu, 20 Feb 2020 06:13:58 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 13CD112003E for <>; Thu, 20 Feb 2020 06:13:58 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by (Postfix) with ESMTPSA id 86DA560B79; Thu, 20 Feb 2020 14:13:57 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
Subject: Re: limiting our set of cities
From: Christian Hopps <>
In-Reply-To: <>
Date: Thu, 20 Feb 2020 09:13:56 -0500
Cc: Christian Hopps <>,
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <17764.1582194882@dooku> <> <> <>
To: Keith Moore <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Feb 2020 14:14:00 -0000

> On Feb 20, 2020, at 8:17 AM, Keith Moore <> wrote:
> On 2/20/20 7:46 AM, Christian Hopps wrote:
>> I think that we should pick the top 12-16 locations that participants are from, then for each destination prior to it being considered we calculate the travel PAIN (cost + time) for that set of participants.
> Why favor participants from large cities?   It's not like they're representative of the whole group.

By trying to make it easier for the most people, of course it's going to be helping areas with the most people. The point is to obtain a list of sites to measure travel cost and time from.

> Also, different participants have different ideas of pain.

I think it's reasonable to equate "painful" with travel time and cost. Do we really want people who love to travel and couldn't care less where we go to be diluting the "pain pool" for the measurement? That doesn't work well towards minimizing pain for everyone else that it does impact.

> A fairer method would be to poll every participant about their preferences for future meeting cities, then for each meeting, pick N polled participants at random from those who have attended the last M meetings (locally or remotely), and select from the cities show up in their preference lists.

Ok as long as N is large and M is reasonable. But making N large is just going to skew to large metro areas being heavily represented anyway. *shrug*


> Keith