Re: [Manycouches] many-fine-dinners --- a view on how to organize virtual meetings
Michael Richardson <mcr+ietf@sandelman.ca> Mon, 23 November 2020 01:31 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 C2C2A3A1123 for <manycouches@ietfa.amsl.com>; Sun, 22 Nov 2020 17:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_BLOCKED=0.001, 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 ESs4TYzGn-z1 for <manycouches@ietfa.amsl.com>; Sun, 22 Nov 2020 17:31:54 -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 4BC5F3A1107 for <manycouches@ietf.org>; Sun, 22 Nov 2020 17:31:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id B456C389B6; Sun, 22 Nov 2020 20:33:04 -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 XfTaxbJyarhh; Sun, 22 Nov 2020 20:33:02 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id C6771389B5; Sun, 22 Nov 2020 20:33:02 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 12F307D; Sun, 22 Nov 2020 20:31:50 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "manycouches@ietf.org" <manycouches@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <E441A975-F3E0-4011-86E5-AAC7494EBE31@cisco.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>
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: Sun, 22 Nov 2020 20:31:50 -0500
Message-ID: <4203.1606095110@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/gU1C5_f-uvBdDZ-VDkfYbtFDQdU>
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 01:31:57 -0000
First, I am not certain what I, or the WG wants to do with this document. I feel I'm getting feedback as if it was a WG document, suggesting consensus words. If the WG wants to adopt this, and find a few co-authors... or maybe even take it over, that would be good. Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote: ce> Section 1.2, "IETF 108 would be best described as a sprint." ce> I would classify IETF 108, and IETF 109, more like a typical IETF ce> meeting attended remotely, which is not a sprint in my mind. You ce> needed to pace yourself for the week, so more like a 10K :) I guess that I feel it was more sprint-like, because there was no time for lunch, side meetings, etc. The day was shorter and was much faster paced. What word would you like to use here? ce> Section 2.1, "Heavily conflicted (physical) meeting schedules have been a growing issue ..." ce> This depends on the type of attendee as well. If focused on a few WGs ce> only, a more comressed agenda is better. For people who like to dive ce> into everything, as is thankfully common with many long time IETFs, ce> the packed agenda results in conflicts and difficulty checking out ce> new things. This wording, "people who like to dive into everything", feels rather flippant to me. You write it as if it's a personal choice. A whim. I wonder if the ADs feel this way too. The IESG likes to make lots of little WGs, which are highly focused. That means that to do certain things, one has to go to many more WGs than might previously have been the case. The charters say that we are supposed to coordinate with other WGs. ce> Section 2.2.2, "This document suggests that the IETF virtual meeting week be focused on: ce> I would add the hackathon and put it somewhere in the middle. One ce> concern is that if many WGs are not meeting, fewer people will want ce> to attend the in-person meeting and others will have a harder time to ce> justify it. This would also hurt the Hackathon as the Hackathon alone ce> may not be enough to justify a trip. This confuses me rather a lot. Above, you suggest that many people are focused on a few WGs. I guess that means three or four maximum, right? How do these people justify the trip now? I am very happy to include significant text about how the Hackathon fits in. In many ways, I think that the (in-person) Hackathon activity are rather MORE important than the WG meetings. I think that Stephen Farrel has said something similiar. ce> Section 2.2.2, "Rather than attempt to compress the schedule ..." ce> For me, the agenda for IETF 106 worked very well. The side ce> meeting/free timeslot that was added plus breakfast, lunch, and ce> dinner/post dinner were great and sufficient for this, including side ce> meetings/BAR-BOFs, Hackdemo, etc. some of those evenings. Improved ce> stay-for-lunch options would save a great deal of time and help ce> facilitate as well. IETF106 was still too congested for me. I would also like to free up more in-person time for side meetings, BAR-BOFs, etc. -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- [Manycouches] IETF109 starts at noon (local time) Michael Richardson
- Re: [Manycouches] IETF109 starts at noon (local t… Carsten Bormann
- Re: [Manycouches] IETF109 starts at noon (local t… Michael Richardson
- Re: [Manycouches] IETF109 starts at noon (local t… Carsten Bormann
- Re: [Manycouches] IETF109 starts at noon (local t… Brian E Carpenter
- Re: [Manycouches] IETF109 starts at noon (local t… Alexandre Petrescu
- Re: [Manycouches] IETF109 starts at noon (local t… Tim Chown
- Re: [Manycouches] IETF109 starts at noon (local t… Robert Sparks
- Re: [Manycouches] IETF109 starts at noon (local t… Andrew G. Malis
- Re: [Manycouches] IETF109 starts at noon (local t… Cj Aronson
- Re: [Manycouches] IETF109 starts at noon (local t… Fred Baker
- [Manycouches] many-fine-dinners --- a view on how… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Charles Eckel (eckelcu)
- Re: [Manycouches] many-fine-dinners --- a view on… Martin Duke
- Re: [Manycouches] many-fine-dinners --- a view on… Jay Daley
- Re: [Manycouches] many-fine-dinners --- a view on… Salz, Rich
- Re: [Manycouches] many-fine-dinners --- a view on… Martin Duke
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Salz, Rich
- Re: [Manycouches] many-fine-dinners --- a view on… Martin Duke
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Vittorio Bertola
- Re: [Manycouches] many-fine-dinners --- a view on… Stephen Farrell
- Re: [Manycouches] many-fine-dinners --- a view on… Charles Eckel (eckelcu)
- Re: [Manycouches] many-fine-dinners --- a view on… Alexandre Petrescu
- Re: [Manycouches] many-fine-dinners --- a view on… Behcet Sarikaya
- Re: [Manycouches] many-fine-dinners --- a view on… Alexandre Petrescu
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Stephen Farrell
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson
- Re: [Manycouches] many-fine-dinners --- a view on… Michael Richardson