Re: [Ietf-hub-boston] Future meeting schedule

Ted Lemon <mellon@fugue.com> Mon, 04 November 2019 15:02 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: ietf-hub-boston@ietfa.amsl.com
Delivered-To: ietf-hub-boston@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3ED1201E0 for <ietf-hub-boston@ietfa.amsl.com>; Mon, 4 Nov 2019 07:02:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OC_g7basdEaa for <ietf-hub-boston@ietfa.amsl.com>; Mon, 4 Nov 2019 07:02:47 -0800 (PST)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B14D9120130 for <ietf-hub-boston@ietf.org>; Mon, 4 Nov 2019 07:02:46 -0800 (PST)
Received: by mail-wr1-x435.google.com with SMTP id b3so11698554wrs.13 for <ietf-hub-boston@ietf.org>; Mon, 04 Nov 2019 07:02:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=e8fy3LaME0JibMu+jybAEW4SHN9y0fmfEQZc6ssKdSo=; b=SpMil+SiPIshhCSLSnXvikevt6Wus/0tlqJTwJG7+j6ka5OZuWZWuxnBXqtKbyzvmb YitxlYVkqXYMDP2ecS+X35zMd2wj07Xcp2fn8hm/g7hyRuR0wUuLpF1Wpz+wEx0oJbYn 4XU9eU6ZNSHHWy8oDI+5fcymgRrDz5tIV1FSyWcbAWemJanktoC2TEtgnu8imZd4kCQN ERl6A2pBnJMNtOY9iYmG/x2hQ/j1GdfkFS0pIxKnhNTEcCStlrdh08Iwvxy9YeiNREOg NV86isdRGNNqd6VvcWrupvimyzlJSvRHpfLgP1bIKrIgm3AjSqzpUFUrrvlY+QJ1OHfD C/iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=e8fy3LaME0JibMu+jybAEW4SHN9y0fmfEQZc6ssKdSo=; b=O5cklIVOdjWM2zsDrg+8KRoGvGnFDzx8GC69LtcpzOaqioeRGJ3EzoPrDmSxXhGMlv a/1YJWkT+caeWJKnB881Ja0tZQLTotYBYxfL6jENXP2HoDfz+5i12b3FQNc8Fjz3E8pp rMhtScGug3Otimda8ckHBp0n6Z/WfYupUNs0uDU51aIZm/6SoYFxC/MW5iaro/uyv7Qj B1MnYbatfu+WgoHmxjpVTo7Sb7Tz1zsWXHH193kpl5F1YsY0gCG37NuudXUoc+rEJYh4 3xXt+2caEwWy2NBpP52OqvaceP8pgFpD5THI6uR1qHYrqyflHCr/aQn/a8Jt5HVsw7BM b6eg==
X-Gm-Message-State: APjAAAU4TmZ8McUEakAHA3ePNHrcSb7R4Gr2URK/zO1Nym7IeE0VvsUM 6bnbgtqUZFfyND6OHuIqMmw/c5WyJNs=
X-Google-Smtp-Source: APXvYqzWuQDILzalSiMtRF2Qh7MfCX49hIz2zPItVGZJPI8JvvneEOHunCO8Stq/Cc0/hYtHx8Ta/g==
X-Received: by 2002:adf:f088:: with SMTP id n8mr13205389wro.115.1572879764877; Mon, 04 Nov 2019 07:02:44 -0800 (PST)
Received: from [10.10.172.7] (78.239.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch. [178.197.239.78]) by smtp.gmail.com with ESMTPSA id l4sm1247728wme.4.2019.11.04.07.02.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Nov 2019 07:02:43 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-5C79C996-05A8-45E7-9F62-AAF1EB9C4ED5"
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 04 Nov 2019 16:02:42 +0100
Message-Id: <9DDCECC2-6B92-4D8C-8465-D1D134469832@fugue.com>
References: <CAA=duU0-CiQx+cHBRPhd+J5Y608D23Se1L0kb+0wgec4mUwBrA@mail.gmail.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, ietf-hub-boston@ietf.org
In-Reply-To: <CAA=duU0-CiQx+cHBRPhd+J5Y608D23Se1L0kb+0wgec4mUwBrA@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: iPhone Mail (17B84)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-hub-boston/VNrq7PURX8ieh00xgqg_9C7Ss0E>
Subject: Re: [Ietf-hub-boston] Future meeting schedule
X-BeenThere: ietf-hub-boston@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "For IETFers in the Boston area." <ietf-hub-boston.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-hub-boston>, <mailto:ietf-hub-boston-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-hub-boston/>
List-Post: <mailto:ietf-hub-boston@ietf.org>
List-Help: <mailto:ietf-hub-boston-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-hub-boston>, <mailto:ietf-hub-boston-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 15:02:53 -0000

It might be good to answer the question ”why are we meeting“ first.   Otherwise it’s hard to know if this is the right amount. 

For my part, I’m actually more interested in low effort frequent meetings that not everyone gets to than high effort infrequent meetings that.. not everyone gets to. I’m not claiming that’s right, just sharing my impression. 

> On Nov 4, 2019, at 15:37, Andrew G. Malis <agmalis@gmail.com> wrote:
> 
> 
> Dale,
> 
> Sounds good to me.
> 
> Cheers,
> Andy
> 
> 
>> On Sun, Nov 3, 2019 at 7:18 PM Dale R. Worley <worley@ariadne.com> wrote:
>> What with the IETF meeting nearly upon us, it's a little early to
>> schedule the next Hub meeting.  But I've been thinking of principles to
>> get a regular meeting cycle going.  So far, I've come up with:
>> 
>> - three meetings a year, equidistant from the IETF meetings, i.e.,
>>   mid-January, mid-May, and Mid-September  (Probably put the mid-Jan
>>   meeting *after* MLK Day.)
>> 
>> - rotating among the three high-tech zones in metro Boston:  Kendall
>>   Square, Route 128 NW, and Route 495 NW (Are there other zones I've
>>   missed?)
>> 
>> - rotating among the three days of the week that seem to be the easiest
>>   for people:  Tuesday, Wednesday, and Thursday
>> 
>> The rotations help prevent people from being locked out if they have a
>> rigid commitment on a particular day of the week, or find one of the
>> zones inaccessible.
>> 
>> I think it's also important to get the dates of the meetings fixed well
>> in advance, as people can then construct the rest of their calendar
>> around the Hub meeting, rather than trying to put the Hub meeting among
>> scheduled things.  People seem better at dynamically adjusting where
>> they commute to than dynamically adjusting when events are.
>> 
>> Comments?
>> 
>> Dale
>> 
>> _______________________________________________
>> Ietf-hub-boston mailing list
>> Ietf-hub-boston@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-hub-boston
> _______________________________________________
> Ietf-hub-boston mailing list
> Ietf-hub-boston@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-hub-boston