Savannah database restructuring effort:
=======================================

At the moment we would like to talk only about the new features which
require the database change. The exact implementation (and the
reulting fields to be introduced) will be worked out once we are
committed to a set of features.

List of new features:
- ---------------------

Feature: Support/Task/Patch tracker subsytems should work like the bug
	 tracker (provide configurable fields).

Feature: advanced email notification for the tracker
	 subsystems. E.g. it should be possible to have mail sent to
	 dedicated users based on the category of the bug.

Feature: Improved news subsystem moderation and notification. New
	 items can be automatically sent to a mailing list.

Feature: Project admins should be able to select whether they want to
	 use the Savannah provides subsystems or point the link at
	 substitutes of their choice. E.g. a project may choose to
	 point the bug tracker link at a bugzilla installation on
	 another server or the CVS browsing link may point to a remote
	 CVS repository.

Feature: Group types specify the default values for their projects,
	 but all fields should be overridable by the project admin
	 (as far as this does not clash with the site administrator
	 configurations)

Feature: For site specific database changes a 'joker' table will be
	 provided, so that all these changes can be found in a well
	 defined location (might be the correct place for the
	 fields with special connotation for GNU/FZK/CERN/...)


Cleaning up of the database:
- ----------------------------

The naming scheme for tables will be unified and tables which are no
longer needed will be deleted (e.g. remnants of SourceForge 2.0).


Migrating to the new DB structure:
- ----------------------------------
Scripts to migrate a present Savannah database structure to the new database
structure will be provided.