Re: [Manycouches] DOGFOOD Virtual BoF

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 17 April 2019 19:34 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 03A5F12046F for <manycouches@ietfa.amsl.com>; Wed, 17 Apr 2019 12:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VEjSoucpUSoY for <manycouches@ietfa.amsl.com>; Wed, 17 Apr 2019 12:34:40 -0700 (PDT)
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 5637C120463 for <manycouches@ietf.org>; Wed, 17 Apr 2019 12:34:39 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 115E63808A; Wed, 17 Apr 2019 15:34:29 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 1F6373A26; Wed, 17 Apr 2019 15:34:36 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1CF73DBF; Wed, 17 Apr 2019 15:34:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Keith Moore <moore@network-heretics.com>
cc: manycouches@ietf.org
In-Reply-To: <7b4e4551-3d10-0b6e-91c1-4bc51c8d0831@network-heretics.com>
References: <AB5A9A15-D7EC-421A-B139-19F42A71C747@fugue.com> <CAHDzDLCKgvdDuxznW7UAQsvKWK1jCgdsUyLJA7GYGdYwUq-XOQ@mail.gmail.com> <7b4e4551-3d10-0b6e-91c1-4bc51c8d0831@network-heretics.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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-sha256"; protocol="application/pgp-signature"
Date: Wed, 17 Apr 2019 15:34:36 -0400
Message-ID: <8873.1555529676@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/IHEHMWi8Fug3npURMPml1NorNkc>
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 19:34:43 -0000

Keith Moore <moore@network-heretics.com> wrote:
    > I think we have to start somewhere, so starting with some base case -
    > say just email - makes more sense than trying every tool right off the
    > bat.

    > Or _maybe_ email and some sort of shared editor that can keep track of what's
    > been concluded. but even then we need to have some discipline for what to put
    > where.   Also, if we use multiple tools without some kind of
    > integration

It sounds like we want a wiki technology that uses git as a backend.
The repo can be cloned, and the history can be a signed commit/tag giving a
clear statement as to what has been concluded.

There are quite few options, including what github offers via host jekyll:
  https://www.google.com/search?q=wiki+with+git+backend
  https://duckduckgo.com/?q=wiki+with+git+backend&t=h_&ia=web

    > I also am loathe to use third-party tools that track my activity, and would
    > not want to see IETF adopt such tools.  So, for instance, google anything is
    > (IMO) not appropriate.

I understand your view.
This view has become a barrier to entry for many.  I wish that weren't so.

    > We should decide what kind of tools we need rather than insisting on
    > shoehorning our activity into existing tools.   And I'm not aware of an
    > existing tool that would do the job well.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-