Proposal
Begin to make dotlrn communities behave like subsites
1) Add subsite_p to apm_package_versions table default 'f'
2) Set subsite_p for dotlrn to 't'
3) uncomment code in subsite::package_keys to pull from this column
4) make all dotlrn community groups application groups for the dotlrn package instance they are under.
In this way I can determine the group of users
associated with a subsite OR dotlrn community consistently with no if {$dotlrn_installed_p} code messing it up. This is really important in places like survey and assessment where we want to know the list of people who can take a survey. Just querying on permissions "works" but grabs in all site wide admins, which is annoying.
We need to figure out how this will affect links such as "login" and "logout" in the master template, which try to go to the register pages under acs-subsite. Otherwise I think this is a good first step to making the dotlrn code simpler and consistent with the rest of the toolkit.
