Re: [Manycouches] many-fine-dinners --- a view on how to organize virtual meetings

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 20 November 2020 05:37 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACEE3A189F for <manycouches@ietfa.amsl.com>; Thu, 19 Nov 2020 21:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 BPDqn9ToIepo for <manycouches@ietfa.amsl.com>; Thu, 19 Nov 2020 21:37:39 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAE8F3A1870 for <manycouches@ietf.org>; Thu, 19 Nov 2020 21:37:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 670C238A11; Fri, 20 Nov 2020 00:38:40 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dHw4irEY0sA9; Fri, 20 Nov 2020 00:38:39 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C9C0A38A10; Fri, 20 Nov 2020 00:38:39 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B1AE6E7; Fri, 20 Nov 2020 00:37:37 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Martin Duke <martin.h.duke@gmail.com>, "manycouches@ietf.org" <manycouches@ietf.org>
In-Reply-To: <CAM4esxQdW2N=NAwgGpJKc3Q9xdyDRG1K-R=75vK7wi2tUO9btQ@mail.gmail.com>
References: <160288855079.14008.13967692974159638979@ietfa.amsl.com> <30344.1602894208@localhost> <FD995870-E9C6-4099-93AF-253F0A11F56B@tzi.org> <CADaq8jcKK5kUvU3v7+6gEaeqjqxtw-Bii5is_hoq1ugogCoWPg@mail.gmail.com> <20201017193610.GA39170@kduck.mit.edu> <12526.1602980594@localhost> <2f99a293-b2b1-498f-36af-36fd201e9e8d@joelhalpern.com> <15451.1603056956@localhost> <2a305ee7-7511-f74d-fd7b-93ff8641c451@joelhalpern.com> <17295.1603123341@localhost> <228dbe14-2362-7374-bf1c-768c6ada7a3f@joelhalpern.com> <5926.1603128427@localhost> <a11e38fd-7d21-112c-fbe9-dc4b699ca5fe@joelhalpern.com> <13688.1604619321@localhost> <E441A975-F3E0-4011-86E5-AAC7494EBE31@cisco.com> <CAM4esxQdW2N=NAwgGpJKc3Q9xdyDRG1K-R=75vK7wi2tUO9btQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 20 Nov 2020 00:37:37 -0500
Message-ID: <32537.1605850657@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/9IPNFSaFP1oXIwH89oA9e9V1iRs>
Subject: Re: [Manycouches] many-fine-dinners --- a view on how to organize virtual meetings
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2020 05:37:42 -0000

Thank you for your comments.
While there are a number of people who attend only 1 WG, aside from so-called
busy-bodies like me, there is also the entire IESG, IAB.

If our meeting structure breaks our management people, then we all lose.

Martin Duke <martin.h.duke@gmail.com> wrote:
    > 3. *Longer days*: The IESG's consensus is that more than 6 hours of
    > videoconferencing is tough on the body under any circumstances, especially
    > when it's the graveyard shift for many people.  Furthermore, I believe that
    > people have a harder time filtering out their everyday life constraints
    > when at home, and so a longer day is particularly onerous.

I agree. I am not really proposing longer days.
I am proposing simpler days.

    > 4. *More days*: This would increase the true cost to employers, compared to
    > an in-person meeting, if it were any more than about 7 working days. I
    > believe, without any evidence, that holding sessions over the weekend would
    > be a non-starter for participation.

So I wrote "4-7 days", for two reasons:
  1) because we have 7 day physical meetings, and maybe someone wants to push.
  2) because we might want to pad the actual schedule so that people would
  have some recovery time.  This is consistent with people claiming travel time.

    > 5. *More interim meetings*: the near-universal interim start time of ~1500
    > UTC makes a lot of inherently discriminatory assumptions about what time
    > zones have the most important contributors and what hours are optimal for
    > any particular time zone. If we were to have regular virtual IETFs without
    > a canceled location as a timebase, using a random start time would be
    > better than optimizing for the Atlantic. That said, sometimes WGs enter a
    > phase where they're in the weeds, tourists are not that helpful, and indeed
    > entirely theoretical anyway. For these groups, interims are currently
    > available but I don't think we should be in the business of actively
    > encouraging interims for the reasons above.

I don't really understand this paragraph at all.

    > Furthermore, in many ways "have an 11am meeting every day for a month" is
    > more onerous than just blocking out a week. As the intended purpose of more
    > interims is to encourage more tourism in meeting week, this amounts to one
    > busy week followed by 1 month of daily meetings. I found this IETF 107
    > model to be far more disruptive than the alternatives.

I didn't like IETF107 format either, btw.

    > All this said, fewer conflicts are good! To me, the most promising avenue
    > is shortening sessions and placing restrictions on how many you can
    > request, a forcing function to reduce status reports and non-interactive
    > presentations, and instead focus on issues that require live-action
    > discussion. Of course, one of the big requests we got between 108 and 109
    > was "longer sessions", so your mileage may vary.

Yes, because people actually need the face time to sort things out.
It's not like we use physical in-person well.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide