Re: Possible modification to issuing Working Group Last Calls from the datatracker

Robert Sparks <rjsparks@nostrum.com> Sat, 27 September 2025 15:37 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@mail2.ietf.org
Delivered-To: wgchairs@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2524B69D9B6A; Sat, 27 Sep 2025 08:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 1.255
X-Spam-Level: *
X-Spam-Status: No, score=1.255 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_SBL_CSS=3.335, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 a6knoh9nG2ew; Sat, 27 Sep 2025 08:37:45 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 9878C69D9B67; Sat, 27 Sep 2025 08:37:45 -0700 (PDT)
Received: from smtpclient.apple ([108.147.185.177]) (authenticated bits=0) by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 58RFba5X028506 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 27 Sep 2025 10:37:37 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1758987458; bh=qhrkeRYtNdNCr6obT21XgbiqW1f7vX6bo0RuwsvpNTw=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=bMTJlZI9g5TFimIhSYReqZGcnz0BH86MnfmD4EQDfxGa2os0z5zLCoKPDGz6B4WOd U/7xhpwcljkMYACbUfW+7eiq1+K7KCPAbnPiazX8YJbG6+JlboVKBccXkDrOzuaePZ GKn5CpCeqOq0wcloy6l2hO+qrwxmxwsE4BHX8FQ0=
X-Authentication-Warning: raven.nostrum.com: Host [108.147.185.177] claimed to be smtpclient.apple
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Robert Sparks <rjsparks@nostrum.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Possible modification to issuing Working Group Last Calls from the datatracker
Date: Sat, 27 Sep 2025 10:37:21 -0500
Message-Id: <96E3FCC7-4C9C-4111-BA3E-9817A59C164A@nostrum.com>
References: <17235.1758932608@obiwan.sandelman.ca>
In-Reply-To: <17235.1758932608@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPhone Mail (22G100)
Message-ID-Hash: QOFH2GDFFVBYBD7L3KMPPTJO6B3T7EDI
X-Message-ID-Hash: QOFH2GDFFVBYBD7L3KMPPTJO6B3T7EDI
X-MailFrom: rjsparks@nostrum.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: wgchairs@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/tymCKithsac29dUZTlnBuLSnDMM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

The surprise was that the datatracker started sending a new message to the lists that it hadnt previously done, and didn’t let the chair know that was going to happen. 
Sent from my iPhone

> On Sep 26, 2025, at 7:24 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Robert Sparks <rjsparks@nostrum.com> wrote:
>> I have a proposal for a change to the workflow to allow this. It's currently
>> running at:
> 
>> https://dt-issuewglc.dev.ietf.org
> 
> logged in, tried it:
> 
>> Please experiment with the workflow for issuing wglc for documents in your
>> WGs - start with the edit button next to stream state - the rest is hopefully
>> self explanatory.
> 
> Do you mean the Edit button next to, "WG State"?
> okay, yes.  Seems nice.
> 
> I have some quibbles about the template text, particularly around the word "support".
> But, I can, I see, edit that as WG chair... so meh. It's fine.
> 
> (I personally find +1s to be a waste of time, and I really do not want to
> hear about how authors support the document.  But that's me.  I want to hear things
> like, "I have read XXXX.  My concerns around issue BLAH are resolved")
> 
> {I also question whether we need to YET AGAIN talk about IPR}
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> <signature.asc>