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

Vittorio Bertola <vittorio.bertola@open-xchange.com> Mon, 23 November 2020 11:18 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
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 D1B453A07D1 for <manycouches@ietfa.amsl.com>; Mon, 23 Nov 2020 03:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (2048-bit key) header.d=open-xchange.com
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 GdE6rhN2iIMa for <manycouches@ietfa.amsl.com>; Mon, 23 Nov 2020 03:18:55 -0800 (PST)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 B08663A07DE for <manycouches@ietf.org>; Mon, 23 Nov 2020 03:18:54 -0800 (PST)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPS id B86E26A275; Mon, 23 Nov 2020 12:18:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1606130331; bh=+aDrLRcbuTb4cGKjJ/peR18NC+jZG5OrYvi+i+7T5/U=; h=Date:From:To:In-Reply-To:References:Subject:From; b=d2/mEPKYin4iRWaMTpfmS4z/rkZE1EwrIjF2Q92mrRozipGKYVDWPcSaLc6mkm7bi Vw58KuSfM/qM5gilfThx1JNIGPsjTK19/IwPfaTEJEcBQ6+rWu0GGcJHSckSKkvHij gTmKSLNN+2Wkatm3td6r00QOS6RtlvZ9XS3U5QPRXC77bbsm7CEwGykO96KzzOE04x CGIrN0YDYiEGY5LFCIP2ntdLokuUSGwr5uOnQdMhAYdfVfwdjfyb42tbEPJKui8f7G c2flGPMuCN0DgC7UByANOM2z9d/u59m9r3qQEgxJiob1fVqK/WCJ0eRLBjnk9eYM3k +jsBiv5SFXRNg==
Received: from appsuite-gw2.open-xchange.com (appsuite-gw2.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id A9CE63C044B; Mon, 23 Nov 2020 12:18:51 +0100 (CET)
Date: Mon, 23 Nov 2020 12:18:51 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "manycouches@ietf.org" <manycouches@ietf.org>
Message-ID: <1558268049.4567.1606130331589@appsuite-gw2.open-xchange.com>
In-Reply-To: <4554.1606103230@localhost>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.4-Rev14
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/uaKG3ZZc-daWeZre1oxTBGL1dtk>
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: Mon, 23 Nov 2020 11:18:57 -0000


> 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. 

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.  

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.

-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy