Re: [Manycouches] DOGFOOD Virtual BoF

"Mukom Akong T." <mukom.tamon@gmail.com> Wed, 17 April 2019 15:12 UTC

Return-Path: <mukom.tamon@gmail.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 67E01120369 for <manycouches@ietfa.amsl.com>; Wed, 17 Apr 2019 08:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 hUtBJ8ykQcUY for <manycouches@ietfa.amsl.com>; Wed, 17 Apr 2019 08:12:05 -0700 (PDT)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (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 57C63120465 for <manycouches@ietf.org>; Wed, 17 Apr 2019 08:12:05 -0700 (PDT)
Received: by mail-oi1-x236.google.com with SMTP id e5so20332829oii.0 for <manycouches@ietf.org>; Wed, 17 Apr 2019 08:12:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AzE1X/J62zqNpgFzPzMcmPZ+Oktte1qiH4NF9HOsLCA=; b=MiYzOWhWctyNdjDYrE7EyqMJpOUYe94tHnQ25n5NZnfd7Uw3hYM4Un15SXVZdMXLH5 1W1DWSkeIktslHF4P8b4QY+OZec/W2dwaAvsgDxgift5fuDFCQRFLED4Nd2ofMeRMjDA k6XBzaHRqnTvkmko/xnNymt00eEDH1zMPPoeHsW8vDqqbWrFue0iLuT20dxK5eao6v6x 04cQXtW/A3ZiQq7efZtiLeMA9UklF9SbJH6RUmpU6UwPTzKrJ+roTOMOHE5PE6hfhyvS fqGZ6p/OlNHNMLGefKlfpcopLfVn36rp53aT6BaKhi6rHtk/6kqSP8EVXK65Zvm2qmWJ cflg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AzE1X/J62zqNpgFzPzMcmPZ+Oktte1qiH4NF9HOsLCA=; b=PtzhcEn6YETsuREwn8eMnOs2XFVFOcEc5miiXxveCskEdFPw4w6OiquY/D0+sQcHLK F5LlkQi+YhPpjyONbJxP/yVwtdB64HnEzV/+eGiPVuE5iq3tu44XOaxWDOpw8NmY/9Cm afIno92OmT1SZ6OQ/pcr6faeOOEVfyPPgL3YjagH52GBy5MXx9fsCZ7wQAqlpoQsB4o0 SJGg4AbmBrertHc5QecZJForbxiphCbd77YCOWPkPkPv+6RKsQBkENp4cJ/A0fFi29PR tmCvp0ZfEJwp2gvRFte/w+Kd98giiV/x9s0KhF1JLiHCBJXsa9txKM95fCjaJVppo/UW PR0w==
X-Gm-Message-State: APjAAAVT5m3qUKI6uREtKW9UVJDvPBCcIrQm986sOI5iFvoqvc7sHQ6j ZU2WN05dkPGYm/FaE/MZKyyfItQ68PfFxXneaXuLuZd+Wbw=
X-Google-Smtp-Source: APXvYqyliGanT/4jZnRljRG2mE/vb1uOt93NkpobBbvTw3L2nY0Eblht6Q/loAb1dy+fKIT0OWW5gvnZKNJ1KE+emeA=
X-Received: by 2002:aca:4a0a:: with SMTP id x10mr26121959oia.82.1555513924185; Wed, 17 Apr 2019 08:12:04 -0700 (PDT)
MIME-Version: 1.0
References: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com>
In-Reply-To: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com>
From: "Mukom Akong T." <mukom.tamon@gmail.com>
Date: Wed, 17 Apr 2019 19:11:32 +0400
Message-ID: <CAHDzDLCKgvdDuxznW7UAQsvKWK1jCgdsUyLJA7GYGdYwUq-XOQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: manycouches@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e4f9240586bb4e8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/EdCgWXrIaEmzToQ6A_M_6wfyVv0>
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: Wed, 17 Apr 2019 15:12:15 -0000

On Wed, 10 Apr 2019 at 16:39, Ted Lemon <mellon@fugue.com> wrote:

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


I think we ought to question even the tools and not assume that the current
tools as we have now are the best ones for the new approach we want to try.
If there's some more effective tool out there, let's find it and try it.
It's better to settle on current tools with the secure knowledge that we've
tried the alternatives.




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


Agree about moving into action. Could we start by having an online page
somewhere which states what we're trying to accomplish and gives context?
An email chain might not be the best way to do this. It could be

- wiki
- dropbox paper
- google doc
- etc etc

I'd suggest it be structured in the form of an experiment in a form like

Objective: Run a BoF completely with no travel
├ Key Result #1: 100% of BOF planning and execution done completely online
├ Key Result #2: 50% of those who sign up for the BoF stick through till
the end
├ Key Result #3: 75% of those who stick to the end agree to sign up for a
second BoF

The numbers we can play with.


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

I sure will


>
> 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!
>
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches
>


-- 

Mukom Akong T.

LinkedIn:Mukom <https://www.linkedin.com/in/mukom>  |  twitter:
@perfexcellent


------------------------------------------------------------------------------------------------------------------------------------------
“When you work, you are the FLUTE through whose lungs the whispering of the
hours turns to MUSIC" - Kahlil Gibran
-------------------------------------------------------------------------------------------------------------------------------------------