Loquacity - Alive again

After a very long hiatus, I’m working on Loquacity development again. This past year has taught me something: don’t shoot for the stars. Having a road map is very useful, but it must be realistic according to the resources at hand.

Since there is only one developer, myself, I need to restructure my goals and the road map to reflect that. Hence, many features I’ve planned for Loquacity 1.0 will not be. What I am considering is:

• cleaning the current code
• fix known bugs
• removing code/features that don’t work
• make the installer work near flawless
• release

Along with the above, I need to remove people from the project that never did anything. This is more a management type thing, only on Berlios.

To start, I’ve fixed a nasty bug in the Comment admin interface. The SQL statement to retrieve the comments was very broken; a junior level mistake that caused a match of LIKE “%”. Of course, that won’t work.

Deleting comments is much faster now, as some redundant queries were removed.

In the interests of improving the speed of Loquacity, I’ve begin keeping a list of Database tables that need indexes added. These changes will be implemented in the Upgrader and base Database schema.

Loquacity Feature - Automatic Backups

A new feature available in Loquacity alpha2 is automatic backups. The data in yourdatabase, along with your configuration file, will be archived:

• During software upgrades
• Periodically

That should provide plenty of safeguards for a person’s data, as long as the backup is downloaded.

Later I want to extend the backup management to allow 3rd parties to provide plugins that allow a person to backupother items. For example, if a 3rd party creates a photo album plugin, part of the plugin could be a module that causes the backup to also include the photo albums.