During my efforts of going through the big backlog of issues on django-user-accounts, I came across this issue:
https://github.com/pinax/django-user-accounts/pull/98 It looks to add support for inviting users through SignupCode which we already support. The issue cities the old admin_invite_user view included with Pinax. I am trying to understand the split between kaleo and doing something in d-u-a. The original view we shipped with Pinax only allowed users with staff access to send invitations. However, I am sure there are a ton of different business-level requirements a user might want to implement. Do I include something or defer this through documentation? I think if we did something it would involve using a permission that would allow the site developer to control the logic of who can or cannot invite users with a SignupCode. Thoughts? -- Brian Rosner http://twitter.com/brosner -- You received this message because you are subscribed to the Google Groups "Pinax Core Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pinax-core-dev. For more options, visit https://groups.google.com/groups/opt_out.
