Re: [TOOLS-DEVELOPMENT] Datatracker improvement requests from IRTF

Allison Mankin <allison.mankin@gmail.com> Wed, 11 April 2018 19:39 UTC

Return-Path: <allison.mankin@gmail.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D34712AAB6 for <tools-development@ietfa.amsl.com>; Wed, 11 Apr 2018 12:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_LOTTO=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HhZLdoLq7bN6 for <tools-development@ietfa.amsl.com>; Wed, 11 Apr 2018 12:39:55 -0700 (PDT)
Received: from mail-pl0-x229.google.com (mail-pl0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (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 D2A311271FD for <tools-development@ietf.org>; Wed, 11 Apr 2018 12:39:55 -0700 (PDT)
Received: by mail-pl0-x229.google.com with SMTP id a39-v6so2129650pla.10 for <tools-development@ietf.org>; Wed, 11 Apr 2018 12:39:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=38hFNdozhJ/XwzGy9Fm+W5spswdZ9Zz4cEDbPF6XYvk=; b=RChkjBgRbSgHmdRli9vYvKbiPSJq7PAv9khGX3nVJwco0alYlCGSqVWITduYiZuf7g NsutN1slXc90H5FamKi+6mxVOLM1G4d4fOnmjcfrgs9W/6PDKDXC7KQT6Z+icx3qHBuv rrWh91MrWTRLaRwapOa1hm8HY6FDIob3LpqgYladORPUvkh/yai9TWVgQl7k+c8xTKje eVE20Qi3259zotbWhSaZkan8CkvzLKw1aUUG+9tZ8Ho5QaXBwDQn65f8BSkxnzI1ge+b P4+bxOTCkTFQgdkmb/GiYPO1pu2Hz9drMjqzZbWlCClCjFAMKWAYQEk/6iOpBqV7+5X5 KkaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=38hFNdozhJ/XwzGy9Fm+W5spswdZ9Zz4cEDbPF6XYvk=; b=ioY/ZYB9PIukjTdIyn+/+04nZhPka1B7WrIQKg1HiwqeU6eexfdASEijQ8DVxNPjNZ o2Gw1APZkwpj67jEMmhB7rA9ex+BrMQwlJvNttA3MxV6aKJH1rG5nbkiV790grk67k/X Fs3kHeAE+vPw394K52pFJzD/tZUX2eHl3prCFlEu0ZXw9nvIOhQZeu9Y+SLdWig4N9Gp HITjBNsiNuNYhmMCSb6aP+GVph3xxPHokliimL69/HlNNqllpG0oir+OAbbyI6Euvyrj ZOd4JIUiK3KoUJB+NLpq4KcS9G+if5WHo2qB3Hi0XNXNW3f6Lm7oKmgV35SKdi1W85By UYtg==
X-Gm-Message-State: ALQs6tDrd5JZrhYc9bpqtAVy/qcVY5mqg8RHWps1wt5FNOXZTEO392wv lvzxuW0JXu7/PBznmonmy9DiomsWiXTYb9sjY0E=
X-Google-Smtp-Source: AIpwx49MFd+KLbUY800mWOuDPXhiU/RWnTzeaVIlBc3NiQ2ybPxg90diqDL5l8KvZsTLhQymR7SxPQavzDF/7+PVOTk=
X-Received: by 2002:a17:902:2941:: with SMTP id g59-v6mr6467894plb.55.1523475595188; Wed, 11 Apr 2018 12:39:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.229.130 with HTTP; Wed, 11 Apr 2018 12:39:54 -0700 (PDT)
In-Reply-To: <072e4e11-779f-8cf5-a783-0e9a4c4083e2@nostrum.com>
References: <1523277501.1497918.1331474032.6685152E@webmail.messagingengine.com> <c64ac6aa-e346-2fe2-7db4-079d390a46aa@levkowetz.com> <072e4e11-779f-8cf5-a783-0e9a4c4083e2@nostrum.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Wed, 11 Apr 2018 15:39:54 -0400
Message-ID: <CAP8yD=uwUcdHRBp3=cfKjW_jL4pCf9Y7D=u=sVJfRFTVRMcCcA@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, IETF Tools Development <tools-development@ietf.org>, Matthew Ford <ford@isoc.org>
Content-Type: multipart/alternative; boundary="000000000000acdf5a056997cddc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/OvHL_J33Kvs4YkCtcKDhWFMJv1k>
Subject: Re: [TOOLS-DEVELOPMENT] Datatracker improvement requests from IRTF
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2018 19:39:59 -0000

Hi, Robert, Henrik,

Thanks for the feedback.  Also I'm very pleased by the IRTF States search
in Advanced search, so thanks for taking
that in!

2. Rationalize the datatracker view when one searches "irtf" - some of
> the documents are labeled "IRTF RFC Stream," others "Active RG Document"
> - these aren't  useful as is (see attached PNG)...
>
> This needs more explanation.  The first of these indicates that the
> document is with the RFC Editor, the second that it is with the RG;
> In other words, these are very different states.  Collapsing them to
> one doesn't seem to make sense.  What is the actual need here?
>
>
The IRTF RFC Stream tags are not actually indicators that the document is
with the RFC
Editor, that's the problem.  Here are three documents that all should both
be "Active RG Document" but one is listed
as "IRTF RFC Stream" instead:

draft-irtf-hrpc-anonymity.00.txt -IRTF RFC Stream
draft-irtf-icnrg-mapme-00.txt - IRTF RFC Stream
draft-irtf-icnrg-flic-01.txt - Active RG Document
<https://datatracker.ietf.org/community/personal/allison.mankin@gmail.com/trackdocument/draft-irtf-hrpc-anonymity/>



Possibly RG Chairs have some pilot errors, but I don't know what causes it
to be set.  We have a state
Sent to the RFC Editor which is probably good enough, and I'd reserve the
IRTF RFC Stream for a future use, not
settable by the RG Chairs.

Hopefully this is clear enough for a ticket.  Let me know.


3. Datatracker view when one searches "irtf" or looks at any IRTF
> document needs to show both the IRTF State and the Tags for the state -
> the tags are missing now
>
> Ack on this for the search results.  There is limited room in the search
> results list; would it be meaningful to replace the intended status with
> the tags, to save space?
>
> With respect to showing tags on the individual document pages, they are
> shown below the IESG status already, see attached screenshot (from a
> development server where I set the 'Waiting for Dependency...' tag on a
> document).
>
>
> I'd be fine with Intended status not being there in this search result -
having the tags visible helps with tracking status, and
that is the more pressing need.

Allison


On 11 April 2018 at 15:11, Robert Sparks <rjsparks@nostrum.com> wrote:

> I'm trying to turn these into tickets and am having some difficulty with
> #2 below. I agree that it needs more explanation. The png Alexey sent does
> not demonstrate the "not useful"ness of the results without more
> explanation. That result page is showing the existing states, as all search
> results do. Is it that there aren't enough hints as to where each bit of
> state is coming from? Or something else that's making the result not what
> you want?
>
> RjS
>
> On 4/9/18 8:33 AM, Henrik Levkowetz wrote:
>
> Hi Alexey, Allison,
>
> Some comments inline as to the functionality.  Scheduling and such is a
> matter for the TMC and possibly IAOC, where it's a matter of substantially
> new functionality.
>
> On 2018-04-09 14:38, Alexey Melnikov wrote:
>
> Dear tools team,
> I am forwarding datatracker improvement requests from IRTF.
>
>
> 1. Need to be able to do a datatracker search by IRTF state - currently
> these are not available terms in the  advanced search State pulldown
>
> Fixed by Mat Ford, will be available in the next release (expected
> tomorrow Tuesday April 9th).
>
>
> 2. Rationalize the datatracker view when one searches "irtf" - some of
> the documents are labeled "IRTF RFC Stream," others "Active RG Document"
> - these aren't  useful as is (see attached PNG)...
>
> This needs more explanation.  The first of these indicates that the
> document is with the RFC Editor, the second that it is with the RG;
> In other words, these are very different states.  Collapsing them to
> one doesn't seem to make sense.  What is the actual need here?
>
>
> 3. Datatracker view when one searches "irtf" or looks at any IRTF
> document needs to show both the IRTF State and the Tags for the state -
> the tags are missing now
>
> Ack on this for the search results.  There is limited room in the search
> results list; would it be meaningful to replace the intended status with
> the tags, to save space?
>
> With respect to showing tags on the individual document pages, they are
> shown below the IESG status already, see attached screenshot (from a
> development server where I set the 'Waiting for Dependency...' tag on a
> document).
>
>
> 4. Create an online ballot for the IRSG Poll for IRTF documents.
> Functions -
>
> 4a. Create IRSG Poll ballot (IRTF Chair only)
>
> This is basically similar to IESG telechat ballot.
>
>
> 4b. Enter ballot position, Yes/No Objection/Not Ready/Recuse - (all IRSG
> members)
>
> 4c. Enter comments - one kind only, no Discuss - (all IRSG members)
>
> 4d. Comments and ballot position get emailed to IRTF Chair, IRSG, RG
> Chair of group, document authors, and RG list
>
>  4e. Mark ballot complete (IRTF Chair only) - not automatic since we
> have a looser definition than IESG's
>
>  4f. Once ballot is marked complete, IRTF Chair can request conflict
> review. Need to be able to do a datatracker search by IRSG state -
> currently these are not available terms in the State pulldown
>
> Ok, seems clear on first view.  I assume the functionality will parallel
> that of the IESG ballots where not otherwise specified.
>
>
> 5. Conflict Review fixes needed:
>
> 5a. Currently the conflict review request by IRTF Chair does not include
> enough notifications - email to IRTF Chair, IRSG, RG Chairs of group,
> document authors, and RG list
>
> Seems clear enough, and should be straightforward.
>
>
> 5b. Currently a conflict review automatically assigns the document to
> the IETF Chair and sets it into the next telechat agenda.  The IETF
> Chair manually changes both of these, and we need notifications when the
> new AD assignment occurs and when the telechat agenda date is set:  same
> set as line above
>
> Seems clear enough.
>
>
> Best regards,
>
> 	Henrik
>
>
>
>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing listTOOLS-DEVELOPMENT@ietf.orghttps://www.ietf.org/mailman/listinfo/tools-development
>
>
>