Re: document writing/editing tools used by IETF

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 26 February 2021 15:48 UTC

Return-Path: <sarikaya2012@gmail.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 26E8B3A0CEE for <ietf@ietfa.amsl.com>; Fri, 26 Feb 2021 07:48:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=gmail.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 f65K74tK8mLF for <ietf@ietfa.amsl.com>; Fri, 26 Feb 2021 07:48:20 -0800 (PST)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89EA63A0CED for <ietf@ietf.org>; Fri, 26 Feb 2021 07:48:20 -0800 (PST)
Received: by mail-yb1-xb32.google.com with SMTP id n195so9301994ybg.9 for <ietf@ietf.org>; Fri, 26 Feb 2021 07:48:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=GimXI6IfT+93CK4/91JaLVKNexf8iDVXzoQthq+fyMY=; b=snr6Y+rQJ9PvSRxqtLdHCgUQ5yQwgCij2iVxNwMY3MMPLs/DQl0KcpbZiMSw+Y7yYl aNawHmMTqpxs9qQTion9onHXP1XSsorsADJzS1g9A+FtflBg1sqHrtHjNw3PI2TgmyBk u53avIhKeI+2EAMcPFVtTdmAKbKw6E3XexffQ/8C4y1IN7pqvMfRBdxeeGjmmRlz3vcr Gd0VuF3fwsRhX4pHXi5R+2leV+U1KgneIpcF8Plm4/FI0nLJhbibQf2nKvG69tqgKkxy qX5PbyPLRDORZRdoecQLnxr38vQvR9/auEwhEPnFwR1DAjk6oOApTqXKgYhxaNH0w5Wz ZAJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=GimXI6IfT+93CK4/91JaLVKNexf8iDVXzoQthq+fyMY=; b=HEnSYTzIC6qykxKkw8aYKWZTLlDyJhGzPDhpnZkPze2oVoiKyy7+atPWkb/LCVv2Up IyATqUp+0auSNuLiUbcZ5aFU/dguPCGbT9OJnGqYanAFZdTs/gVTanupwjEnUNSZDJFv OVCTZm+HPicArWYaPd3K+J2uZF6EMeC/KTdy/fJjUM2sugD9xtqe8+an+2BPeI157mpD QKOkKNM1oVUSJemF9yEAlz5BQkBLxBF2Hb4FYmdqFYD0jZuOmAQ/AcYNTwea5SwzKc23 c/eapYPrhQfJOAOXa8LVg2GbTDqPs/Sh5N6eYDGW1ucl+lnJaVPggGHVnfICUqrFuKDM mRtw==
X-Gm-Message-State: AOAM531XKG/Bvnhv8fT7uXJI/lcDi4jM3/sxGP/PYky4jmKPC5lAUJu1 EA7bw4ofyXI39mNfO+zi/RAVPV8sYuXf2ERciiw=
X-Google-Smtp-Source: ABdhPJzN73ZvQSgztqjdS+yI3lcp+olBXlMqPOpSyL3MIfowDutO9Fro1QOov16GJFQwQHT4rbSxAtPrPCrS06hZxko=
X-Received: by 2002:a25:ea06:: with SMTP id p6mr5528660ybd.243.1614354499679; Fri, 26 Feb 2021 07:48:19 -0800 (PST)
MIME-Version: 1.0
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> <213FBF20-E8BB-40C3-ACAF-40A53731A23C@tzi.org> <c14f77c6-adc0-0d0b-5c17-c25c19e9ce5f@nic.cz>
In-Reply-To: <c14f77c6-adc0-0d0b-5c17-c25c19e9ce5f@nic.cz>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Fri, 26 Feb 2021 09:48:08 -0600
Message-ID: <CAC8QAcfsiCT7AprEdfK5B38jzaANh+2rQiv3k2x=U1MPvTU3Fg@mail.gmail.com>
Subject: Re: document writing/editing tools used by IETF
To: Ladislav Lhotka <ladislav.lhotka@nic.cz>
Cc: Carsten Bormann <cabo@tzi.org>, Larry Masinter <LMM@acm.org>, Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007eb6ce05bc3f320c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JHqG9WB-ne-hVnOdPqwfv0mdhKs>
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 15:48:22 -0000

On Fri, Feb 26, 2021 at 2:06 AM Ladislav Lhotka <ladislav.lhotka@nic.cz>
wrote:

> On 26. 02. 21 8:36, Carsten Bormann wrote:
> > 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.
>
> +1
>
> For me, one of the greatest virtues of the IETF work style has always
> been that I wasn't forced to use MS Office (or similar software, which
> is often even worse).
>
>

I think a lot of people would like to use Word because of wide spread use
of MS Office in workplace. It is almost standard there. Appreciating this
even Apple comes up with Office for MAC software.

I disagree with those who say MS-Word collaboration is not good, that means
you don't know Word well :)

Having said that I have always preferred to use XML2RFC tool and continue
to use it. I am sure some people will always be happy using Word.

Behcet

> Lada
>
> >
> > 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
> >
>
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>
>