I lean to this structure:
/projects/openacs3/
/projects/openacs4/
/projects/opneacsdev/
First, I am assuming these are sub-site enabled.
If there are still communities out there that might want to acccess OACS 3.x packages and might even want to develop new packages for 3.x it makes sense to give them a place. If there are not enough people out there working on 3.x, then that section of the site atrophe's and it becomes a historical record, but at least the packages are accessible.
Non-package development would always happen on openacsdev. Package development would happen on the appropriate version openacs4.
One potential problem is if there are seperate discussion boards or other community functionality. Spliting up core and package development may be very logical from the OACS administrator point of view, but my weaken the community by creating artficial barriers between folks building packages and folks extending the core.
Those are my thoughts from the perspective of administrator that wants to install OACS functionality, but does not have the skills to develop new functionality.
