this is the general state of things.  below is a list of either unfinished
or planned work for the present and future of dbconfig-common

- bugs
  - i suspect the "back" functionality doesn't quite work

- database support
  - general
    - some kind of support for multi-db applications
	 - provide a normal-user-accessible script for setting up databases
	   (for running out of public_html type directories etc).
    - support for other database types (sqlite, others?)

- general
  - think about how this should tie in with the webapps-common.
  - begin discussion on having the "best-practices" document incorporated
    in some form as debian policy.
  - how we handle admin passwords should differ based on remote/local.
  - ask if the user is to be completely deleted or only have privileges
    revoked in mysql.  this is the default in pgsql, but in pgsql the drop
    will fail if the user owns other databases (not so in mysql).
  - a test harness for testing all the features of this package for
    qa purposes.   
  - support for other package formats, such as rpm.
    - should we still depend on debconf or extract the debconf questions
	   manually?

- unresolved issues
  - mysql does not support ssl for the time being (see bug #291945)
  - should we remove users completely at purge?
