RE: adapting IETF in light of github and similar tools

Larry Masinter <> Tue, 20 April 2021 17:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E15D93A0D00 for <>; Tue, 20 Apr 2021 10:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1g6KRA8S-1iS for <>; Tue, 20 Apr 2021 10:32:32 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7564D3A0CFC for <>; Tue, 20 Apr 2021 10:32:32 -0700 (PDT)
Received: by with SMTP id d10so27106126pgf.12 for <>; Tue, 20 Apr 2021 10:32:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=sender:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=PFDFJ4AtM0Nw/hVJs68hCUWE7qcBoEmqvdtDHE0MzgE=; b=nifLwr9fdhAOPMr46qZEz+j4QN2f8Ne8b/UWlbSn6fMg5PPyxBal+1YiVyVhbcO8BY joSMdBTMIcb+K/6TYprS5HkcNtU2HnmZZMpSU6IzGEihCbIHP1iOdGmGQRQIEq8T3+yf K83rKniZjF2Khxie1KFAA4YdwWtkyuRcgMksZmm0V7y0DudE182Pv+Y2bD2h124wRPRU Jv7uxmqKRf/LwbxJaJYBu+7gRb5CYodTLzThGefj9LkME38GKRbxNmFiYTaHjhrMLlK5 VhRFjBvVBvZvBv1JqeYOy8cch2mozLYDhJdWUsVw0dkPJXEtpRGVnPAAgcV5xQSCXWKC 9j6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:sender:from:to:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=PFDFJ4AtM0Nw/hVJs68hCUWE7qcBoEmqvdtDHE0MzgE=; b=eC2jKv+Q+bZJrKWwMFubZp4mx0OpeQF+I6mmVU+OF5KHPowg/mAMyEWQ196U+znHPx 7XErOyu0+gXmxiU4q98mPtKy0nS4O89xnuCShJFLFvy1j95o08cZ5hsk6s530flZu1Ge t9xTGeEe7Xn55/965L2hxNMR+MmxEV6nFbNLS7T2Cb99C8AXtkLg4t1Z4gBiH1ka0a3G d3Z3osQTI42Oa7syaLAVuZCtUT1V0rzZcNfMzfAR80T4zI6Y9GkDaa0bR4mIabkxme24 /CURQwdiY58LoIv2QSMtxt1E79dxfWDY+fIXVRDf4sPhtT6Bq1tLzu3ZYyvav9f5xchP 65vQ==
X-Gm-Message-State: AOAM531UdibabWMr9RVrtoHvslMLULLWIyDByCCkzBYXL8MfousHK7Ww Rqztq16ZPvWJdbLxMYIe9Zb/dAxS3THvbA==
X-Google-Smtp-Source: ABdhPJyvP4kvN1ltTjpOug72fp68qH1CJRdB4toMNAqp7GhmH8nWZdBR84jceVacm6EvQfhp5yrsog==
X-Received: by 2002:a05:6a00:b41:b029:261:fc0f:15f7 with SMTP id p1-20020a056a000b41b0290261fc0f15f7mr7985702pfo.30.1618939950360; Tue, 20 Apr 2021 10:32:30 -0700 (PDT)
Received: from TVPC ( []) by with ESMTPSA id w10sm5395126pfq.184.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Apr 2021 10:32:29 -0700 (PDT)
Sender: Larry Masinter <>
From: Larry Masinter <>
X-Google-Original-From: "Larry Masinter" <>
To: "'Salz, Rich'" <>, "'Keith Moore'" <>, <>
References: <20210420160859.BF41573B7076@ary.qy> <> <> <>
In-Reply-To: <>
Subject: RE: adapting IETF in light of github and similar tools
Date: Tue, 20 Apr 2021 10:32:28 -0700
Message-ID: <001001d7360b$2384e0d0$6a8ea270$>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIpioWCvDqaNk5D8aAZ4YcV8LsnZgHsatyuAhbXlgQChoH8PanksPJQ
Content-Language: en-us
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Apr 2021 17:32:37 -0000

Git/github could use some adaption to make it work better for IETF.
I sent in some suggestions back in January. Does anyone think GitHub is
perfect for IETF use already?

-----Original Message-----
From: Larry Masinter <> On Behalf Of Larry Masinter
Sent: Wednesday, January 6, 2021 10:51 AM
Subject: RE: Old directions in social media.

I'd like to see the IETF LLC fund some development of enterprise to make it work better.
Just off the top ...
An enterprise license so it could be customized.
Fix the default GFM so it could easily be used to produce xml2rfcv3 With custom diff appropriate.
Default actions for building PDF, HTML, text views Tie in with DataTracker and appropriate authentication....
Integrate with email and wg "decisions"
Fix the bugs in GitHub "discussions" <-> Issues Integration with meeting tools (agendas, minutes) Default "Teams" & roles appropriate for WG work rather than software development Tutorials & written guides for using Git for IETF work  Regular summaries and insights appropriate for document production Some way to subscribe to summaries of actions and topics without watching every action on the repo (maybe a 'significant change' flag that the PR has and must be approved)