Re: [Tools-discuss] Why post text and not XML? (was: I-D statistics)

Carsten Bormann <cabo@tzi.org> Sat, 16 March 2024 22:07 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A856C14F61D for <tools-discuss@ietfa.amsl.com>; Sat, 16 Mar 2024 15:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZ73uyeEWkXs for <tools-discuss@ietfa.amsl.com>; Sat, 16 Mar 2024 15:07:19 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EB9DC14F60C for <tools-discuss@ietf.org>; Sat, 16 Mar 2024 15:07:19 -0700 (PDT)
Received: from smtpclient.apple (unknown [202.4.29.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4TxwFw2FmMzDCbj; Sat, 16 Mar 2024 23:07:15 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ZfYV05Ij_PPbJTS_@faui48e.informatik.uni-erlangen.de>
Date: Sun, 17 Mar 2024 08:07:02 +1000
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, tools-discuss <tools-discuss@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <67F2FA33-FBE8-448A-9021-1CD5E7452833@tzi.org>
References: <1952067F-6467-4BEC-9CA5-BB8B16FA662B@tzi.org> <14807.1709682543@obiwan.sandelman.ca> <effb521c-1e20-cff8-acd3-17212a6b3fb9@gmail.com> <447A96F55A3D36851570B3B6@PSB> <60f18950-a2e0-16be-3a05-33f9a637062d@gmail.com> <CABcZeBPzYvscB3yeaRYQg6waR1BvqQMhJ+GpoKAZThoDvREs+w@mail.gmail.com> <ZfYOMEGdrGaz3BXB@faui48e.informatik.uni-erlangen.de> <512D8379-8E25-4FA6-B533-B872003126C2@tzi.org> <ZfYV05Ij_PPbJTS_@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/gDtLhVPqegqNT-ck16n_eFhucpc>
Subject: Re: [Tools-discuss] Why post text and not XML? (was: I-D statistics)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2024 22:07:21 -0000

> How do i create such 'crefs' from markdown ?

Using markdown footnote syntax:

   This encoding only supports even-shaped widgets. [^foo]

   [^foo]: We have to put in support for odd-shaped widgets, as well.
       Maybe we can snap off the odd part first?  Or use CBOR? :-)

> A github issue or pull discuss is a process. The result of this
> could/should be an inline comment, maybe even with backreference to the issue/pull.
> Aka: both have different purpose and could well co-exist/help each other and
> improve the creation/tracking process.

Until someone does a convincing PoC, I’m skeptical.
Please surprise me.

> I very much like github process. I struggle figuring out, how to best
> keep discussions on WG mailing list and github in-sync.

Please talk to your WG chair.
(Might involve a mirror, I know.)

> I think/fear
> that we would have to provide drops from github to mailing list upon
> closure of pull/issues, so instead of that the comment in the document itself
> might be another way to keep track of such "WG work" that happened on github
> instead of the mailing list. Thats why i started to get interested in this thread.

Indeed, discuss on your git forge, decide on the mailing list.
Having someone summarize a meandering git forge issue thread to the mailing list can be a great help to focus on the actual decisions needed.
(BTW, that someone traditionally is the WG chair…)

Grüße, Carsten