Hi Tom,
At 04:04 31-01-2013, t.p. wrote:
Time to publication of an RFC can be reduced by cutting out the pauses,
which could achieved by highlighting when they occur.
[snip]
Such a list would shine a light on what is moving and what is not. This
in turn would encourage, motivate, spur those on whom the draft is
waiting to progress it (and anyone else who could contribute).
There was an interesting quote from #overlyhonestmethods. I cannot
locate it right now as the web site is whaling out.
There is a Daily Dose web page (see http://tools.ietf.org/dailydose/
). The web page provides a snapshot of what's being "published" in
the IETF. However, it does not provide a view of what is moving and
what is not moving. I don't have a view of what an area or what a
working group is up to.
Sometimes it come as a surprise when working group participants hear
that their working group is being shut down. It is possible to tell
whether a working group might be shut down. It is possible to
identify some of the issues which can delay publication. The data
for what you suggested is available from the datatracker. The data
to identify WG activity is also available. I don't know how to
assess progress though.
Regards,
-sm