[RTG-DIR] Chasing Routing Directorate Reviews

[Adrian Farrel <[e-mail]>]

Hi Amy and Luc,

THIS IS NOT A CRITICISM!

And to prove it - thank you very much for the super job you do assigning
reviews to the Directorate members and keeping the tool and wiki up-to-date.
The work-load is just changing (and possibly expanding) as the requirement
to do RTG Dir reviews at the time of WG last call kicks in.

I have a process question:

When a review request is accepted with its (possibly re-negotiated
deadline), whose job is it to chase the reviewer?

Obviously, anyone can chase the reviewer. The authors might be considered to
have a strong incentive, but it might not be clear to them that the document
is stuck waiting for the review (there is a flag in the Datatracker to say
the review is pending, but no state that says the document is blocked
waiting for the review). Indeed, in the previous world, if a directorate
review didn't arrive during IETF last call or IESG review, then the document
was not held up. But now, the document is blocked.

Perhaps it is the Document Shepherd's job, but in many WGs the shepherd
isn't assigned until WG last call has "completed". So sometimes there is no
shepherd, but the Directorate review is still pending.

Of course, it was the WG chairs who requested the "early review" so it could
be their job, but they have enough on their hands.

Or, it might be something we should ask you to do as admins.

So...

Should we be getting a feature added to the tool to automatically prompt the
reviewer every week when they are overdue? Should there be a reminder to you
(as admins) so that you can talk to the current reviewer and assign a new
reviewer if necessary?

Any thoughts?

Cheers,
Adrian