Re: [Manycouches] DOGFOOD Virtual BoF

Ted Lemon <mellon@fugue.com> Tue, 11 February 2020 23:52 UTC

Return-Path: <mellon@fugue.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 5989E12006D for <manycouches@ietfa.amsl.com>; Tue, 11 Feb 2020 15:52:21 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Xd1mx4ydOkiI for <manycouches@ietfa.amsl.com>; Tue, 11 Feb 2020 15:52:17 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A5E012004C for <manycouches@ietf.org>; Tue, 11 Feb 2020 15:52:17 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id dw13so44540pjb.4 for <manycouches@ietf.org>; Tue, 11 Feb 2020 15:52:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=wWTM1PSECk/RuUn/45Li5B0C9oie1KXdW28pNE2x07k=; b=aYsL4/0hN0m1iqjdePEDtcxr+Jq1DCfQX7dfRTqe6bohW/P7AdGaIK+bnU0jeNvZ3n arbN97Gz10gVgRvytOSw+l1NvCy51VGIp6cB/pHFZHsew5WulJpUR0SIdgwYzEXWV+th ePrQSNq/OiTASyhtagOvnu43U4oYIs15JW6PihDaTFC2ZcjzEcpJHS4uBrUN4KC9SbBy 0Cy91swG329pIgQeUZTcUBG/lNPA3EdkzN4zEZlDq5HTBQXJoMfb5ssOc7e94YT21p6L ApUuifXeiKjXjfxmQErPFa7GaCdO47fNHWNrwrE60I91xgv5/RbgzyuBgobK29OTt0pe Wp1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=wWTM1PSECk/RuUn/45Li5B0C9oie1KXdW28pNE2x07k=; b=VVG3ygHE96/EXmwnGDgQELmcxC48HLvUYTfVIQ17LAWcheOix6p4dS5dGa69WbvLzY FPMgXAiJCzhnrEASJSLj6+9Xw2+D2NbmvPaO/FxQV11h18Z+Db1yn+PsLve0Wvylz/a+ IYPHRuxbUNecL3RCHZxhJA8eYK/d7/TgL0RMmKAawX7EQFR4G/Rk9w0C5hXEmhQ5VRjG yVdlsOAeB4QJ3VcejBOjqHWmV06MO+d+dg3RvsSYxl0VW5GeNMcRc0S1yHbQBhRKB2Ah WLklbDqIWLpbe3yTi1Y5Qq+SVZNS2ErH3LuQ58fZZhlaTlLDzdm67fzCeWQGVrxhzJp6 pVBA==
X-Gm-Message-State: APjAAAWm+lTWHZ4qJofmXjJ5N9kJJHwK2OzL4w9yNtU9JWkAt+9iUAH4 dtXlnqna7oQk3KGKV/byG4iHNc3Rjrk=
X-Google-Smtp-Source: APXvYqxxB5GJ7+VEWUbKCsiLzGmPLoyrJ5Yl+tSF0CvzZHY91HeaQEetmzkPeEpf/bGm90ShZvhmMw==
X-Received: by 2002:a17:902:740c:: with SMTP id g12mr21395154pll.166.1581465136828; Tue, 11 Feb 2020 15:52:16 -0800 (PST)
Received: from [172.16.140.189] ([144.178.28.13]) by smtp.gmail.com with ESMTPSA id b3sm5502347pft.73.2020.02.11.15.52.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Feb 2020 15:52:16 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <A980371A-949A-49E6-99B7-DB0449476275@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F6CC2BA2-3930-4BB8-9225-EFF45D5B1A31"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Tue, 11 Feb 2020 15:52:14 -0800
In-Reply-To: <540374B8-FB46-4F35-851A-ED6CEE586EA1@ischool.berkeley.edu>
Cc: manycouches@ietf.org
To: Nick Doty <npdoty@ischool.berkeley.edu>
References: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com> <540374B8-FB46-4F35-851A-ED6CEE586EA1@ischool.berkeley.edu>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/2uGBuAFgswURBaWEChwg0-aTA6I>
Subject: Re: [Manycouches] DOGFOOD Virtual BoF
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: Tue, 11 Feb 2020 23:52:21 -0000

I ran out of bandwidth and dropped it on the floor.  Yes, there was a lot of support, and some good discussion.   If you want to pick it up, that would be cool.   One thing to think about is, is the right way to do this to try to talk IETF leadership into doing it, or would it work better to just start getting working groups to do their work online and not in person, and just not meet at IETF in-person meetings, or only at one designated meeting per year.

The problem is that the IETF leadership may not be able to see the problem clearly because it’s so far outside of the scope of standard operating procedure, and convincing them to take the lead on this probably won’t work—it hasn’t in the past.   So can we instead lead by simply being smart about our own behavior as IETF participants?

> On Feb 11, 2020, at 3:44 PM, Nick Doty <npdoty@ischool.berkeley.edu> wrote:
> 
> Apologies that I’m coming to this conversation belatedly.
> 
>> On Apr 10, 2019, at 8:38 AM, Ted Lemon <mellon@fugue.com> wrote:
>> 
>> At IETF we had a bar BoF which hopefully quite a few people on this mailing list attended.   At the BoF we had a round table discussion about what peoples ideas were for getting the IETF into a new mode of operation that makes better use of the technology we’ve developed, rather than requiring in-person meetings as a driver for getting work done.
>> 
>> At the BoF we agreed to have a virtual BoF online in about a month.   It’s about two weeks before the deadline for that, so I wanted to have a quick discussion about what to do at this BoF before announcing it.  Because this is not an IETF working group, the usual notification requirements don’t technically apply, but on a practical level I think two weeks notice is just as necessary for a virtual BoF as for a virtual interim, so I’m going to ask the secretariat to announce it the same way.
>> 
>> I would like to try out some of the stuff that Wes talked about in his presentation at HotRFC: rather than just doing a normal BoF, I’d like to see if we can use existing tools to achieve some of what Wes described.   We will still want to do some online video discussion, but I’d also like to try using a Wiki and an interim-only mailing list as the primary communication method, and do the BoF over two days to give us time to participate in the way Wes described.   This may fail miserably or may go well—we can only find out by trying.
>> 
>> If we go ahead with this, one of the things I will ask is that you add to the Wiki your recollection of what you said in the bar BoF.   I at least didn’t take notes, and I don’t think Wes did either, but I think there was a lot of useful stuff exchanged there.
>> 
>> Does anybody object to this approach?   If I don’t hear loud objections, I’ll set up a wiki and ask people to work on it; I’d like it if we could do that work before the interim so that at the interim we can talk about it and form some ideas for experimentation.
> 
> Catching up on the thread it looks like there was a lot of support for this idea. Was there a wiki set up and the tools/ideas tracked somewhere?
> 
> I think part of responding to the climate crisis — and being prepared for the impacts of the climate crisis and responses that others will take to encourage mitigation of the climate crisis — is practicing conducting useful meetings without all having to be physically co-located. One idea I’ve heard proposed is regional satellite meetings. I’d be happy to hop on a train to join a US/East satellite meeting that could have a few conference rooms and some nice videoconference software to the other regional ietf1XX satellites, rather than flying to a different continent on a regular basis. That it would be much cheaper financially would also make such meetings more accessible to recovering academics like myself, and could serve our goals of encouraging more new participation and participation from outside well-resourced companies.
> 
> Looking forward to learning more from you all.
> Cheers,
> Nick