Fixed problem with SPInfo and SPPrivacy URLS. Also changed name of /events/ view to 'home-events' so the 'home' view will point to the one that is actually public.

Added public url patterns in ligoauth/middlware/auth.py. Note: This is a temporary hack to facilitate registration with InCommon.

Removed 'Alpha' from the GraceDB homepage. Also added service provider privacy and info pages, which are required for federation with InCommon.

Removed SimpleSearchFormWithSubclasses. The only thing that needed this was the gstlalcbc report page, and there is a simple workaround instead: just get a list of Event objects, and upcast them to CoincInspiralEvents. One wrinkle is that the matplotlib call 'fill_between' (which had given us that nice grey region on either side of the expected IFAR line) seems to hang now. I emailed Chad and commented this out.

Fixed bug due to Django 1.6 update. The get_or_create call in refresh_users_from_ldap.py needed some default arguments. Otherwise, it tries to create a user with an empty username, and that will collide with another user with an empty filename and cause an unhandled exception.

Removed settings/update.py and modified branson.py to reflect updates. No changes required for settings/default.py

Fixed URL sent out in event creation LVAlert to a valid URL, namely the URL of the event file in the web interface.

Added Bayestar MIC robot DN and user. This is a temporary robot for ER5. Should probably be removed when Leo doesn't need it anymore.

Changed performance log to a simple rather than rotating file. The file needs to be cleaned up rather than rotated, or the 3-day lookback property breaks.

Changed admin and admin email to Branson (e.g., myself), so that I can get emails when the live box throws a 500.

Added a log file and view for the ER5 performance metric. The PerformanceMiddleware response handler checks whether the user tried to create an event or annotation, and records the status code of the response. The view 'performance' displays stats for performance over the last three days. NB: This solution is fragile for several different reasons. But the most egregious is that permissions on the log file cause conflicts with django management commands. This will need to be addressed in the future.