[Manycouches] DOGFOOD Virtual BoF

Ted Lemon <mellon@fugue.com> Wed, 10 April 2019 12:38 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 25A621202E4 for <manycouches@ietfa.amsl.com>; Wed, 10 Apr 2019 05:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 QTNLcTPB_jZ7 for <manycouches@ietfa.amsl.com>; Wed, 10 Apr 2019 05:38:53 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 8EE3A120072 for <manycouches@ietf.org>; Wed, 10 Apr 2019 05:38:53 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id c189so1072179qke.6 for <manycouches@ietf.org>; Wed, 10 Apr 2019 05:38:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:date:subject:message-id:to; bh=Z0VMeyp9ZPOhXQjmsUgwEsSokRjyayovYMHjxUlZQMY=; b=Kn+Qww9t881AGyO5WMZmoaDS2Ta7vLc1rg6l1inAFITCFHaorvyB5Eti6bnV0QlKdV ofW5axpOpWklqhhcDsf/gm06qG3zYISmKViLJs0d1R9P1KLgkMLfZvj7vYvTvJf2fLZW d4+qCHRHWuj8UfzHXCwtwndrQe7HRRHfVSDq5ZFHyhBp19MwPbJJtGrrN/QwYVbRTAHd G6At/n+GcTjVSI1FjVUdHE3sS/5qsS3/LV01h3hIDyf+cPKrcc+JdoBlP8PcPcYzIA87 wSIXBFcFJTud8vKx3KcuZi+7XnBKDLFVjZhtijBk4TS+vaDr/IT6D0YOnsSSdxRQ231W EMIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:subject:message-id:to; bh=Z0VMeyp9ZPOhXQjmsUgwEsSokRjyayovYMHjxUlZQMY=; b=VP249oBeu+adEQ9uLFWYziKpjeM+N8AhwPJtrCdilLrq5QvtHXgQUq/YsT6ZmXv6Fz TraHL1qTwHIdOLifHTQnvO0SgEezRdr8MGeljF3pD7qtg943eisF+LPREp7QBcfiUiP9 qQ96c7B6jFWpYWgvBbpiGEAx6vLYUGUSLy9efyIteBsuKEO/9/DrzjdiEn+xqJC6f0Zk +EZrH9NG4goVsFbthzVNh7rGA7NcFN07EsHd1f85ErbE2qr9VZo6ZyOw53TMZ9B3O4EN HyZPd9LQaEgbhqx/jmWjNXfDlBOasNfSOlbxGyD4OVdZnqB37fs1i1nfS8I+G9XT+Z8J YItg==
X-Gm-Message-State: APjAAAUeI27KXEKZYiFQ1nJmt+WjCCxb3pL4eormuCPtUsw6173Mnsu9 iPRHGJtZSqd5GjyCUfpvcHoOQE4x1wqE5A==
X-Google-Smtp-Source: APXvYqwmi5zmG9ZkUTf6NkVIviR7POMQ4/cMeyv5+JEeGTw07YVdlZP8TWTeVdcFdYyMK9sK5hmHzQ==
X-Received: by 2002:a37:27d4:: with SMTP id n203mr32670486qkn.105.1554899932236; Wed, 10 Apr 2019 05:38:52 -0700 (PDT)
Received: from [10.0.100.12] (c-73-186-137-119.hsd1.nh.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id s50sm24471264qts.39.2019.04.10.05.38.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Apr 2019 05:38:51 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0985C6BB-9FD7-49D0-8F1A-03D0326EB667"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Date: Wed, 10 Apr 2019 08:38:49 -0400
Message-Id: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com>
To: manycouches@ietf.org
X-Mailer: Apple Mail (2.3445.104.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/maq37eMOcjouwQuyY1dHZ40xx34>
Subject: [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: Wed, 10 Apr 2019 12:38:56 -0000

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.

Thanks!