-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement "social signup", e.g., "log in with Google or LinkedIn or GitHub or Facebook or …" #13
Comments
Spoiler: I'd pick LinkedIn, GitHub, and one or two "social" networks, e.g., Twitter plus either Facebook or Instagram. The goal here is to accommodate third party logins for early adopters and potential survey takers. There is overhead associated with setting up each provider so limiting it to the 3, 4, or 5 networks that would cover that audience is paramount. Account creation with email and password is supported and use of third-party authentication is optional but convenient and preferred for some people. |
@erictheise your suggestion to look at the most popular social media providers that people have included so far in their profiles/survey sounded good to me - can we pull that info out of the database? |
I did do it when I started working on this issue. We're missing dozens of recently surveyed organizations and the survey does not collect individual social accounts. Short on time but
So Twitter's a good choice. Can refine when Angela and company add additional survey results and it'd be great, @dayotte, if you and @cherylhjli could casually collect individual preferences during crits you run. It's also not perfect as Google no longer has and never did have a wildly popular social network but many (most?) people have Google accounts for email and sharing documents. |
Creating an account the old fashioned way – with email address and password – is being dealt with in issue #2. We'll track signing up with another trusted account here. Now that
django-registration
is implemented the use of django-allauth is supposed to be straightforward.The text was updated successfully, but these errors were encountered: