OpenACS is not going to be a "port" for very long. OpenACS 4 is a superset of ACS 4, in that it will run on Oracle *and* on PostgreSQL. We will certainly improve OpenACS 4 as we see fit, given that ACS Classic Tcl is, for all intents and purposes, dead.
Now, the question is: how much do we need to improve it? There are some things like the content repository that we'd like to improve. The core OpenACS team will probably handle that task. However, the core OpenACS team is not going to get deeply involved with specific packages like CMS and ecommerce: we're going to let the developer community address those functionality-specific issues.
*That* is the strength of OpenACS 4: developers can add features in a packaged, modular way, without involving the OpenACS core group. Thus, while we see some level of improvement that can be made to the core, the real innovation in OpenACS 4 is going to come from package developers out there... Get PSYCHED, because the spotlight will start shining on package developers within a couple of weeks!
