Switch out django-openid for django-socialauth
The account app and django-openid is not the best approach. Django-socialauth provides many more options and looks much cleaner. http://uswaretech.com/blog/2009/08/django-socialauth-login-via-twitter-facebook-openid-yahoo-google/
Keep in mind that we have to have all the information to create a valid Researcher profile before we can create the user. We don't want user's without names running around the site.
I talked to brosner and he said a better approach is to keep django-openid and add django-oauth-access.
I agree and I've started to implement this. Still needs a lot of work.
This needs to be done at some point, but for now I am removing OpenID and OAuth from the login/registration templates. I'd rather have a solid simple signup for the launch than poorly tested extra stuff.
I wouldn't mind helping out here.