PageOutline(2)

Here are some possible topics for the Vancouver Code Sprint:

The public-facing tools were all converted to django, but the password-protected tools were not. Some candidates for this sprint:

• Liaison Manager

• WG Schedule Requester (Neustar is delivering this 11/28/2007)

• WG Proceedings Manager

• Non-WG Mailing List Approval

• IETF Announcement Sender

• Initial Revision Approval Tool (note that I don't think we have the perl source to this tool)

This is open for brainstorming.

• Email Address Changing Tool

• BOF Session Requiest Tool

• I-D Management Tool (request to publish as RFC, withdraw, replace, resurrect)

• WG Charter Management (phase 1 and phase 2)

django makes atom feeds easy - so what feeds should we create?

From Paul Hoffman:

''Hi again. You already have all the data for this one. It would be grand if a tool told me a week before my draft was going to expire that, well, it was going to expire. You could probably just pore through the drafts database each night looking for "expiration_date == today + 7" and send mail to all the authors. The message should say something like "we know you might want to let this draft expire, and we're not encouraging you to renew it unless you want, but in case you wanted to keep it alive, here's a chance before it expires".''

This is open for brainstorming.

• Liaison Management Tool Update

• Addition to the WG status page that indicates whether an IPR disclosure has been filed on a draft -- Lars

• Addition to the WG status page that ties a draft to its milestones and flags missed ones -- Lars

• Addition to the WG status page that logs recent activity, or activity over time -- Lars

• Addition to the WG status page that lets users expand and collapse the various document categories (active/expired/iesg/published/dead/etc.) -- Lars

• Addition to the draft history page that follows the "replaced by" information such that versions of a draft that have had different names can be accessed and diff'ed -- Lars

• HTMLify the output of idnits (just run through rfcmarkup?) -- Lars

• include SVG version of Bill's draft dependency graphs in the draft history page (and think about if there is a more intuitively understandable presentation) -- Lars

• draft history pages for non-WG drafts -- Lars

• Addition to the WG status page that shows the RFC Editor state for a draft instead of the generic "RFC Ed Queue" -- Lars

• Addition to the WG status page that shows the area the WG belongs to -- Lars

• Combining Bill's and Jari's IESG statistics on one set of common pages -- Jari (Done)

• Separating the reliable and unreliable data in Jari's IESG statistics (substates are not used by all ADs, for instance, while publication requests and approvals can be tracked fairly reliably) -- Jari (Done)