Re: [Manycouches] DOGFOOD Virtual BoF

Nick Doty <npdoty@ischool.berkeley.edu> Tue, 11 February 2020 23:44 UTC

Return-Path: <npdoty@berkeley.edu>
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 BBDBA12083D for <manycouches@ietfa.amsl.com>; Tue, 11 Feb 2020 15:44:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=ischool-berkeley-edu.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 BIsKi6Ce9lxM for <manycouches@ietfa.amsl.com>; Tue, 11 Feb 2020 15:44:25 -0800 (PST)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 EF0F1120839 for <manycouches@ietf.org>; Tue, 11 Feb 2020 15:44:24 -0800 (PST)
Received: by mail-yb1-xb29.google.com with SMTP id k69so32121ybk.4 for <manycouches@ietf.org>; Tue, 11 Feb 2020 15:44:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ischool-berkeley-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=O5ZsXBhA5hC1Ltes/fa2l/N7axWNK4IDz3NlyXT90WM=; b=eMtMrmpSKS6IxKuQZHt/rsTmObHZcUYq78S9M8XG/WA5xLIH6jtxCYcVmjsA9bnRCe Pa9E0xKREt/tPPDydAhwbI4zlM3xMSzquP1Mo7zEVBKMJ3EaL/SJpOcZY8UgkDg5BP9Z MSiaXCrOc/tcnMV9KI1+ZCGet85pkJFeBIum5esfBOZ+4XOJvu8alIMLYpCvzAMpB2G3 UeAOX9+ACf+QIwwqhf/xzEElkjU2Jfyw+6LnOKL8SY2I+QV8THKXXEUrb1rtmfskH8Nw U6ulqd9ES7BJMCyZuLsK0ouVjeWgjf48j9jpxcbKZWYODSXdBhs5k6cHmFXpNuXkK7MK aQtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=O5ZsXBhA5hC1Ltes/fa2l/N7axWNK4IDz3NlyXT90WM=; b=n/xKDSgRlcmZdgIRak5P9tX2l0AlfGhtn1P9M9Q7j8NSsw5zZ3JQUN6yLeLSjTml8Z hGQitSQhTZwHBCT7lb+BGiL5jghuPNI8TndM3I6fzUWjzOevknVwCZ1uQge0nz06+an/ kG+VmvROlSbzXiQaY2k1rc6RTrcUkXnVzuN31a1bWw/lVZ3IsvZt5vmuR824Va2KIwZt aW0WMAMbEEzB8+YuXEdnETWyvjh6ah+xFAy7nugJW5UU6Xe6jy5Ozbn0HtitMA4Fb9M5 BiNGtUFchJZ3O8nieZ+1ygiajYHkBYgsjjfHJS9V2bNcl+DON3YkCQvKMWBmx3DoCg5i foTw==
X-Gm-Message-State: APjAAAW/lTv9RnEmj/l9Pgcr93k0+NVifKyy4hNgFfpZ9cg4H04Xzggj 53qAxEuNVGQnXhcU8vmLNdXCrwAPcDA=
X-Google-Smtp-Source: APXvYqwghvVdgQb9lnjDShzEFXs+6nnbr7KtrU5Nbq1qcAQbwtOKyDzRMMB7mmGWhzzANyAgmrFibg==
X-Received: by 2002:a25:7707:: with SMTP id s7mr7967600ybc.278.1581464664000; Tue, 11 Feb 2020 15:44:24 -0800 (PST)
Received: from olgas-phone.localdomain (cpe-24-163-91-0.nc.res.rr.com. [24.163.91.0]) by smtp.gmail.com with ESMTPSA id o189sm2602468ywe.15.2020.02.11.15.44.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Feb 2020 15:44:23 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Nick Doty <npdoty@ischool.berkeley.edu>
In-Reply-To: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com>
Date: Tue, 11 Feb 2020 18:44:22 -0500
Cc: manycouches@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <540374B8-FB46-4F35-851A-ED6CEE586EA1@ischool.berkeley.edu>
References: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/fyvk7FLk7Olc7F_4riaDvN1yL1M>
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:44:27 -0000

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