The Journal Module
When more than one person is working on a site there invariably comes a moment when something breaks but nobody changed anything . . . or did they? A version control system catches the file changes, but what about Drupal settings? A new module addressing this issue appeared on the module RSS feed last month so I took a look.
The Journal module (Release 5.x-1.0) is very straightforward. It adds an additional text field named "Journal entry" to all Drupal forms via hook_form_alter.
The field is mandatory for system settings forms, and non-mandatory for other forms. Some forms are excluded by the module (search_block_form, user_login_block, devel_switch_user_form), but there is no user setting to add additional forms to the exclusion list.
The journal entries are viewed at Administer >> Logs >> Journal entries. The date, user, journal entry and form's source URL (which it calls location) of each entry is displayed. These entries are stored in a database table created by the module.
The Journal module has a single access permission: access journal. Only accounts holding this permission see any of the Journal module functionality. This means you can create account roles that can change system settings but do not fall under mandatory journaling (I consider this problematic, but have worked in shops that would consider this a welcome feature).
The module also has an Administer >> Site configuration >> Journal page, but oddly there are no settings. In reviewing the module code, there actually doesn't appear to be a settings form included in the module.
For content the Journal entry field is competing with the Log message field. Although these fields are logging information for different reasons, both are capturing the same information. There will likely be annoyed users at sites wanting to use both functions.
The module's stated goal is "to allow developers and site administrators to record and track all actions that have been performed to setup a site or change its configuration" . From this reviewer's perspective it's off to a good start. This would be a good tool in a cooperating team. Or in my case, tracking otherwise forgotten changes on some small sites I maintain solo.
If your requirement is a mandatory audit log this module isn't it. For example, the user permissions form is not a system setting form so the journal entry is not mandatory. Given user permissions can have a dramatic effect on site functionality (e.g. A module's anonymous access is turned off breaking a feature) you'd probably want mandatory logging for it.
The Journal module project page is http://drupal.org/project/journal. Newly released into the community, I'll be following its progress with interest. Journal Module 5.x-1.0 README.txt