I would like start discussing a more general way to track reviews when
they are needed. Dan's new-column tweak to the existing tool makes me a
little nervous in the long run - the column won't apply to all
documents, and other types will come in making new columns leading to a
painfully sparse matrix.
Rather, I would like to work towards a system where we can request
reviews on a document at any time, for any reason.
Instead of scraping last calls to identify documents that need review,
we can make the parts of the system that issue last calls automatically
make a review request, and that request can tailor the data we need to
track for that particular review (like any constraining dates such as WG
LC or IETF LC completion).
RjS
On 7/11/13 10:23 AM, Jari Arkko wrote:
I am also in favor of the experiment and willing to participate. Besides the
changes pointed to by Brian we may also need to make some adjustments to the
Gen-ART tools (new column in the table at
http://art.tools.ietf.org/tools/art/genart/index.cgi/t=3634/fullqueue to mark
the WG review due date) and the process used by the secretary (separate mail
for WG early review?).
That's a good point. Thanks.
Jari
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
