TW
userprofiles implemented by cs aa425c34026b14eb4988430580e0de484477e941
translatable messages: ae61712fbcf73effae682ced27c21332ab042ea9 and 58aae90b0ae6bf4d4d874b197974ac94b4890cfe
todo: unify/move translatable strings to some common location (at least for management commands), update .po files / transifex.
wanted to use templates, blocked by: https://code.djangoproject.com/ticket/24111 bug already closed as wontfix and the option i tried to use will go away again in django again. in django 1.8 there...
keep this on hold until we have a minimum requirement of django 1.8, so we can use its email templating.
note: before any local 2factor auth is implemented, you could already use the 2factor auth of some social auth (like google auth with 2FA) that we already offer.
Looks nice. :)
maybe. for each extension we add, we always have to consider how well it is maintained (now and in future), because as we have already seen with "registration", things get...
https://stackoverflow.com/questions/47620487/django-2-0-sqlite-integrityerror-foreign-key-constraint-failed or that? `Host.get_by_fqdn()` maybe?
Not sure I want that because I can't maintain it (I don't use docker). @elnappo what do you think?