Reenable development based database initializer strategy
Add open and closed tags to db seed
Add roles to db seed
Update todo with priority features

Reflects info from meeting.
Update Contact page
Improve ticket Comments styling
Removed About page
Update Project details layout
Update layout of Ticket details page
Hide edit link on Ticket details page when appropriate

Before, the edit link would show even when you didn't actually have
sufficient permissions to edit the ticket. This lead to a 403 forbidden
page.
Remove edit/delete links to tickets on Project Details page
Remove collection setters from Models

When EF overrides the methods for database classes, it replaces these
setters with a runtime exception. It's not legal to set the collections
so the class should reflect that.
Add View models for project authorizations
Create Edit Permissions page

It's currently not linked to, but it's implemented and working. The plan
is to either add it to the Project details page or have a dedicated page
for listing users associated with a project and putting a link there.
Allow admin user to edit own permissions

Originally, this was disallowed since it seemed potentially error prone
from the perspective that a user might accidentally remove his own admin
permission, but it would make sense that it should be allowed.

Plus admins should be able to add submitter permissions to themselves,
for instance.
Add UserList to Projects
Add links to user list and edit permissions to layout
Show owner on UserList
Show owner when editing permissions on projects
Fix Forbidden when removing project permissions from self

When a user removed all project permissions from himself, he would no
longer be allowed to access the project, but the redirect would
indiscriminately redirect the user back to the project details. This
would cause a forbidden page to be displayed.