Re: adapting IETF in light of github and similar tools

Keith Moore <moore@network-heretics.com> Tue, 20 April 2021 16:54 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 302FB3A08DE for <ietf@ietfa.amsl.com>; Tue, 20 Apr 2021 09:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=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=messagingengine.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 rSV53UTByDhM for <ietf@ietfa.amsl.com>; Tue, 20 Apr 2021 09:54:51 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85F8E3A08DA for <ietf@ietf.org>; Tue, 20 Apr 2021 09:54:51 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 01F873E77 for <ietf@ietf.org>; Tue, 20 Apr 2021 12:54:47 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 20 Apr 2021 12:54:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=u1xzH0v7/NsUt6FO+fEvzPFGtV7C/RBBjyMO7vbfZ w0=; b=KRRAQIFprt/7tAlNIzrJE5KeLq8k21wj1DkXaMlgpocrmny6YmJRHushk CK9xAZQKkzJLWnuv0MAGPojvZ8trLPxzURcFiOY3HyfshYnklrwtQVo9xfaDtfN/ Ivreafae70ielUb31To2h44QDVgRsYqzdPcxmV4HfX1ZTgFWbmvK8It7J3RlVAlo 8S6EWlf8frHCIsYH/LrvWa1+D1ALTFigfEHkKp/FfxeneE5QrLzXJBa/6QxeC6LL XMgc/mMUUimOXPT747q+wWkmySxg2DASW0Uci7r0cH21T8bUp4QeMBPkPT3Nr5p8 QPVB3t39y/D2jX1WZnp2vbg0PxudQ==
X-ME-Sender: <xms:Vgd_YEqGzvvc0oWDBkXE39ycV9YgeKGlCR7n4IVCYrFXqvs_tdtGNw> <xme:Vgd_YKrFwwPTK_5BTQohsx5K6fGkF0PKucZp0ItxhcnMIWK7nyDPfxUJ9vQ3uaZxJ uaMkkS_WKA_fg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddtiedguddtlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ejredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepkedvgefgle euleekuefhffehgefhhfekuedvudduiefhhedufefftdfgtdekfffgnecukfhppedvfedr uddvgedruddtrddujedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:Vgd_YJM9ChoOeROinxE8R_YxTfyo3afGVGzucRxp1RjB-72cqsgwwg> <xmx:Vgd_YL61FcwVzyHTZMOW4IdgGHQoRkNmcyLHUEWvNNDberHWIPzTTg> <xmx:Vgd_YD7a8vHPnXvlzmRumH-h_yjf3DU1Dsj8C0FV8n_hm73e1Q8keQ> <xmx:Vwd_YGI-tzUxxs-Yth8EDUEm9Ude7RujJh2FiQXC2clYIwBBJyqADg>
Received: from [192.168.1.121] (23-124-10-170.lightspeed.knvltn.sbcglobal.net [23.124.10.170]) by mail.messagingengine.com (Postfix) with ESMTPA id C2A4A1080068 for <ietf@ietf.org>; Tue, 20 Apr 2021 12:54:46 -0400 (EDT)
Subject: Re: adapting IETF in light of github and similar tools
To: ietf@ietf.org
References: <20210420160859.BF41573B7076@ary.qy> <9678ca2c-207d-51ef-1979-c982253d7ecf@foobar.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <b9cacfa5-5085-6a87-add9-c77c6f8bed7b@network-heretics.com>
Date: Tue, 20 Apr 2021 12:54:45 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <9678ca2c-207d-51ef-1979-c982253d7ecf@foobar.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H7_0KFXPk-QymxaoJSAAvVG4WXc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2021 16:54:56 -0000

On 4/20/21 12:38 PM, Nick Hilliard wrote:

> in addition to which, any claim of GH capture risk can be averted with 
> a surprisingly low overhead "git clone" operation. 

The overhead isn't in the "git clone", it's in retraining everyone to 
use a different site with different enhancements to vanilla git.

Keith