IETF Logo Mail Archive

[Tools-discuss] Re: Introducing a new roadmap framework

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 18 December 2025 04:41 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@mail2.ietf.org
Delivered-To: tools-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id CD3409C22610 for <tools-discuss@mail2.ietf.org>; Wed, 17 Dec 2025 20:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VOkZdDv1x5O for <tools-discuss@mail2.ietf.org>; Wed, 17 Dec 2025 20:41:28 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4DEB29C22608 for <tools-discuss@ietf.org>; Wed, 17 Dec 2025 20:41:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2C03138B4C for <tools-discuss@ietf.org>; Wed, 17 Dec 2025 23:41:21 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id NHQQvt5mL3df for <tools-discuss@ietf.org>; Wed, 17 Dec 2025 23:41:19 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1766032879; bh=o5oqBbYrysTB7k8WMXuYEcvG1uTQlQiqX/XuWTnezgU=; h=From:To:Subject:In-Reply-To:References:Date:From; b=huBL2dgJEFT7e2CjFk8ZP+oDLixe9h8GJ/WLVZiNOGHnjP7V+SsqebNEv3NRl7GjN 6MLjNsxzbMzZ/RWqECUJNtPtsGx1z/vBiVF7VVOzrTZ7ZJc38QV+KwrjME26Cl9Azj E0ALB6885/A8QOYZHzuiGW3N9eOaR0bTZjngxgR0eSHAyX4bq0rFKQDBXJVx2Iw5uH PpCVi7oWLAB6R/K0K8697hZVi3fme9UhhvgN+I5Bd7igLze+NWCxoVMaLhbjIRfY2k HyGwEA0qAXfEY9pv6KObc9pMmXJsa0X0wdCuFg0hH9XofWW5upjgndbX3Cqu5RA3gn CsVouyQJAKjlw==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1820138B4B for <tools-discuss@ietf.org>; Wed, 17 Dec 2025 23:41:19 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 10A64180 for <tools-discuss@ietf.org>; Wed, 17 Dec 2025 23:41:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tools Team Discussion <tools-discuss@ietf.org>
In-Reply-To: <CABcZeBPcfpMaGc3bmt4xX2WUf1h+6a=M2kFYp6-7BX93_QbE7g@mail.gmail.com>
References: <4494cd7e-d315-4174-ace1-6e4eaae95301@nostrum.com> <CABcZeBPcfpMaGc3bmt4xX2WUf1h+6a=M2kFYp6-7BX93_QbE7g@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 17 Dec 2025 23:41:19 -0500
Message-ID: <19801.1766032879@obiwan.sandelman.ca>
Message-ID-Hash: HUGRLJ5DPDCWQZNEPIPA6TEOD3XDYKQV
X-Message-ID-Hash: HUGRLJ5DPDCWQZNEPIPA6TEOD3XDYKQV
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] Re: Introducing a new roadmap framework
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Bf-XeGc8QBooG2ltqjDmEiJQXE0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

I agree with EKR: this is the wrong level of abstraction for communicating
with the community.  It's probably good for the tools-team internal planning.
In that, I think it's a good step forward.

(Every time over 20+ years that I've found a useful Agile/XP Sprint/Story
system, it's an out-of-tree plugin for trac,redmine,jira,gitlab,... which
someone decides to break in order to "improve" something I don't care about.
Except that first one for Trac, when it didn't support plugins, and I just
hacked in the fields I wanted, and didn't upgrade when they broke it, and
then that the company that was using it went broke... So I take your github
isn't really very good at this comment to heart, yet everything else is as
bad or worse)

Eric Rescorla <ekr@rtfm.com> wrote:
    > ## Support for the RPC

    > I'm having trouble understanding the rationale for building a new
    > editing tool. I'm more than prepared to believe that the existing
    > toolchain is a mess, but ISTM that the rest of the community gets along
    > just fine without a custom editor (in some cases, they even use
    > Emacs!). It's certainly possible that there's some specific reason why

I didn't worry about this part as I don't know what the RPC needs are...
I thought it was not a text/markdown/xml-editor.   And I do use Emacs. :-)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.46.0 | Report a Bug | By Email | System Status