Add contribution guidelines, issue templates, and pull request templates.

Author: thomashoneyman

.github/contributing.md

@@ -0,0 +1,51 @@
+# Contribution
+
+Thank you for contributing to `purescript-parsing`!
+
+Following these guidelines helps ensure we're able to carefully consider your contribution and help you finalize your pull request. Your time (like ours) is valuable, and we try to at least provide constructive feedback on every contribution.
+
+### Contributions we love
+`purescript-parsing` is an open-source library and we love to receive contributions. There are many ways you can contribute:
+
+* Help expand our test coverage
+* Help fix open issues, even if that simply means adding a helpful comment
+* Help push along open pull requests that need more work to be complete
+* Improve or add new usage examples to better demonstrate how to use the library in real-world scenarios
+* Update documentation and tutorials to be easier to understand, more comprehensive, and above all -- up to date!
+
+### Contributions we should discuss
+Some contributions will take some discussion before we accept an update to the project. If your contribution includes one of the below examples (or seems to be reasonably similar), please consider reaching out to us before putting in a lot of work to build the feature. We're active on the [PureScript user forum](https://purescript-users.ml) and the [functional programming Slack](https://functionalprogramming.slack.com/) community (new? [use this link to join](https://fpchat-invite.herokuapp.com/)!). For feature requests, feel free to open an issue with a tag.
+
+* New features and functions that will change the library's public API
+* New tutorials (while we love seeing new tutorials, we won't always be able to feature them in the readme)
+
+# Ground Rules
+
+We have a small set of quality-of-life guidelines for contributing to `purescript-parsing`. These include:
+
+* All pull requests must pass continuous integration.
+* If you are adding new functionality, you should provide tests and documentation for your code. If you're fixing an existing bug, please provide a failing test case your patch solves.
+* If possible, please avoid requiring new dependencies.
+
+### Filing issues
+If you have a general question about the project, it's best to ask on the [PureScript user forum](https://purescript-users.ml) or the [functional programming Slack](https://functionalprogramming.slack.com/) than to open a new issue. If you have run into a bug in the project, then please do open an issue! When you do, we ask that you follow a few steps which are outlined in our issues template. The gist of it is here:
+
+* Verify the problem is indeed with `purescript-parsing` (not with Pulp, Bower, or PureScript);
+* Record what versions you are using for PureScript and `purescript-parsing`
+* Describe the issue with steps to reproduce (as much as you are able). A minimal reproducible example is the absolute best case scenario.
+
+We promise to address the issue as soon as we can.
+
+### Suggesting features or enhancements
+We love to hear about ways we could make  better. If you're wishing for a feature that doesn't exist in `purescript-parsing`, you're probably not alone; there are bound to be others with similar needs. Please feel free to open an issue on GitHub that describes:
+
+* the feature you would like to see
+* why you need it
+* how it should work
+
+We promise to review your issue, but we aren't always able to accommodate all requests. It helps if you're able to contribute to the implementation, too!
+
+### Code reviews
+The core team looks at pull requests weekly, at which point we will review your code, ensure it meets our ground rules and fits with the philosophy of the project, and -- if necessary -- provide constructive feedback. As soon as at least one member of the team has signed off on your pull request, we will merge your contribution.
+
+If you opened a pull request and we need to ask a few questions, we expect responses within a month. After that we may close the pull request if it isn't showing any activity to keep things manageable.

.github/issue_template.md

@@ -0,0 +1,22 @@
+## Pre-check
+
+* For help and support, try the [PureScript user forum](https://purescript-users.ml) or the [functional programming Slack](https://functionalprogramming.slack.com) before opening an issue in the repository.
+* For bug reports, do a quick search to ensure the bug has not yet been reported.
+* For new feature requests, please remember to describe the feature you would like to see, why you need it, and how it might be implemented.
+* Finally -- be nice and have fun!
+
+---
+
+## Environment
+
+* PureScript **[version]**
+* Pulp **[version]**
+* `purescript-parsing` **[version]**
+
+## Current behavior
+
+Please include code samples, errors, steps to reproduce, and compiler output if appropriate.
+
+If possible, provide a sample minimal app or test case that reproduces the error. For visual bugs that are difficult to demonstrate in text, consider including a .gif using an app like [Recordit](http://www.recordit.co/).
+
+## Expected behavior

.github/pull_request_template.md

@@ -0,0 +1,15 @@
+## What does this pull request do?
+
+Please describe the purpose of the pull request, including any background context and links to related issues. If this introduces a large change to the project, please describe what you have implemented.
+
+## Where should the reviewer start?
+
+Help save the reviewer time by highlighting the most important sections of code.
+
+## How should this be manually tested?
+
+If this is a new feature, you should provide new test coverage. If it fixes an existing bug, you should provide a failing test case this change fixes. Other than automated testing, what manual tests can the reviewer perform to verify your work?
+
+## Other Notes:
+
+Does the project documentation need to be updated? Should we introduce a new example, or update any existing examples? Does this PR require any other follow-up tasks?

.gitignore

@@ -1,9 +1,9 @@
 /.*
 !/.gitignore
+!/.github
 !/.jscsrc
 !/.jshintrc
 !/.travis.yml
 /bower_components/
 /node_modules/
 /output/
-package-lock.json

README.md

@@ -1,7 +1,10 @@
 # purescript-parsing
 
-[![Latest release](http://img.shields.io/github/release/purescript-contrib/purescript-parsing.svg)](https://github.com/purescript/purescript-parsing/releases)
+[![Latest release](http://img.shields.io/github/release/purescript-contrib/purescript-parsing.svg)](https://github.com/purescript-contrib/purescript-parsing/releases)
 [![Build status](https://travis-ci.org/purescript-contrib/purescript-parsing.svg?branch=master)](https://travis-ci.org/purescript-contrib/purescript-parsing)
+[![Pursuit](http://pursuit.purescript.org/packages/purescript-parsing/badge)](http://pursuit.purescript.org/packages/purescript-parsing/)
+[![Maintainer: garyb](https://img.shields.io/badge/maintainer-garyb-lightgrey.svg)](http://github.com/garyb)
+[![Maintainer: thomashoneyman](https://img.shields.io/badge/maintainer-thomashoneyman-lightgrey.svg)](http://github.com/thomashoneyman)
 
 A parser combinator library based on Haskell's Parsec.
 
@@ -15,3 +18,7 @@ bower install purescript-parsing
 
 - [See the tests](test/Main.purs) for some example usages.
 - Module documentation is [published on Pursuit](http://pursuit.purescript.org/packages/purescript-parsing).
+
+## Contributing
+
+Read the [contribution guidelines](https://github.com/purescript-contrib/purescript-parsing/blob/master/.github/contributing.md) to get started and see helpful related resources.