Schedule model, API endpoints with permissions
pep8 style: replace mixedCase with lower_and_underscores
static files and homepage using a basic PolymerJS element
enable pagination for Django REST Framework
move Web Components to their own components/ subdir
basic Polymer tabs on the homepage
load Schedule objects from the API in the Polymer front-end

and some setup:
― js libraries
― JS unit tests and a url+view to run them
create, delete and edit schedules using PolymerJS
add canPerformAction(user, action, obj)

Check permissions for normal users, allow superusers to do anything.
Avoids creating permissions for all the corner-cases we want to allow,
e.g. create_vm_without_project_membership.
order schedules by name in the API
add TimeZone model
check Schedule (ON/OFF) against TimeStamp, with tests
configure logging
move all permission checking in 1 place
expose Projects via API, require permissions
add {|Dummy|AWS}Provider models
add {|Dummy|AWS}VMConfig models
ui structure for projects
add User and Profile to the API

Expose only specific fields and allow filtering profiles by project id.
list users in project