Registration

[Mischback]

• [ ] create Class Based View for creating new accounts
  • [ ] how much of Django's built-in views can be re-used?
  • [x] Django's built-in views were introduced as CBV in Django 1.11. Up to 1.10 they are FBV. Should we seperate them logically? Or drop 1.10 support?
• [x] create a corresponding form
• [x] automatically activate if MINIUSER_DEFAULT_ACTIVE = True
• [x] provide some mean of manual activation
  • [x] no notification of staff members
  • [x] with (email) notification of staff members
  • ~OPTIONAL: on-site notification of staff members~ moved to #14
• [ ] handle MINIUSER_REQUIRE_VALID_EMAIL
  • [x] send verification email
• [ ] add specific actions to Django's admin to
  • [x] activate / deactivate a user
  • [ ] re-send the verification email

[Mischback]

add specific actions to Django's admin

• https://medium.com/@hakibenita/how-to-add-custom-action-buttons-to-django-admin-8d266f5b0d41

• method in MiniUser-model?

[Mischback]

sending email with Django

A SMTP server is needed... How to best implement this or at least, provide sane defaults for the configuration? During development/testing, an offline backend is sufficient, but how about testing this on Travis?

• https://docs.djangoproject.com/en/2.0/topics/email/

• https://stackoverflow.com/questions/6367014/how-to-send-email-via-django

• https://simpleisbetterthancomplex.com/tutorial/2016/06/13/how-to-send-email.html

• https://www.mailgun.com/

• https://simpleisbetterthancomplex.com/tutorial/2017/05/27/how-to-configure-mailgun-to-send-emails-in-a-django-app.html

[Mischback]

See #9: Support for Django < 1.11 will be dropped. If that can be done in this feature-branch: Do it!

• do not forget to adjust tox.ini