Re: [Int-dir] Proposed change to review assignment email subject

Robert Sparks <rjsparks@nostrum.com> Wed, 30 March 2022 20:04 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE6F3A0ED0 for <int-dir@ietfa.amsl.com>; Wed, 30 Mar 2022 13:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.689
X-Spam-Level:
X-Spam-Status: No, score=-1.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 EfqY6hFvCien for <int-dir@ietfa.amsl.com>; Wed, 30 Mar 2022 13:04:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 5E1B83A0FCA for <int-dir@ietf.org>; Wed, 30 Mar 2022 13:03:49 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 22UK3iUb036571 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 30 Mar 2022 15:03:44 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1648670626; bh=+7ex0f9LCBhqy5tDdEcXw4MbJ7qSeQhersAi0gK+pMo=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=Hj7e4SZijY9UjqFczNqKv3bFaodT4Sui2P9RXLUscFKSpOeFMc1ragm/TOyUpaCR2 xNOWIO/SUERZVCgKlDaIffUJEJN486MNGkWVa9nwAGH2ICKAZUaoCsy3I2f3IuSe3Z ybNR7KkbdsK1VYTAxbGcl52TTYU8amkm+Do4t1b4=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Content-Type: multipart/alternative; boundary="------------L4GrCnZ0x30DGrB6jt3vtCLK"
Message-ID: <3537ea26-a4b4-620a-7f47-6b06b1f7ecee@nostrum.com>
Date: Wed, 30 Mar 2022 15:03:38 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: Ted Lemon <mellon@fugue.com>
Cc: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, Tim Chown <tim.chown@jisc.ac.uk>, "int-dir@ietf.org" <int-dir@ietf.org>
References: <CC84AB46-8B73-4042-B873-360C22774992@cisco.com> <4EE390BC-04FC-4263-938D-386ADE5A1CB1@jisc.ac.uk> <a768e222-7417-7426-3c08-cd7a5ebf8cf0@nostrum.com> <CAPt1N1kW7aGqDZXJPu+xmHM0hD40_dyLTHZMfd-70n9Bqy6C_A@mail.gmail.com> <2252b350-3937-96e0-bf76-4bb26fef82ac@nostrum.com> <CAPt1N1mvGBrT+R+oG7LjsqiV3tDfz8J8iOvXrtcpbvyayrJqhQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <CAPt1N1mvGBrT+R+oG7LjsqiV3tDfz8J8iOvXrtcpbvyayrJqhQ@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/erz25Y4C4bsa5dUEfh3Q1V9PPLA>
Subject: Re: [Int-dir] Proposed change to review assignment email subject
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2022 20:04:16 -0000

On 3/30/22 12:43 PM, Ted Lemon wrote:
> Sure, but I would think that we /wouldn't/ want a review notification 
> to match that rule, right? Otherwise it's going to get filed in the 
> bucket for the draft and possibly not land on the reviewer's to-do list.

Ted - Other people _want_ these to go into their draft buckets. People 
have their own workflows, and having draft names in these announcements 
are already part of them.

When I am scanning email, I _personally_  want to see the draft name in 
the subject - a long string of things with a semantic of "you have a new 
review assignment, read the message or click on some links to find out 
what it is" is not welcome. Further, if I had some reason to go back 
later and find the message that pertained to a particular draft, such 
mining would not be ok.

RjS

>
> On Wed, Mar 30, 2022 at 1:42 PM Robert Sparks <rjsparks@nostrum.com> 
> wrote:
>
>
>     On 3/30/22 12:29 PM, Ted Lemon wrote:
>>     Do notifications to reviewers go in the archive?  If so, why?
>     Fair point - I'll look to confirm. But even if they don't, I know
>     of users that have filters in their own mail processing chains
>     that look for draft names in the subject line.
>>     Could we have one for the archive and one for the reviewer?  It
>>     seems to me that these are two separate functions. I don’t
>>     understand the first, but don’t object to it. I do object to the
>>     second being compromised in favor of the first.
>>
>>     On Wed, Mar 30, 2022 at 13:18 Robert Sparks
>>     <rjsparks@nostrum.com> wrote:
>>
>>
>>         On 3/30/22 10:14 AM, Tim Chown wrote:
>>         > Hmm, I would avoid any instance of the draft name in the
>>         subject line.
>>
>>         The draft name MUST be on the subject line.
>>
>>         Many people search the archives (using mailarchive) for
>>         messages related
>>         to drafts looking for the draft name in the subject line. The
>>         datatracker even assumes this with the searches it provides
>>         in the
>>         buttons on a document's page.
>>
>>         RjS
>>
>>         >
>>         > Or do we have to say that in git?
>>         Do you mean github? If so, then no - participating on lists
>>         is fine (but
>>         this really should have gone to tools-discuss).
>>         >
>>         > Tim
>>         >
>>         >> On 30 Mar 2022, at 07:08, Eric Vyncke (evyncke)
>>         <evyncke=40cisco.com@dmarc.ietf.org> wrote:
>>         >>
>>         >> Forwarding Robert's email just in case some filters were
>>         too paranoid and dropped it ;-)
>>         >>
>>         >> -éric
>>         >>
>>         >> -----Original Message-----
>>         >> From: OPS-DIR <ops-dir-bounces@ietf.org> on behalf of
>>         >> Reply to: tools-discuss <tools-discuss@ietf.org>
>>         >> Date: Tuesday, 29 March 2022 at 17:31
>>         >> To: "secdir@ietf.org" <secdir@ietf.org>,
>>         "yang-doctors@ietf.org" <yang-doctors@ietf.org>,
>>         "gen-art@ietf.org" <gen-art@ietf.org>, "int-dir@ietf.org"
>>         <int-dir@ietf.org>, "iot-directorate@ietf.org"
>>         <iot-directorate@ietf.org>, "ops-dir@ietf.org"
>>         <ops-dir@ietf.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>,
>>         "tsv-art@ietf.org" <tsv-art@ietf.org>, "art@ietf.org"
>>         <art@ietf.org>, "i18ndir@ietf.org" <i18ndir@ietf.org>
>>         >> Subject: [OPS-DIR] Proposed change to review assignment
>>         email subject
>>         >>
>>         >>     Please take note of
>>         >>
>>         https://github.com/ietf-tools/datatracker/discussions/3760.
>>         If the
>>         >>     change proposed there will cause problems for you, add
>>         a comment there,
>>         >>     or reply to tools-discuss@ietf.org to let us know.
>>         >>
>>         >>     RjS
>>         >>
>>         >> _______________________________________________
>>         >> Int-dir mailing list
>>         >> Int-dir@ietf.org
>>         >> https://www.ietf.org/mailman/listinfo/int-dir
>>
>>         _______________________________________________
>>         Int-dir mailing list
>>         Int-dir@ietf.org
>>         https://www.ietf.org/mailman/listinfo/int-dir
>>