User model specs

[javorszky]

Right, so here's the idea:

• first user ever is admin, auto-login
• subsequent users be not auto-logged in, but somehow be flagged in the admin area that they've requested access, and had to be approved? (discuss)
• there should be check for duplicate email addresses and usernames
• fixtures updated with username: john@onolan.org, pass: Wh0YouG0nnaCall?
• email address validation

Questions

• When should we send an email?
  • password reset
  • verification
  • approval
• setting to allow signup for anyone with a specific role (how's that ACL coming along?)?
  • would this be a white-list kind of thing
  • a simple dropdown with [no, reader, contributor, editor, user, admin]
  • a checkbox and a dropdown... ? )

Anything else I missed, let me know, otherwise I'm working on stuff that I think are core at this stage, which are:

[ErisDS]

A couple of super quick things:

• registration very much relies on / is connected to ACL - Jacob has taken that on and I'm working on specing out some of the perms / roles etc - see ACL
• for standalone installs,first-user (admin) registration needs to happen as part of the install process
• pretty much everything else you've said is spot on

[javorszky]

Because the duplicate email address validation is broken. Yay...