Merge pull request #60 from AuthorizeNet/pr-merger

Adding Contributing.md and changes in README.md

Author: gnongsie

CONTRIBUTING.md

@@ -0,0 +1,7 @@
++ Thanks for contributing to the Authorize.Net Node SDK.
+
++ Before you submit a pull request, we ask that you consider the following:
+
+     - Submit an issue to state the problem your pull request solves or the funtionality that it adds. We can then advise on the feasability of the pull request, and let you know if there are other possible solutions.
+     - Part of the SDK is auto-generated based on the XML schema. Due to this auto-generation, we cannot merge contributions for request or response classes. You are welcome to open an issue to report problems or suggest improvements. Auto-generated classes are inside [sdk-node/lib/apicontracts.js](https://github.com/AuthorizeNet/sdk-node/tree/master/lib) and [sdk-node/lib/apicontrollers.js](https://github.com/AuthorizeNet/sdk-node/tree/master/lib) folders, except [sdk-node/lib/apicontrollersbase.js](https://github.com/AuthorizeNet/sdk-node/tree/master/lib).
+    

README.md

@@ -8,6 +8,10 @@
 * Node.js version 4.8.4 or higher
 * An Authorize.Net account (see _Registration & Configuration_ section below)
 
+### Contribution  
+  - If you need information or clarification about any Authorize.Net features, please create an issue for it. Also you can search in the [Authorize.Net developer community](https://community.developer.authorize.net/).
+  - Before creating pull requests, please read [the contributors guide](CONTRIBUTING.md).
+
 ### TLS 1.2
 The Authorize.Net APIs only support connections using the TLS 1.2 security protocol. It's important to make sure you have new enough versions of all required components to support TLS 1.2. Additionally, it's very important to keep these components up to date going forward to mitigate the risk of any security flaws that may be discovered in your system or any libraries it uses.