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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 25 November 2020 22:59 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 CC3AD3A1F3E for <manycouches@ietfa.amsl.com>; Wed, 25 Nov 2020 14:59:16 -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 F2gyDlzZLgCi for <manycouches@ietfa.amsl.com>; Wed, 25 Nov 2020 14:59:15 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06C633A1F3A for <manycouches@ietf.org>; Wed, 25 Nov 2020 14:59:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C44B7389E9; Wed, 25 Nov 2020 18:00:36 -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 MesEjVXsE7YP; Wed, 25 Nov 2020 18:00:36 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 313CA389E8; Wed, 25 Nov 2020 18:00:36 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 91BEC66B; Wed, 25 Nov 2020 17:59:12 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>, "manycouches@ietf.org" <manycouches@ietf.org>
In-Reply-To: <1558268049.4567.1606130331589@appsuite-gw2.open-xchange.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> <32537.1605850657@localhost> <4554.1606103230@localhost> <1558268049.4567.1606130331589@appsuite-gw2.open-xchange.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: Wed, 25 Nov 2020 17:59:12 -0500
Message-ID: <13602.1606345152@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/8KLik50BD2oSjKzsU8-yjYpMX54>
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: Wed, 25 Nov 2020 22:59:17 -0000

Vittorio Bertola <vittorio.bertola@open-xchange.com> wrote:
    >> Il 23/11/2020 04:47 Michael Richardson <mcr+ietf@sandelman.ca> ha scritto:
    >>
    >> I was mostly successful in managing my time zones, but I couldn't stay awake
    >> past 1400UTC (9AM), having gotten up around 2000UTC (3PM) the previous day.
    >> Friday, I knew I was going to be a write-off, and it was.
    >> Maybe I should have found a hotel room.  Saturday was also mostly a write-off.
    >>
    >> I'm sure that I'm not the only one who needed recovery time after this "travel"
    >> The question is: how can we, when we write the schedule, make this really
    >> clear to managers?  (many of whom probably didn't notice the "UTC" on the schedule)

    > I don't think you can change the perception of the time commitment just
    > by mangling the appearance of the schedule - either the people around
    > you get it, ot they don't.  Unfortunately, for physical meetings in
    > remote locations, everyone understands that travel and jetlag recovery
    > time is necessary, but it's not the same if you stay home and "only"
    > wake up and go to sleep at "weird" times.

Yes, so we really really need to fix this expectation from employers that
remote meetings are not travel.

    > In my case, the IETF meeting happened 6am-noon every day; this involved
    > a very early wakeup, but in no way it would allow me not to work until
    > 6pm as usual (even later if necessary), not to have dinner at home at
    > "regular" times, and so on.  Last Monday, for example, I was booked as
    > a panelist in a session of the U.N. Internet Governance Forum (which
    > was held in parallel in CET) scheduled at 6:20-7:30pm my time.

I'm sorry to hear of that experience.

    > So, basically, "remote IETF" just meant up-to-14-hour-long working
    > days, definitely less productive than usual, for a week - and I don't
    > see any easy way to avoid this, except getting back to physical
    > meetings.

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