You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently the current inscription process discourages most of people to use paiji (as can be seen in the poll results : 50 votes max). It would be a good idea to automaticaly create account for everyone in the residence, and then just send the verification email for them to click. We can then provide a way to change the user id.
The text was updated successfully, but these errors were encountered:
Yes, I must admit, as the newcomer, that I found the experience of
subscribing very discomforting. Having to send a mail to the rézo, then
waiting, and the process was, as far as I thought back then, too
complicated for a subscription.
Now, let me learn Django :)
Apparently the current inscription process discourages most of people to
use paiji (as can be seen in the poll results : 50 votes max). It would be
a good idea to automaticaly create account for everyone in the residence,
and then just send the verification email for them to click. We can then
provide a way to change the user id.
—
Reply to this email directly or view it on GitHub #45.
Well... the best solution is to start integrating rezo.rez into paiji.rez as the code of rezo.rez is unmaintainable. That will solve a lot of problems and frankly it shouldn't be that much work to rewrite the interface.
Also the authentication and permission by group is already there in django. So why don't we start to build rezo.rez in django and make that our goal for rezo 2015?
The ultimate goal is to have one single account across all rezo services.
Apparently the current inscription process discourages most of people to use paiji (as can be seen in the poll results : 50 votes max). It would be a good idea to automaticaly create account for everyone in the residence, and then just send the verification email for them to click. We can then provide a way to change the user id.
The text was updated successfully, but these errors were encountered: