Similarity to Journal - merge projects?

The only issue thus far is that the journal module provides a tool to manually write entires to the database to keep a running log of activity in the database. Again, this a manual process which keeps a running "journal" of manually entered items.

The blame module works a bit different and automizes everything in one location. It programmatically determines changes made to form submissions (content, admin forms, etc) and logs them in its own fashion.

I am absolutely open to contacting the modules maintainer and discussing a possible merge, but our approaches currently are completely opposite in that respect. As soon as I am able to gain more insite into the possibility of a migration of these efforts I will update this thread regarding the details of that information.

Thank you for your request!

I've worked with journal, and this module seems sufficiently different and useful to warrant a separate project on its own merits.

We have had about three conversations in the last week where this module would have been very useful - we'll likely be evaluating it in the next few days.

bonobo, thanks for the reply. I would greatly appreciate the evaluation and feedback as I feel this provides a lot potential moving forward, but still requires a lot of tightening and feature additions to consider this stable for an official release. Your feedback is greatly appreciated.

To note, this module has basically been tested using content nodes and some core admin forms, but has not been put through the ringer using CCK or VIews, or other highly advanced forms that can be added by means of contributed modules. I think there is a lot of uncharted territory here that needs to be tested so we can make this as solid as useful as possible.

@All - I would like to leave this thread open to come to a definitive resolution before I remove this project and attempt a migration with the journal module. I will be reaching out to the maintainer this week to see if this is a reasonable request and the level of effort for a migration, unless of course the community decides otherwise.

Blame probably fits best as #193222: Allow to re-play form submissions (which is part of the #247635: Journal roadmap). I think it makes sense to merge it in with Journal.

Even though Journal expects the administrator to initiate the logging and Blame wants it to be automatic, there's no reason why those two things can't coexist in the same module.

I like greggles' idea of a separate Journal branch for this merger.

I'd love to investigate to merge this functionality into Journal. After all, programmatically recording form submissions resp. configuration changes is way higher on Journal's "roadmap" than the re-play facility (which I'm not sure makes sense anymore in the rising days of Features module).

It's good to see that there is already working code, so we can actually compare the data schemas as well as technical/logical implementation.

Strictly speaking, I guess that the main feature is to record the actually submitted form values (excluding internal FAPI values, but including the clicked button), and to auto-generate a log message, when not entered manually.

A new branch wouldn't be necessary for adding that functionality.

Deciding not to merge with Journal. Journal's approach to this is more manual and works great in certain / specific workflow environments, while the Blame module works better in others. I will be keeping this module as its own module going forward.