[Ietf-hub-boston] Future meeting schedule
worley@ariadne.com (Dale R. Worley) Mon, 04 November 2019 00:18 UTC
Return-Path: <worley@alum.mit.edu>
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 E25F012006E for <ietf-hub-boston@ietfa.amsl.com>; Sun, 3 Nov 2019 16:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level:
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 Iv--afFUpQSA for <ietf-hub-boston@ietfa.amsl.com>; Sun, 3 Nov 2019 16:18:07 -0800 (PST)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DFE812003E for <ietf-hub-boston@ietf.org>; Sun, 3 Nov 2019 16:18:07 -0800 (PST)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-07v.sys.comcast.net with ESMTP id RPMXiBfDhgoPqRQ4LioinF; Mon, 04 Nov 2019 00:18:05 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1572826685; bh=OLkHvyjgr/dgX0yaf3H+khxH7Jnqh/TL7kt91PYRBfc=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=NHS53L8FsDTGagoC2fVnvsRFG00zvXqNQtA8gqjIzO15mfOS276a+fAgqNkplMbhe 15mtiNv/NUq16Bcmosu/P+8co/dWIe/2frFf0hQSUXPYttsfwyCEm5gwl3RKP6PiLX zgk0FpEjWEujjW5DvS5YJiTf/80DSBpb/dCW4BkbXJq8xfMkrRbAffPlwT4yeNVh+5 N/Py4trxE47UymV/AsnoYRYUFXVfvSYJmWc8xbfdSxD1W8FFXxVpfZvzs3bN5pIaMf eGkJDFHuQI2+266AjPr9CzwFqPRFGDulxqktPsWQtqx8225xoJZSSoNX7QgLPXyRep kTIPdRDseMHXQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-07v.sys.comcast.net with ESMTPA id RQ4KiGRJ71rYrRQ4Li4xNZ; Mon, 04 Nov 2019 00:18:05 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id xA40IZXf021210 for <ietf-hub-boston@ietf.org>; Sun, 3 Nov 2019 19:18:35 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id xA40IYg7021205; Sun, 3 Nov 2019 19:18:34 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: ietf-hub-boston@ietf.org
Sender: worley@ariadne.com
Date: Sun, 03 Nov 2019 19:18:34 -0500
Message-ID: <8736f4a3z9.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-hub-boston/dG8dp6mDEQkyl9rsag72NhB_j9s>
Subject: [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 00:18:09 -0000
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] Future meeting schedule Dale R. Worley
- Re: [Ietf-hub-boston] Future meeting schedule Andrew G. Malis
- Re: [Ietf-hub-boston] Future meeting schedule Ted Lemon
- Re: [Ietf-hub-boston] Future meeting schedule Kyle Rose
- Re: [Ietf-hub-boston] Future meeting schedule Dave Lawrence
- Re: [Ietf-hub-boston] Future meeting schedule Kyle Rose
- Re: [Ietf-hub-boston] Future meeting schedule Dave Lawrence
- Re: [Ietf-hub-boston] Future meeting schedule John C Klensin
- [Ietf-hub-boston] The October health of the IETF … John C Klensin
- Re: [Ietf-hub-boston] Future meeting schedule Salz, Rich
- Re: [Ietf-hub-boston] The October health of the I… Dave Lawrence
- Re: [Ietf-hub-boston] The October health of the I… John C Klensin
- Re: [Ietf-hub-boston] Future meeting schedule Dale R. Worley
- Re: [Ietf-hub-boston] Future meeting schedule Dale R. Worley
- Re: [Ietf-hub-boston] Future meeting schedule Dean Bogdanovic
- Re: [Ietf-hub-boston] Future meeting schedule Ted Lemon