Remember that the ACS is really a toolkit for website development, not
a website-in-a-box. As the toolkit matures, more and more
out-of-the-box capability is developed (wait 'til we get OpenACS 4 up
and running!). ACS 3.2 isn't very orthogonal, i.e. only part of the
modules are user group aware rather than all of them, etc. That's due
to the incremental nature of the development of the toolkit. ACS 4 is
among other things meant to be much more orthogonal, with the goal
being that all modules be subsite and group/party aware, that the
categorization mechanism be applicable to all content, etc...
Don how long is the bit when the openacs4 is expected These are your comments at the arsdigita site.
We'll be requiring PG 7.1 for OpenACS 4, and it is now in a kind of
quiet, semi-internal beta test phase, with a more widely-announced
beta to follow. OpenACS 4.1 should be released in three-four weeks,
and that's the version we should target porting.
This will be a more difficult port than the 3x versions, since aD's
gone hog-wild on using Oracle features in 4x.