Re: [Ietf-hub-boston] Future meeting schedule
Kyle Rose <krose@krose.org> Mon, 04 November 2019 18:33 UTC
Return-Path: <krose@krose.org>
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 7F6091200FE for <ietf-hub-boston@ietfa.amsl.com>; Mon, 4 Nov 2019 10:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=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 (1024-bit key) header.d=krose.org
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 BfIzQUpizvNg for <ietf-hub-boston@ietfa.amsl.com>; Mon, 4 Nov 2019 10:33:36 -0800 (PST)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 5594A120019 for <ietf-hub-boston@ietf.org>; Mon, 4 Nov 2019 10:33:36 -0800 (PST)
Received: by mail-yb1-xb33.google.com with SMTP id g38so7904433ybe.11 for <ietf-hub-boston@ietf.org>; Mon, 04 Nov 2019 10:33:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O5ek9O79VvMPVJHhG0WxReJyLd9h4n3VhE+NiswFaPI=; b=qoSAllOilmZ4MCDaxGgooNhW5USnY/f9+z+f2mWTTjqUfZi2kTDXTA/sx1mr7B0MYO UoSK+265lkkWGaBZfG/HKI66dUV1VXZhKV1VMVzPsxMq6lrv6OpKbG/csuH4pkWj6I4E 4bHIUpAQblnVZg254CKNwBKcGX02k6Y6awKe4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O5ek9O79VvMPVJHhG0WxReJyLd9h4n3VhE+NiswFaPI=; b=jV4XqpHAVDLGlHrcaxPhSQSkxi3xInIVAZz2F4u+u+bMMTv0mockWcQOAdx1B2H9G6 gPlqp8xp7c4WCZfM9vjL7jHVnqXU+jpzK/qP7fzQ6ca12iztOj7PUiNvMotZpbkc++gS AxdSJqu1sCuQttoupDse/PJe8flzMQ8PC1gGFDw25GVdV+GWpAIiiSiDSTv+vFprx8qB D4EtqQmNGrkzYtYCg6UIfDps8rKMMu+UUlOVTW48coywg2z3WaKDi5qGaFrysCVHJsdK hEOQA3OwExIHMrk5WCMeJt09dSjjV23HPnrroqj5cU/CJsP6zPx2tdzSwyJg+5FQ9735 NeWw==
X-Gm-Message-State: APjAAAVaLdm+MGWmuHFXz5BwO9BH0NFtjkmJskWA1ZKRuQuomMXs635i BjsiHPtAVjBRBtEOzZg3YLZBS1O74CBzs8oTzKJ1USWOpuI=
X-Google-Smtp-Source: APXvYqx6lVfGNZs5ntxPItCW1f0C3CH/6gzx06GPVH6xLCt6OqsAAz0zHP2iX0z94jt4wC+gT+PrpsrCrDxYCBZVB+M=
X-Received: by 2002:a25:ac8:: with SMTP id 191mr2904165ybk.396.1572892415212; Mon, 04 Nov 2019 10:33:35 -0800 (PST)
MIME-Version: 1.0
References: <CAA=duU0-CiQx+cHBRPhd+J5Y608D23Se1L0kb+0wgec4mUwBrA@mail.gmail.com> <9DDCECC2-6B92-4D8C-8465-D1D134469832@fugue.com>
In-Reply-To: <9DDCECC2-6B92-4D8C-8465-D1D134469832@fugue.com>
From: Kyle Rose <krose@krose.org>
Date: Mon, 04 Nov 2019 13:33:24 -0500
Message-ID: <CAJU8_nW9YB4mZBkaRNsLgE9A8=awrDksVRZVrScu0R9iKdam8Q@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: "Andrew G. Malis" <agmalis@gmail.com>, ietf-hub-boston@ietf.org, "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="000000000000add1e70596898d4a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-hub-boston/h2JQezlgb1hSVwZRz_QdfPDuRKc>
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 18:33:38 -0000
I agree, mostly because I think we benefit greatly from informal discussion. The hour and a half we spent talking about the IETF leadership at the last meeting was eye-opening, and IMO would have been even better with more folks in attendance sharing their perspectives. On Mon, Nov 4, 2019 at 10:03 AM Ted Lemon <mellon@fugue.com> wrote: > 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 > > _______________________________________________ > Ietf-hub-boston mailing list > Ietf-hub-boston@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-hub-boston >
- [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