Updated the CONTRIBUTING file to include a code of conduct section (d…

…uosecurity#154)

CODEOFCONDUCT.md

@@ -0,0 +1,15 @@
+# Duo Unix Code of Conduct
+By participating in Duo’s Github you agree to abide by the following guidelines regarding standards of conduct and information security within the community.  All     guidelines are subject to moderator interpretation and any violations will be evaluated on a case-by-case basis, at Duo’s sole discretion.
+
+1. You will not post any information that compromises the security of any third party or third party data, including Duo customers or customer employees. This includes physical addresses, real names, phone numbers, and Duo account information. The Duo team reserves the right to determine whether a post, image, or any other media compromises the security of any third party or third party data.
+2. You will not solicit other users for their personal or corporate information, including contact information. We’re okay with you privately sharing this information with other users if you and your organization are comfortable with it.
+3. You will not post links to sites that illegitimately prompt users to enter their login credentials for any service.
+4. You will not post spam of any kind including text, images, and links.
+5. You agree to communicate with other users and Duo moderators in a mature and respectful manner.
+6. You will not post any content that Duo moderators deem inappropriate. This includes pornographic content and racist, sexist, or otherwise bigoted content. If you are unsure whether an image or statement is inappropriate, you probably shouldn’t post it.
+7. You agree not to “bump” any discussion threads more than once a day. “Bumping” is replying to a thread in order to raise its position higher on the board but without answering the question or adding to the conversation. For example posting a message such as “Does anyone have an answer to this?” without additional context could be considered bumping.
+8. You agree to refrain from using profanity when interacting with users and moderators.
+9. You agree to not discuss any topics that do not relate to Duo Unix or general digital security topics.
+10. You agree to use punctuation and proper sentence structure when writing posts.
+If you have questions about any of these guidelines, please send an email to support@duosecurity.com. 
+

CONTRIBUTING.md

@@ -3,7 +3,6 @@ Thanks for your interest in contributing to Duo Unix!
 
 We welcome pull requests as well issues you may have.
 
-
 ## Opening Issues
 Before opening an issue on the Github project see if your issue falls into the following categories. If it does please direct your issue to those locations instead.
 

README.md

@@ -130,7 +130,7 @@ For production deployments Duo recommends using our stable release tarballs or p
 
 ## Contributing
 
-Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+Please read [CODEOFCONDUCT.md](CODEOFCONDUCT.md) and [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct and the process for submitting pull requests to us.
 
 ## Versioning