Purpose or Intent
-----------------
> Describe the rationale and use case for this pull request.  Provide any background, examples, and images that provide further information to accurately describe what it is that you are adding to the repo.  Add subsections as necessary to organize and feel free to link and reference other PRs as necessary, but also include them in the links section below as a quick reference.
> 
> Guidelines:
>   * Keep Pull Request titles short and to the point, ideally under 72 characters
>   * Provide as much context/info in the description as necessary to get the reviewer up to the same domain knowledge level as yourself
>   * Keep code changes as short and implementing a single feature/bug fix/refactoring when possible


Links
-----
> * http://documentation.for/library/that/I/am/adding
> * [PR relevant issue or pull_request](#123)


Steps for Testing/QA
--------------------
> [Optional] If there are any manual steps that you would like the reviewer(s) to take to verify your changes, please describe in detail the steps to reproduce the features added by the pull request, or the bug before and after the change.

Add github pull request template
Add github pull request template

This adds a standard way of formatting a pull-request and guiding a contributer
to the prefered format and level of detail for a pull request.  This feature
was recently added to the github web UI:

https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/

And is in the process of being supported in `hub`, the official command line
git augmentation tool for github:

https://github.com/github/hub/pull/1187

The idea is this is a suggestion, not an enforcement.  Everything in the quotes
is meant to be a short documentation of guidelines for the commiter to use when
opening a pull-request, and should be deleted and filled out with pull-request
context specific information.  None of the pull-request template is enforced by
github and can be deleted if the commiter so chooses.
