I'm going to propose a small change to the site code that handles database connections. This is not highly critical code nor is there any real difference in vision with me, Fnordia or AF on its implementation. AF has even already made a patch that implemented most of the work. I just like to see how a more structured development process works out in practice.
So bare with me here.

--------------------------
Plan: Abstract site configuration details
Description
I like to abstract the way the site sets up configuration details (mainly database connection details) so it's harder to accidentally commit real passwords to svn, to make the code more exchangeable with the production and development environments without accidentally making connections to the wrong database back-end. (e.g. prod. env. connecting to the dev. env. database and visa versa.) and to allow people to make configuration changes to make the code run on other domains and servers. (localhost for example)
This would fit into the requirements of the "Webmasters" (that's the site developers (me, AF) and maintainer (Fnordia)).
But also make it easy for other people to set up a (local) copy of the site for development purposes.
Implementation
Have a general configuration file below www-root contain the database connection details and any other settings that are host specific, this file would be included with each page request.