Adding contribution guidelines

Author: Carlos Atencio

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+# Contributing to protractor-http-mock
+This project has come a long way thanks to the community, and its growth has been very much a result from countless suggestions and pull requests. Thank you all!
+
+## Pull Requests
+I strongly encourage developers to submit pull requests for new features and bug fixes. Please add unit tests and/or an examples to any pull request submitted. This goes a long way in getting the pull request merged in as soon as possible.
+
+This project is developed using grunt. To run all tests, simply execute
+
+`npm install`
+`node_modules/.bin/webdriver-manager update`
+`grunt verify`
+
+* To add a unit test, please refer to tests/httpMock.test.js
+* To add an example, please refer to the example/ folder.

README.md

@@ -212,16 +212,3 @@ To run these tests locally, please follow these steps from the root directory:
 1. `npm install`
 2. `node_modules/.bin/webdriver-manager update`
 3. `npm run example`
-
-
-### Contributions and recognition
-
-* `jdgblinq` for their contribution to query string matching.
-* `ReactiveRaven` for adding convenience methods key for getting this to work with ngResource.
-* `nielssj` for the `requestsMade` functionality and for pointing out a few bugs.
-* `nadersoliman` for their input and pull request on allowing the user to set custom name for the protractor configuration file.
-* `kharnt0x` for submitting a bug fix for proper callback handling.
-* `zigzackattack` for their contribution on post data matching.
-* `matthewjh` for their pull request to allow the plugin to play nice with interceptors.
-* `stevehenry13` for their pull request to allow the plugin to work with transforms.
-* `brandonroberts` for the fantastic work on interceptors and promises.