We will want to flesh out the specifics of each Mixin, and associated UI models, as we complete each associated UI story.

WIP: UI Architecture for Module UI Components

Conflicts:
	apps/openassessment/peer/api.py
	apps/openassessment/xblock/openassessmentblock.py
	apps/openassessment/xblock/static/html/oa_rubric.html
	apps/openassessment/xblock/static/js/src/oa_submission.js

Sass/Styling Architecture

* import order - with base blocks, theming, and specific app layers
* base utilities/tools
* notes/starters for each Sass partial imported

TIM-127

HTML Templates: Update Term References & Problem Results UI

TIM-125: Pull request fixups

* Fixes to method names requested on the PR

TIM-125: Students completing scoring see results

* When a score becomes available for a student (i.e., when they have
  completed the minimum number of peer assessments and have received
  enough assessments to their submission), it is shown to the student.
* XXX: As an interim fix to not having thought through all the cases
  around multiple existing submissions, this commit disallows making
  multiple submissions.
* Refactoring of XBlock view to devolve functionality into smaller
  pieces - this is interim work until there's a better workflow layer
  (or perhaps it can be the prep for that.)
* TODO: since overgrading should be baked in, we should still show them
  their assessment page.

Conflicts:
	apps/openassessment/xblock/openassessmentblock.py

xblock lms integration for TIM

Conflicts:
	apps/openassessment/xblock/openassessmentblock.py
	apps/openassessment/xblock/static/html/t-base.html

Basic/Static Application HTML

* basic app skeleton HTML
* response HTML
* peer evaluations
* self evaluation
* grade status
* UI messages

Conflicts:
	apps/openassessment/xblock/openassessmentblock.py

TIM-126: Peer criteria support explanations

* Rubric criteria options now support an optional <explain>
  child, which is used as explanatory text for that particular
  criterion option, e.g.:
  5 - Very Well (indicates intelligent use of persuasive
                 argument to, etc etc.)
* Sample explanations added to the Poverty sample rubric to
  show them in use.
* parse_xml now calls external rubric parser to make testing easier
* basic unit tests for xml parsing confirm things seem to work
* max available points calculated at rubric ingestion time now

* basic app skeleton HTML
* response HTML
* peer evaluations
* self evaluation
* grade status
* UI messages

Sanchez/xblock peer eval