librelist archives

users in capra site?

users in capra site? by David Winslow
- Re: [geonode] users in capra site? by Ariel Nunez
  - Re: [geonode] users in capra site? by David Winslow

users in capra site?

From:: David Winslow
Date:: 2010-07-01 @ 19:23

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/

Re: [geonode] users in capra site?

From:: Ariel Nunez
Date:: 2010-07-01 @ 19:39

David,

The main reason I put the profiles app in capra/settings.py in the
first place is because settings like these:

    AUTH_PROFILE_MODULE = 'capra.profiles.Profile'
    REGISTRATION_OPEN = False

are very site specific, i.e. different sites need different profile
models and some might be open to the public or not.

However, the reasons I just mentioned above, do not conflict with
putting the app in the geonode folder instead of the capra one.

If it's ok with you I will take care of this refactoring after my
metadata branch gets merged back to master.

Ariel.

Re: [geonode] users in capra site?

From:: David Winslow
Date:: 2010-07-01 @ 19:55

On 07/01/2010 03:39 PM, Ariel Nunez wrote:
> David,
>
> The main reason I put the profiles app in capra/settings.py in the
> first place is because settings like these:
>
>      AUTH_PROFILE_MODULE = 'capra.profiles.Profile'
>      REGISTRATION_OPEN = False
>
> are very site specific, i.e. different sites need different profile
> models and some might be open to the public or not.
>
> However, the reasons I just mentioned above, do not conflict with
> putting the app in the geonode folder instead of the capra one.
>
> If it's ok with you I will take care of this refactoring after my
> metadata branch gets merged back to master.
>
> Ariel.
>    
Currently the user profile is very closely tied to the metadata document 
format, which is fairly deeply "baked in" to GeoNetwork and the layer 
handling in GeoNode maps module.  I don't think it makes a lot of sense 
to have the user profile in a capra module when it is used so intimately 
for the layer form and such.

Not in a big hurry on this (I don't really know when we'll be pulling 
the capra stuff out) but, until/unless we have the actual metadata 
format decoupled from the layer and map management stuff, I don't think 
this is actually as site-specific as you might suspect.

It's also pretty easy to figure out a conservative default for these 
settings, so I don't see any harm in setting them so that the "basic" 
site actually runs.

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