Journal roadmap

Posted by sun on April 16, 2008 at 11:07pm

Issue Summary

By adding a simple block containing the all previous Journal entries of a page/path location, release 5.x-1.2 has been significantly improved.

This is the proposed roadmap for Journal: (using a comment, so I'm able to edit and insert issue links later on)

Comments

#1

Posted by sun on May 3, 2008 at 4:38pm

Allow adding of arbitrary journal entries

Sometimes, you simply want to add a short note, unrelated to any form.

Allow editing/deleting of journal entries

Journal entries should be editable and deletable by users granted a new edit journal entries permission.

#254303: Add log of d.o patch issues and hacks

Advanced developers should be able to create a list of applied hacks and patches on a site: From all enabled modules, select the involved module(s), enter a (private) description, and optionally a d.o issue #number. Journal should provide a list of all patches/hacks, and, if d.o allows, automatically retrieve issue statuses.

Add default journal entries for certain forms

F.e. running update.php, or enabling/disabling modules should automatically create appropriate journal entries containing the new schema version for each module, or the actual enabled/disabled modules. Not a big deal to code but always annoying to type.

Add Demo module integration

Store all journal entries in a snapshot .info file.
Display those journal entries in the snapshot administration.
Introduce snapshot revisions, so only journal entries since the last snapshot are saved and displayed.
And finally: Display links to Demo snapshots in Journal's log.

#193222: Allow to re-play form submissions

This involves (optionally?) saving the actual form_ids and (original/changed) form values in the database. FAPI3 in D6 is our friend. By adding checkboxes to the journal log, users should be allowed to save/export form submissions. Another form needs to allow to import such exported form submissions. This already sounds awesome and may be a (the?) solution for deployment/staging, but also Drupal configuration snippets.

Further Demo module integration

Introduce tags, much like CVS tags. Tag a site when it's about to go live. Display these tags in Journal's log. Revert to a tag by clicking on a tag (resetting to this snapshot or even re-playing form submissions in reverse order).

#2

Posted by okeedoak on May 4, 2008 at 3:58pm

To complete the base functionality I think that allowing editing/deleting of journal entries should be the next logical step.

Project:	Journal
Version:	5.x-1.x-dev
Component:	Code
Category:	task
Priority:	normal
Assigned:	Unassigned
Status:	active

Jump to:

Issue Summary

Comments

#1

#2