[Tools-discuss] Re: Automated mail on call for adoption and working group last call
Toerless Eckert <tte@cs.fau.de> Mon, 25 August 2025 23:30 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 C211558DE9C3; Mon, 25 Aug 2025 16:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level:
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.017, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RKLBI-nHrPpl; Mon, 25 Aug 2025 16:30:49 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 BCD1858DE9BD; Mon, 25 Aug 2025 16:30:49 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4c9n905pZTz1R9Xh; Tue, 26 Aug 2025 01:30:44 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4c9n905320zl1Tb; Tue, 26 Aug 2025 01:30:44 +0200 (CEST)
Date: Tue, 26 Aug 2025 01:30:44 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Bob Hinden <bob.hinden@gmail.com>
Message-ID: <aKzyJE3J4WsYWUPx@faui48e.informatik.uni-erlangen.de>
References: <9420de32-95a4-4c50-b59a-b28bcefdca3a@nostrum.com> <FB6B9123-3E92-4725-AFAD-34FC7473010D@gmail.com> <21f90f87-2390-4a43-8050-13d9f6ded421@nostrum.com> <C8708FCE-2296-4E9E-83D3-963927C2FDDB@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C8708FCE-2296-4E9E-83D3-963927C2FDDB@gmail.com>
Message-ID-Hash: RRIVMSIQ5QZWGPIXO7WUO4NRZQ57OHOF
X-Message-ID-Hash: RRIVMSIQ5QZWGPIXO7WUO4NRZQ57OHOF
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
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
CC: Robert Sparks <rjsparks@nostrum.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] Re: Automated mail on call for adoption and working group last call
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/EB6Tgt2sXt9bdRe0v6nsPuifFBM>
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>
My thoughts:
a) The GUI definitely needs to be "no surprise". The chair putting a draft into
call-for-adoption should be shown very explicitly by the web page if/that
an automated adoption email will be sent. AND allow to preview exactly what
the content of that adoption call email will be.
b) Instead of adding all the bells and whistles to allow modifying the email
to one's chairs likings, it might be simpler (to implement and use) an
option to select "I'll send the adoption call email myself".
The automated system can then still send a notification purely about the
state change and note that the chair is responsible for sending the
adoption call email.will or has send an adoptio
Cheers
Toerless
On Mon, Aug 25, 2025 at 07:28:45AM -0700, Bob Hinden wrote:
> Robert,
>
> > On Aug 25, 2025, at 6:37 AM, Robert Sparks <rjsparks@nostrum.com> wrote:
> >
> >
> > On 8/24/25 12:41 PM, Bob Hinden wrote:
> >> Hi,
> >>
> >>> On Aug 22, 2025, at 3:23 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> >>>
> >>> Chairs -
> >>>
> >>> The IESG asked that the datatracker send email automatically when a group puts a document into the WG state of "call for adoption issued" or "working group last call issued". That change was part of yesterday's datatracker deployment. It surprised at least one chair, for which I apologize.
> >>>
> >>> To see the details, look at
> >>>
> >>> https://github.com/ietf-tools/datatracker/issues/9142 (the request from the IESG)
> >>>
> >>> and
> >>>
> >>> https://github.com/ietf-tools/datatracker/pull/9322 (the PR from a volunteer that added the functionality).
> >>>
> >>> If you have use cases like the one Bob Hinden ran afoul of (going and adding the state to the datatracker long after the actual call had been issued) for which the current implementation will cause you trouble, please open an issue or send mail to tools-discuss. I'll make sure the IESG follows the discussion.
> >>>
> >> As Robert mentioned this change caught me by surprise. I had no idea that changing the state for a draft in the datatracker would automatically generate an adoption call email to the working group mailing list.
> >>
> >> In this case, we had already done an adoption call, so it was both redundant and wrong.
> >>
> >> It seems to me that datatracker changes that affect how working group chairs use the data tracker should be discussed on the w.g. chairs list. For this change, I can think of some improvements:
> >>
> >> - Make it clear it going to happen in the UI.
> >> - Be able to set the length of the adoption call. Many times around holidays we make it longer.
> > that should already be there. (See the "Expected weeks in state" box).
>
> OK, good to know. I didn’t know these were related.
>
> Bob
>
>
> >> - Make it optional. That is, ask if it should be sent.
> >>
> >> Bob
> >>
> >> p.s. I read the request from the IESG, but that did not include any reason why this change was needed.
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----------------------------------------------
> >> Tools-discuss mailing list -- tools-discuss@ietf.org
> >> To unsubscribe send an email to tools-discuss-leave@ietf.org
> >> https://mailarchive.ietf.org/arch/browse/tools-discuss/
>
> -----------------------------------------------
> Tools-discuss mailing list -- tools-discuss@ietf.org
> To unsubscribe send an email to tools-discuss-leave@ietf.org
> https://mailarchive.ietf.org/arch/browse/tools-discuss/
--
---
tte@cs.fau.de
- [Tools-discuss] Re: Automated mail on call for ad… Mark Nottingham
- [Tools-discuss] Re: Automated mail on call for ad… Tim Wicinski
- [Tools-discuss] Re: Automated mail on call for ad… Bob Hinden
- [Tools-discuss] Re: Automated mail on call for ad… Robert Sparks
- [Tools-discuss] Re: Automated mail on call for ad… Rifaat Shekh-Yusef
- [Tools-discuss] Re: Automated mail on call for ad… Robert Sparks
- [Tools-discuss] Re: Automated mail on call for ad… Bob Hinden
- [Tools-discuss] Re: Automated mail on call for ad… Rifaat Shekh-Yusef
- [Tools-discuss] Re: Automated mail on call for ad… Toerless Eckert
- [Tools-discuss] Re: Automated mail on call for ad… Tero Kivinen
- [Tools-discuss] Re: Automated mail on call for ad… Pete Resnick
- [Tools-discuss] Re: Automated mail on call for ad… Nour Almaani