Re: [Int-dir] Proposed change to review assignment email subject
CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Mon, 04 April 2022 10:58 UTC
Return-Path: <cjbc@it.uc3m.es>
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 BD0BE3A2082 for <int-dir@ietfa.amsl.com>; Mon, 4 Apr 2022 03:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
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 wrOsRQz3Q6w2 for <int-dir@ietfa.amsl.com>; Mon, 4 Apr 2022 03:58:25 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 725EC3A1B74 for <int-dir@ietf.org>; Mon, 4 Apr 2022 03:58:25 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id yy13so19099798ejb.2 for <int-dir@ietf.org>; Mon, 04 Apr 2022 03:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Cwfvjbisxy2DZo70wG9uvsL2bAYAPZezVLHUEBZQOV0=; b=OlyUzEmMNHODuingxwD/a1prEmE888yKPW8TwLX0fcTeC0LeZudk8LvcG9MUmApBcL QQCC1LZ9BCmD8UTujfJTneE+CDECLfZf6Wz0LASNbaYkgJQN1lYzMaCiFaZe5wp60Fqi XaRMkwMltEcWTV7eDVC3BMOsX1jopsxB1iStTaqN2o6TQlfs4MRtzlBhlXX+X4CGMu9R vF/59zAZQFuFY5sTwpI37CWywPZayhrSjXwN6VMgEia9HYrhGz09+PV9O1BIKSIQeD9D y0ti/uih9sB+bHG+Qvh5Qbn0J2kW49dh6qor1tPT/UXcqHP8E7FYKqD96gH0kpw9m3Yh s6EQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cwfvjbisxy2DZo70wG9uvsL2bAYAPZezVLHUEBZQOV0=; b=3JM2dFj7Kv/3QwHcYA1FZLdCVj9PPLcdiqMaofBy9jXKF9pb+8CqjlvdbdAEBZfs5c kqkBuYsJHSQd2rbHqWkory6NlAb0/BJrxjtSAEg6roShFB4YNY3e6ih14WshinJ6fH8l bxpTk3j07Ou1+5UKtk7ECnzT66qjWGcADcQlubOognXqbqUmkkvsTlbJruIKfO+vkua6 ikzX4rvkylkC3kWdK6Hf/LvHreQPSGbXIrQTfyaQvjJ1TSMy3bVZ0+xvzxvRsnhygV5+ ZfueLVyFlh6BL6C+an2uI1I8nyP1C0t+4ckLpAAQ6WxZIdmSU0uGfVdNg8BtoRx+eq6i yhxg==
X-Gm-Message-State: AOAM531GNLJmaRi4puxWcyf907Us0/1GXEc0d3IugOY6eWtzaLShO6f4 yK8zZGrl9pGaxl7CCqQD7sUTNfjCcR5oeFD51ivm+Q==
X-Google-Smtp-Source: ABdhPJwmPXGKYwoGxOywizRMWtWDg+v+g9oLZmIqiYh1Y5XeYuSEkDqCLQTiL4wkV73EzdpYFeW9xZ6hQCQQSs6Brtg=
X-Received: by 2002:a17:906:cc93:b0:6e0:afec:b005 with SMTP id oq19-20020a170906cc9300b006e0afecb005mr9937622ejb.219.1649069902933; Mon, 04 Apr 2022 03:58:22 -0700 (PDT)
MIME-Version: 1.0
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> <3537ea26-a4b4-620a-7f47-6b06b1f7ecee@nostrum.com> <B9FAC37F-B565-4C9F-B8CE-2C5B5357EF9D@jisc.ac.uk> <36004fef-b786-1b4c-b19f-6a1ece18f1da@nostrum.com> <A37DFDCF-FDB8-4369-ADE8-9CEFC6F27ECB@jisc.ac.uk>
In-Reply-To: <A37DFDCF-FDB8-4369-ADE8-9CEFC6F27ECB@jisc.ac.uk>
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Mon, 04 Apr 2022 12:58:06 +0200
Message-ID: <CALypLp9D8yZ=J=gcQXagCYkcTTiq9ZBEAhq_w7epJ-zxiRgtqw@mail.gmail.com>
To: Tim Chown <Tim.Chown=40jisc.ac.uk@dmarc.ietf.org>
Cc: tools-discuss <tools-discuss@ietf.org>, "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, Ted Lemon <mellon@fugue.com>, "int-dir@ietf.org" <int-dir@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c651f805dbd201c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/vf7lcB2PJjL9wi-eEYKPX5vQ-64>
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: Mon, 04 Apr 2022 10:58:31 -0000
Hi, I think sending two e-mails would be an overkill. I think the consensus so far is to use something like: Your <team name> review assignment of <draft-foo> by <deadline> Can we move forward with this? We'll need to inform reviewers so they can update their filters if needed. Thanks, Carlos On Thu, Mar 31, 2022 at 5:18 PM Tim Chown <Tim.Chown= 40jisc.ac.uk@dmarc.ietf.org> wrote: > Well, then just send two emails, one in old school format, one as a > ‘flare’ for attention. > > Then those who like it as it is have what they need, and those who are > missing assignments have a greater chance of not doing so. > > Tim > > > On 31 Mar 2022, at 15:42, Robert Sparks <rjsparks@nostrum.com> wrote: > > > > > > On 3/31/22 3:58 AM, Tim Chown wrote: > >> On 30 Mar 2022, at 21:03, Robert Sparks <rjsparks@nostrum.com> wrote: > >>> 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. > >> So send a separate alert to the reviewer, please, that is in a format > least likely to be misfiled, parsed or spam foldered. > > That assumes that the likelihood function you point to is the same for > everyone, and we're seeing already that it is not. Removing the draft name > will introduce errors for some and apparently introduce them for others. > >> > >> The subject can simply be “New INT-DIR assignment” or something simple > like that. Without any draft name. > >> > >> That MUST be possible. > > This is starting to sound like a need for personalized subject lines. > Would the calendar subscription suggestion made earlier better fill the > need? > >> > >> And I really think this should be discussable and resolved here and not > require us to engage in the Git issue tracker > > I already said that it was I thought? But this should move to > tools-discuss so we can get all the concerned review team members on one > thread (I've added a Reply-To). > >> > >>> 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. > >> A search can include the message body. > > > > Not really the right answer in modern mail clients with the volume of > mail someone on the I* or who does work in many working groups has to see > through. > > > >> The current problem is clean receipt. > > > > And we're disagreeing on one part of what clean receipt requires. > > > >> > >> Tim > > _______________________________________________ > Int-dir mailing list > Int-dir@ietf.org > https://www.ietf.org/mailman/listinfo/int-dir >
- [Int-dir] Proposed change to review assignment em… Robert Sparks
- [Int-dir] FW: Proposed change to review assignmen… Eric Vyncke (evyncke)
- Re: [Int-dir] Proposed change to review assignmen… Tim Chown
- Re: [Int-dir] Proposed change to review assignmen… Ted Lemon
- Re: [Int-dir] Proposed change to review assignmen… Robert Sparks
- Re: [Int-dir] Proposed change to review assignmen… Ted Lemon
- Re: [Int-dir] Proposed change to review assignmen… Robert Sparks
- Re: [Int-dir] Proposed change to review assignmen… Ted Lemon
- Re: [Int-dir] Proposed change to review assignmen… Robert Sparks
- Re: [Int-dir] Proposed change to review assignmen… Tim Chown
- Re: [Int-dir] Proposed change to review assignmen… Robert Sparks
- Re: [Int-dir] Proposed change to review assignmen… Tim Chown
- Re: [Int-dir] Proposed change to review assignmen… CARLOS JESUS BERNARDOS CANO
- Re: [Int-dir] Proposed change to review assignmen… Tim Chown
- Re: [Int-dir] Proposed change to review assignmen… Eric Vyncke (evyncke)
- Re: [Int-dir] Proposed change to review assignmen… Tim Chown
- Re: [Int-dir] [Tools-discuss] Proposed change to … Tero Kivinen