-
Notifications
You must be signed in to change notification settings - Fork 5
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
Sign Up & Login policy #13
Comments
@shaib mentioned that we can add login possibility later (sending them tokens if we want to avoid requiring the signup), after CFP is loaded, so speakers can edit their abstracts etc. |
We might want to allow logins for things like marking presentations to attend etc |
update: for now, login hidden. We might readd in the future if required |
@AmitAronovitch Those are already fixed by the style redisgn I did. |
@AmitAronovitch Wasn't this resolved some way? Haven't speakers been given logins? |
Now that we have some users, maybe we should re-enable login button? |
I think we should disable the sign-up in production. Maybe even the login button - have them available only on "staging server".
If we keep using ti.to, registration would come through there, and I think also the sponsors would be simpler to handle by us via admin interface (I want to just remove the sponsors stuff from the menu).
The benefit of disabling login & signup is that we will not have to worry about the stability, usability & translation of the Dashboard (only we will see it), and as byproduct reduce risks of spam & security. As an example: confirmation emails are not being sent on signup now (would be nice if we would not have to worry about that).
Anyways, state your opinions. Once we decide - fix accordingly.
The text was updated successfully, but these errors were encountered: