This consists of beginning with the base tiki install db, and adding to it any SUMO specific tables. There is also a set of actual data required for SUMO, including permissions, admin option setup, and admin modules where the code is in the database. I had a rough go at this just after the Summit last year, took me about a day to do a bad job at it.

Create generic set of templates, with product name as a variable - 1 week - frontend dev

This is so that when the software is installed, it doesn't say "Mozilla Support". We can hack what we already have into this easily. Also need to remove links to Live Chat. Since the other groups we have talked to about this don't seem to want to use Live Chat to begin with, we should defer productization of that component (and make it an optional module when we do, with separate installer).

The goal is for users to be able to untar and ./install.sh and be ready to go. The installer would need to take care of database user creation, locations of database server(s) and memcache servers (if used).

This is basically testing and documenting the method for creating a downloadable package, which would include checking out code, removing any inappropriate files (.svn etc), reverting to defaults where needed.

Define process for upgrade from one version to another (after product 1.0, thinking time 2-3 days, dev)

For each packaged release, we'll need to create a tarball. If there are database changes, we will also need to create a database upgrade/downgrade script.