Assign users to Public group on signup

[lukehollis]

Now on signup, the form is processed and the new user is assigned to a "Public" group that needs to be created in the admin backend by a superuser.

Should address #94 -- I'll add the buttons for managing collections on the frontend in a separate issue after the Collections data model is adjusted.

[rsinghal]

Please rebase this branch against master to remove 6bcd113 from the list of changes

[lukehollis]

@rsinghal I rebased to master--let me know if this is as expected.

[ColeDCrawford]

@lukehollis Rashmi can take a look at this on Monday, but I'm still seeing the same modified files as #149 (0004_lesson_summary.py, models.py, lesson-topic-blurb.html). The changes in 0004_lesson_summary.py and models.py are already in master, but the changes to lesson-topic-blurb look new compared to current master. I thought the rebase was going to fix that but I guess not?

[lukehollis]

Hi @ColeDCrawford thanks for taking a look, and I followed instructions for what I thought was to rebase master -- I'll branch from master continually in future PRs, and for last weekend, I wanted to make sure that the migrations added were numbered correctly between PRs. Do you have a strategy for this that you prefer?

[rsinghal]

@lukehollis unfortunately, this didn't work as there are now more files changed than before. You would need to rebase against artshumrc giza master, not your own. See https://docs.ansible.com/ansible/latest/dev_guide/developing_rebasing.html. Alternatively, you can resubmit the PR with just the changes for this one. Ultimately, I need to only see the files changed by the PR, not from other PRs, so I can review.

[lukehollis]

Hi @rsinghal let me know how this looks--now this PR should only contain the single commit.

[rsinghal]

Yes, this looks right! I'll get this up on dev for the team to test.