Packaging issues I didn't yet get around to, or which I didn't yet confirm as
solved.

*************
* Note: For all these items, patches are appreciated!
*************

[RC] means that I won't release a Debian version without that is solved, so if
you see this below and you're not looking at the subversion version... There's
something wrong.

--Jeroen

long-term TODOs
  * maybe move styles to their own packages? (what about l10n for styles?)

Normal TODO's:
- Multiboard security okay? Yes. [Jeroen]
- Multiboard: avatar dir is shared, fix that -- sort of fixed see README.multiboard [JM]
- Make sure there are good and useful errors if for example php4-mysql module
  isn't installed, an invalid dbms type is specified, stuff like that.
- PostgreSQL setup, also the default SQL needs to be fixed analog to MySQL -- ok [JM]
- Purge user on package purge (but not DB, or ask about DB, do note about that)
- Revise the taken-from-website description to be as useful as possible for
  people deciding whether or not they want phpBB installed
- Download and apply some useful mods (there are quite some)
- Provide a way to reset passwords, in case the admin looses control over the
  board.
- What's the doc-base stuff... probably need to do something with it?
- Translations: Translators can ask subversion access, so they can check in
  translations themselves.
- Debconf has half-baken support for backup... workaround someday/write a patch
- Have #231186 fixed, and remove the workaround in this package
- use dpatch or dbs or something like that, currently both are too
  overengineered for my purposes (but that will change) -- ok, quilt [JM]
- Support mysql4 (enable transactions)
- Use UCF on apache.conf (--three-way)
- Report bug about ucf --three-way going crazy on disappeared files

Possible enhancements:
- Have admin choose the database prefix - is this useful? Will only do it if
  requested, because I don't think so
- Rename config.php to database.php, which is more appropriate? Upstream calls
  it config.php