Silly TODO list; most of this is post-woody.  For woody we're mostly
in a maintenance cycle; no real new features.

1. Interface abstraction and multiple interfaces.  The menus in
reportbug can be handled by a set of UI functions in a Python module.
reportbug_ui_text is there; reportbug_ui_newt is coming, but its menu
implementation leaves something to be desired... a new menu may have
to be designed from scratch, or we may have to reimplement the nice
newt dialogs in slang (boo, hiss).  reportbug_ui_gnome... is in my
head.  And will be staying there for a while, probably.

2. Is debconf support worthwhile?  I don't see /etc/reportbug.conf as
being something most people need to edit... the defaults are IMHO
sensible.  But feedback is welcome... maybe a couple of things could
be debconf'd on first install, like interface choice (see #1).

3. BTS management interface for developers.  You should be able to
view the list of bug reports for a package, construct a list of
actions, and produce one giant email to control@bugs.debian.org to do
that.  Forwarding and merging, which both can be major PITAs, will be
helpful.  (See #77424)

4. i18n/l10n.  Python includes gettext support; however, the Python
2.x interface is much better so reportbug will be using that when 2.1
makes it in.  (i18n/l10n with reportbug may not make much sense, since
the reports have to be in English for most maintainers to understand
them... unless we figure out some way to get bug reports translated
for maintainers.)

5. Decruft for Python 2.x: use string methods, mainly.

