It seems to me, in any case, the first step is to get django-registration
actively maintained again. James Bennett is welcoming proposals of people
to take over maintenance of the project. Get it working well with custom
user models and with python 3. Once django-registration is a thriving app
as popular as django-south (about 10x as many people using it), it would
make sense to think about the possibility of adding it to contrib.
I think LDAP and oauth (facebook login) support out of the box in django
would be great, though I think it's easier said than done, and
django-registration doesn't even do it out of the box.
As for me personally. I use the admin in every one of the 18 django
websites I maintain, and in the few websites where non-staff users login to
the website, including this line in urls.py goes a long way for me:
url(r'^accounts/', include('django.contrib.auth.urls')),
If email-verification is required, I re-use the password reset code to
handle the tokens.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/f5a95a35-9a56-45af-bbf8-1dba75ef91f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
