Get various AD work load and past performance statistics. Usage:
admeasurements [ --ad pattern ] [ --doc pattern] [ --copy ] [ --quiet ]
Output will provide the statistics. The author runs this regularly and the most current statistics are available here.
The tool uses the following definition for completed documents by an AD: all documents in RFC Published, RFC Ed Queue, or Approved-announcement sent states are completed. This is because the AD no longer has to perform any work on them. Note that this definition does not handle documents in AD Is Watching, DNP, Dead very well; but the different ADs use these states in different ways, so it is not easy to use them for statistics.
For other documents, the tool uses the following definition of when the document is waiting for an action from an AD: if the substate of the document is AD Followup or Point Raised - writeup needed, it is waiting for the AD, assuming no Discusses are left on the document. If the substate is External Party or Revised ID Needed, it is not. Otherwise, the main state determines this. The AD needs to do something in the Publication Requested, AD Evaluation, Waiting for Writeup, Waiting for AD Go-Ahead, and DNP-waiting for AD note states.
A document waits for the author or WG, if it is in a Revised ID Needed state, or if it has unresolved Discusses. If the document is not waiting for the AD or the author, it is waiting for other things, such as the next telechat date, expiration of IETF Last Call, Expert Review, etc.
Document processing times are calculated based on the above definitions of who holds the token for the next action. For the purposes of these statistics, no time runs before the document is delivered to the AD or the IESG. (And if that happens many times, only the last one counts.) Similarly, time is only counted as far as the AD's term extends to; time spent in the process during the AD's predecessor is not counted. Only documents that have successfully been approved are counted.
Processing times are shown as min/average/max, for the total processing time, time spent waiting for the AD, waiting for the author, and other events. Finally, a word of warning: the timing is completely based on what the tracker states are. Often these do not match reality, and significant errors may show up in the results because of this. For instance, state stays AD Followup even if in reality it should have been Revised ID Needed, or AD holding a publication request in e-mail form, and only entering it to the tracker at the time he is going to initiate the AD Review. And what if the AD marks the document as needing a revision, but in reality no revision is needed? Also, the tool is based on heuristics that read tracker web pages, a process which is inherently unreliable due to format changes over time, exceptional conditions, etc. Nevertheless, we expect the numbers to be reliable at least in terms of being in the right magnitude. The author of this tool has verified his own documents to be calculated correctly.
A WG action is counted as a proposal to the IESG on the rechartering or the creation of a new WG; only one action per year is counted per WG, as it is customary that a WG action may be discussed on several telechats, and it is not easy to distinguish these from true actions. WG terminations are not currently counted, either.
The tool can be downloaded here. Current version is 2.1.0. The tool uses some related tools as well (docage and drafttimeline), so please be sure to download them as well.
This software was written by Jari Arkko and its use and modification is free. No warranty is given: use this software at your own risk.