Re: [Ietf-and-github] document editing and protocol implementation absent from draft-ietf-git-using-github-05

Martin Thomson <mt@lowentropy.net> Tue, 10 March 2020 12:06 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BFE23A11A6 for <ietf-and-github@ietfa.amsl.com>; Tue, 10 Mar 2020 05:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=lowentropy.net header.b=m6bQ4uqy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=r+mvd9ni
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 ctfKLs6xoysX for <ietf-and-github@ietfa.amsl.com>; Tue, 10 Mar 2020 05:06:48 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AB6C3A11A4 for <ietf-and-github@ietf.org>; Tue, 10 Mar 2020 05:06:47 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id B61FA21C4D; Tue, 10 Mar 2020 08:06:46 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Tue, 10 Mar 2020 08:06:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm1; bh=hc 4GCDX1s6+q7YwXTCC47ggoByABFyM2a4BvQil/rRY=; b=m6bQ4uqy2t3Di+h6wC mEe8J2wB/+kgujeQBcEEq+NCTJ/anBAA1DtqFpvBJy3lxYzJ+5NXyOM0gfM+ASxG K7gERQdstlxP2gS4P6Qw5/JfrV7IGjwf3yPYbPj8oj0mpPL5Kh3NN46MCoIqX4bP GChs9AgVUYMkDC74QDUy5wqk+tMzn0rhkQrqCnNbqjoeaXSfQSWfMEfdiQ2UoXu4 u1Z57psozo81FoWV1dPfIMesogQOHf7rwt1iUdN4oZD0GtEDLudWQgn0VN9N5FJT V7OzVRgHnswfO8q6yPteQc2wdA/M0IzapXdxLlPUKRXKANrRaMg9RJtIeOJeX3Xx HSng==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=hc4GCDX1s6+q7YwXTCC47ggoByABFyM2a4BvQil/r RY=; b=r+mvd9nipE2B+ABiRPZfoC/SowXGwg9kYIuoC+1Qmgx3Ouqu1iE2FgMAT EtnXCVfzQ+Y520N+CLP8etPkfeCdOqAYuOYhD1qdGZu9L2Xr9E1ABYApDMZPnlbV 6CA/LMmIAV2nkXx+egSAO9fqjvvjTPZ8eEY2lvQY2KBcpJf+a+9LZ+oA1gjNEzET LPGLLftboo/eEy9M1o1h3l1F0HJK4XZGnjxTzJliCgq+cUeR9AmX++QuF5jpbMr2 nEyeA+QpJdfhb0PF7u7BU1kBzdT7dV48+6mYdHHjj08FdkAPzCnsD3uJH9FVkQ91 26LhgG9aJ09u9CQFLmYzRKGCpAUfQ==
X-ME-Sender: <xms:1oJnXopCnwvkzbJby4qAe3RJv-L0pD4Ex0O4v1pCQzBlRlB24rWR3w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvtddgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfofgr rhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenuc ffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:1oJnXpFeaNVu0QwY_HYFBZFPq67Sqg1aNx6n8jPxzKlamb_J5PT1gw> <xmx:1oJnXksIfeAvX4KB1UhCdwluf_7Y7ivba71SCqnWG6BSlaRECEPb8Q> <xmx:1oJnXnYLxBasZmhjM_hrQZDkASv2thk2xrtRQPe4MPJnwoBDSjyXFA> <xmx:1oJnXgEu7CVOHWgYQ-7u3tfrOu1x2mRNHUjEmqxIm5ei-VQJzc7pgg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 705FBE00AC; Tue, 10 Mar 2020 08:06:46 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-991-g5a577d3-fmstable-20200305v3
Mime-Version: 1.0
Message-Id: <1e6d4ab9-e647-48a6-8b25-3a904d96df47@www.fastmail.com>
In-Reply-To: <CADyWQ+GLjXfhv3G5rAY88qDa9fjzsj6KbwxyYJw+-ng86f8hRQ@mail.gmail.com>
References: <158250611906.1067.14505081937854561120@ietfa.amsl.com> <3450f158-be66-71d3-b29a-6751650d64af@gmail.com> <f1c29108-1710-425e-a6f9-394ab247896e@www.fastmail.com> <26084a2d-a6f7-955c-7994-3dc48f58f145@gmail.com> <05fd402e-5ee3-4996-8394-8835a8f3f0c7@www.fastmail.com> <53307b7c-8575-9d7d-5504-d9dd7f7d5097@gmail.com> <CADyWQ+GLjXfhv3G5rAY88qDa9fjzsj6KbwxyYJw+-ng86f8hRQ@mail.gmail.com>
Date: Tue, 10 Mar 2020 23:06:25 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Tim Wicinski" <tjw.ietf@gmail.com>, "Alexandre Petrescu" <alexandre.petrescu@gmail.com>
Cc: ietf-and-github@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/ua2j_gDLA0i2K58Ix_qQ9ajPULE>
Subject: Re: [Ietf-and-github] =?utf-8?q?document_editing_and_protocol_implem?= =?utf-8?q?entation_absent_from_draft-ietf-git-using-github-05?=
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2020 12:06:50 -0000

Thanks Tim, I agree.

The document concentrates on document production.  Though GitHub is probably even better suited to software development, that's not an activity that the IETF needs to have such a strong hand in.  If a working group wanted to develop a reference implementation or a test suite or other code product, then I would definitely recommend GitHub.  But that is rare enough to treat on an ad hoc basis. Many people will use the tool for that purpose and more power to them for doing so, but we don't need supporting documents for that.


On Tue, Mar 10, 2020, at 22:54, Tim Wicinski wrote:
> 
> This document very much stays away from suggesting using github to 
> write software for protocol development.
> I would argue that the decision on which tools to use in a WG project 
> should be decided by the WG based on 
> needs, etc. 
> 
> tim
> 
> 
> On Tue, Mar 10, 2020 at 7:39 AM Alexandre Petrescu 
> <alexandre.petrescu@gmail.com> wrote:
> > 
> > 
> >  Le 10/03/2020 à 06:50, Martin Thomson a écrit :
> >  [...]
> >  >>> 3.1. What to Use GitHub For
> >  >> 
> >  >> This section 3.1 is good in general, but does not seem to me to say
> >  >> What to Use GitHub For. This is what it should be used for: share
> >  >> Internet Drafts and share code implementing protocols.
> >  > 
> >  > That is in the Introduction and Document Goals sections[...]
> > 
> >  I think that is not the case.
> > 
> >  It does say in Introduction and Document Goals that one goal is document 
> >  editing.
> > 
> >  It does not say in either section that a goal of using github is to 
> >  write software for protocol developped by that WG.
> > 
> >  Were it to say so, I would discuss it further. In one WG I am active I 
> >  hesitate between recommending github for software writing, or another one.
> > 
> >  Alex
> > 
> >  _______________________________________________
> >  Ietf-and-github mailing list
> > Ietf-and-github@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-and-github