Re: document writing/editing tools used by IETF

Carsten Bormann <cabo@tzi.org> Fri, 26 February 2021 07:36 UTC

Return-Path: <cabo@tzi.org>
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 0E1223A08BE for <ietf@ietfa.amsl.com>; Thu, 25 Feb 2021 23:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 lUw_SKUEuacD for <ietf@ietfa.amsl.com>; Thu, 25 Feb 2021 23:36:04 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9649C3A08C5 for <ietf@ietf.org>; Thu, 25 Feb 2021 23:36:04 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Dn1fp5Lh5zyTv; Fri, 26 Feb 2021 08:36:02 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: document writing/editing tools used by IETF
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <001d01d70be3$ff0972d0$fd1c5870$@acm.org>
Date: Fri, 26 Feb 2021 08:36:02 +0100
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-Mao-Original-Outgoing-Id: 636017761.2290469-b95fbfea1fa8878d51d69c048796d6a8
Content-Transfer-Encoding: quoted-printable
Message-Id: <213FBF20-E8BB-40C3-ACAF-40A53731A23C@tzi.org>
References: <37eecb9b-f0eb-e21c-b162-b1f0339e4981@si6networks.com> <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com> <446A8D6B-E624-49E0-B67E-D1F8AFC794E2@lastpresslabel.com> <28ac1e86-f641-b9e8-0f61-6ff442feaa90@si6networks.com> <LO2P265MB057322BA95B1B44D4175356BC29E9@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM> <089096b1-10d2-3eac-d37c-f040a1930061@network-heretics.com> <37142313-C251-40DC-9336-D3A2F0FB69AD@tzi.org> <001d01d70be3$ff0972d0$fd1c5870$@acm.org>
To: Larry Masinter <LMM@acm.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rKXPjTCEuD8kOAMff32LX5pvnC4>
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: Fri, 26 Feb 2021 07:36:07 -0000

On 2021-02-26, at 03:06, Larry Masinter <LMM@acm.org> wrote:
> 
> For collaboration, there's a generation of collaborative tools from Google Docs to Dropbox and Microsoft tools that are a lot better than GitHub for collaboration.

I’m sorry, Larry, you’d have to have a very weird sense of “better” to believe that.

I have had extensive exposure to the MS-Word type of “collaboration” (I was the editor of RFC 3095 which was done in MS-Word, with 16 collaborators).  The English language does not have words to describe that experience.

For hacking out a quick draft, shared editors like Google Docs are fine (we mostly use hedgedoc née codimd née hackmd for that, and it sure is fun).  For structured, controlled collaboration in a large team, nothing beats VCS systems like git, and github has a lot of mindshare in the tools around that process (issue tracking etc.).  

It is simply hilarious to imagine the QUIC or HTTPBIS WGs typing away at a shared Google doc.  That’s not how it works.  Specs are code, and there is a good reason why creating good documents (like the core ones of the above WGs) benefits from experience in collaborating on code.

Grüße, Carsten