I just noticed that all of the user stuff was added to the CAPRA site, 
not the more generic GeoNode site.  Eventually (maybe even by 1.0) I 
would like to see the CAPRA site split off from the main source tree, 
and geonode.settings serving as the geonode prototype that shows up for 
folks developing on the core.  To that end, we've been trying to keep 
everything in capra/ as strictly opt-out (which is why there is a 
geonode.settings in the first place.)

Is there a reason we shouldn't move the user profiles and related stuff 
into a geonode/... module?

--
David Winslow
OpenGeo - http://opengeo.org/

Reply via email to