Re: document writing/editing tools used by IETF

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 26 February 2021 01:43 UTC

Return-Path: <jmh@joelhalpern.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 781C93A1492 for <ietf@ietfa.amsl.com>; Thu, 25 Feb 2021 17:43:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, 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 (1024-bit key) header.d=joelhalpern.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 ldDc4JHKA05z for <ietf@ietfa.amsl.com>; Thu, 25 Feb 2021 17:43:00 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D85B3A1490 for <ietf@ietf.org>; Thu, 25 Feb 2021 17:43:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4DmsqS1ZFHz1nyF4; Thu, 25 Feb 2021 17:43:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1614303780; bh=Y4rH2pMjFTUBtTSGW4UOL+9WASFilHnbwDYBgYBJH1s=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=QsQIbjed/7qOM9d8lrKRvnHcQn+2Fbsgt5mY04YQVH6bmg2+KEGjqLWG3lAY7c1pv /h6v5bCEoYdypM5HDx9qZt8URsgct+cmk2hy/gsYdTlHHnvAfKa4OPKtyxsBp4sgC+ 6/SN+068VjvY0+VRCp0+opH0q+sasH5e+B7tDaOY=
X-Quarantine-ID: <sUOQnnavJjjS>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4DmsqR2wW7z1nyBf; Thu, 25 Feb 2021 17:42:59 -0800 (PST)
Subject: Re: document writing/editing tools used by IETF
To: Carsten Bormann <cabo@tzi.org>
Cc: ietf@ietf.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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <7d07396d-7677-9889-0a4e-7a5c0eb27846@joelhalpern.com>
Date: Thu, 25 Feb 2021 20:42:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <37142313-C251-40DC-9336-D3A2F0FB69AD@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U2IqKTEpwd5MWLoxYXR4LFgUqUE>
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 01:43:02 -0000

I think there are actually two issues related to authoring approaches 
that we do not currently handle very well.

First is probably not our problem as an organization.  That is the one 
you allude to below.  If there are multiple authors, they need a tooling 
approach that the authors collectivly can work with.  Whether that is 
github, passing source around, having a single pen-holder, ... is up to 
the author team.

There is however a second problem.  Namely the ability for the WG to 
take charge of the document when the author either can't or doesn't.  I 
still remember how much work the new author had to do with the ForCES 
protocol spec to convert the document from a very messy (and error 
prone) word format to the XML that we could edit in tools that would 
work for us. (The previous author / editor had left her company and 
therefore was no longer supported to do the work.)

Yours,
Joel

On 2/25/2021 8:19 PM, Carsten Bormann wrote:
> On 25. Feb 2021, at 21:27, Keith Moore <moore@network-heretics.com> wrote:
>>
>> I would like to make it be the case that anyone could submit a document written with their favorite word processor, and for that document to be converted to whatever format we want to use.   I actually think this is feasible for document submission.
> 
> This works if the draft is written by a single person.
> This approach does not lend itself to cooperative editing, for many reasons.
> 
> Grüße, Carsten
>