Create data migrations for static models

[adehnert]

At the moment, when you create a new deployment, you need to remember to create various static models. South should be poked to do this automatically.

This includes:

• OfficerRole?
• System users, groups, and associated permissions
  • The system:groupadmin group and groupadmin@SYSTEM user
  • mit, autocreated groups
  • asa-ebm, mit-deskworker, mit-offices
• ActivityCategory? (though at least there's a script for this already; see #30)

There's probably some other stuff that I'm forgetting just now.

[adehnert]

Fixtures may be more appropriate for OfficerRole? and ActivityCategory?.

(I think users, groups, and permissions do want a data migration, to handle foreign keys.)

[adehnert]

OfficerRole? wants a migration, because it needs to reference the User table.

As of:

commit 29a7eca255c5e4b3d305ed908248bad9d5f95d4a
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Thu Nov 17 17:00:21 2011 -0500

    Create auth groups (Trac: #29)

the system users, groups, and associated permissions are all done, I think.

[adehnert]

Blergh. OfficerRole? has a foreign key as well (grant user).

[adehnert]

Fixed:

commit 4d6fe00e42dc36ad4b49911930b52dd84c0d9cbf
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Mon Dec 12 01:33:44 2011 -0500

    Create standard OfficerRoles (Trac: #29)

commit c060d8c4dbc5a3602684ddc8a5d743bb3cd604cc
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Mon Dec 12 00:23:27 2011 -0500

    Use fixtures for categories, and track changes
    
    * Remove the old import_categories.py script, and associated
      legacy-categories.txt file
    * Add fixtures for:
        * Creating the groups.ActivityCategory objects (formerly the role of the
          import_categories.py script, see above)
        * Creating the forms.FYSMCategory objects (formerly done by hand)
    * Diff those fixtures in the diff_static_data.sh script
    
    This partially fixes Trac #29 and fixes Trac #30.