MIME-Version: 1.0
References: <8736f4a3z9.fsf@hobgoblin.ariadne.com>
In-Reply-To: <8736f4a3z9.fsf@hobgoblin.ariadne.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 4 Nov 2019 09:36:51 -0500
Message-ID: <CAA=duU0-CiQx+cHBRPhd+J5Y608D23Se1L0kb+0wgec4mUwBrA@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: ietf-hub-boston@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c03f070596863f58"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-hub-boston/xlXW5iqM4HmZ_vVfx3Ny1zcaewE>
Subject: Re: [Ietf-hub-boston] Future meeting schedule
Precedence: list

--000000000000c03f070596863f58
Content-Type: text/plain; charset="UTF-8"

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
>

--000000000000c03f070596863f58
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dale,<div><br></div><div>Sounds good to me.</div><div><br>=
</div><div>Cheers,</div><div>Andy</div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Nov 3, 2019 =
at 7:18 PM Dale R. Worley &lt;<a href=3D"mailto:worley@ariadne.com">worley@=
ariadne.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">What with the IETF meeting nearly upon us, it&#39;s a little ear=
ly to<br>
schedule the next Hub meeting.=C2=A0 But I&#39;ve been thinking of principl=
es to<br>
get a regular meeting cycle going.=C2=A0 So far, I&#39;ve come up with:<br>
<br>
- three meetings a year, equidistant from the IETF meetings, i.e.,<br>
=C2=A0 mid-January, mid-May, and Mid-September=C2=A0 (Probably put the mid-=
Jan<br>
=C2=A0 meeting *after* MLK Day.)<br>
<br>
- rotating among the three high-tech zones in metro Boston:=C2=A0 Kendall<b=
r>
=C2=A0 Square, Route 128 NW, and Route 495 NW (Are there other zones I&#39;=
ve<br>
=C2=A0 missed?)<br>
<br>
- rotating among the three days of the week that seem to be the easiest<br>
=C2=A0 for people:=C2=A0 Tuesday, Wednesday, and Thursday<br>
<br>
The rotations help prevent people from being locked out if they have a<br>
rigid commitment on a particular day of the week, or find one of the<br>
zones inaccessible.<br>
<br>
I think it&#39;s also important to get the dates of the meetings fixed well=
<br>
in advance, as people can then construct the rest of their calendar<br>
around the Hub meeting, rather than trying to put the Hub meeting among<br>
scheduled things.=C2=A0 People seem better at dynamically adjusting where<b=
r>
they commute to than dynamically adjusting when events are.<br>
<br>
Comments?<br>
<br>
Dale<br>
<br>
_______________________________________________<br>
Ietf-hub-boston mailing list<br>
<a href=3D"mailto:Ietf-hub-boston@ietf.org" target=3D"_blank">Ietf-hub-bost=
on@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf-hub-boston" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ietf-hub-=
boston</a><br>
</blockquote></div>

--000000000000c03f070596863f58--