Hi Dave,
I think its best to have ETP handle it. When you create a new subsection/ETP instance, you have the option to piggy back on an acs-subsite or create a new ETP instance.
Still my opinion in going forward on OpenACS code is to remove the ETP stuff on acs-subsite. Of course if its your client project it would not matter.
Making content available to another package (acs-subsite) from another package (etp) maybe handled better with portlets. (Not sure thought, dont know about portlets except the concept). There was a time I asked DonB a long time ago (no sure if he still remebers it), is to make ETP piggy back on all packages by using the package_id on the cr_folders. It was an interesting idea and possibly a workable one, although now I think it was a silly idea. Because dotLRN seem to have showed the way for me how to get content from another package.
