Forum OpenACS Development: Re: OpenACS Roadmap

*smile*. I was just about to make a posting asking for the roadmap, but there you go ;).

We had some discussions about packages having roadmaps independent of the core. How shall we go about this?
Shall we edit the document to add things that are missing or will you take care of it, and everyone else posts the ammendments to this thread? I assume the latter, therefore here I go:
Performance
- (5.2): Documentation on how to scale both in hardware as well as software (how to scale your database, how to use multiple webserver, reverse proxy aso.).
- Which monitoring package are you talking about? We use a nice one for AIESEC, which I could upload somewhere and even give a writeup to be OACS 5.0 compatible, but maybe there is something out there already.
I'm missing categorization and (working) site-wide search in the basic services section.
Developer support:
- Change 5.2 and 5.1 goals. I think at the current stage it is more imporant to have a good way to upgrade and import changes from the core in a consisten manner than to have Eclipse support.
- Best practises section should definitly be out there.
- Add a book to 5.2 (containing a couple of things, like best practises, how-to aso.)
Wouldn't "Intranet" be a vertical feature, that we should aim for in 5.3. This would be the next big *selling* thing for OpenACS in fall 2004.
OpenACS Community: We should implement the installation reporting feature for 5.1 (quick summary: Report of a couple of core and maybe extended information about installations back to OpenACS.org during the installation process, with an OPT-IN approach).