You can use this page to describe and develop the Exit Strategy document.
I'd suggest using
Headings
Seperated by lines... (use the tool bar above)
Technical implementation
Minimum feature set
Analysis of ZOPE/PLONE
Analysis of Forge and Repository area
Possible future replacements/upgrades
- Consider gforge: http://gforge.org/ for hosting the actual forge, and leave plone for the front end. The gforge might be simpler for building forges per project, has all the stuff we use plus more all integrated - and designed for hosting software projects. So should be cleaner for setting up new projects... for instance there is currently many manual steps, eg. trac, permissions, software centre...
- Should definitely look to use LDAP for maintaining logins - would be able to work across, plone, apache, trac and subversion from a single registration... thus user registration and setup would be simpler.
Hardware
- Apparently zope/plone is very resource hungry, recommended to run zope+plone on one machine (dual pentium 4) and another box doing all the other work.
