Moved code of conduct into ruby-grape.io.

Author: dblock

code_of_conduct/index.md

@@ -0,0 +1,28 @@
+---
+layout: page
+title: Code of Conduct
+tags: [code of conduct]
+comments: false
+---
+### Code of Conduct
+
+As contributors and maintainers of Ruby Grape and community projects, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
+
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.2.0, available at [http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)

index.md

@@ -15,11 +15,8 @@ Working projects using Grape.
 [Users](/users)
 Who uses Grape?
 
-[History and Team](/team)
-Who maintains Grape?
-
-[Want to help?](https://github.com/ruby-grape/ruby-grape.github.io/issues)
-A number of non-code, community-related work-items you can help with.
+[History, Team and Contributing](/team)
+Who maintains Grape? How can I contribute?
 
 [Need help?](https://groups.google.com/forum/#!forum/ruby-grape)
 Please join and use the ruby-grape Google group for all questions.

team/index.md

@@ -43,6 +43,8 @@ Grape was created by [Michael Bleigh](https://github.com/mbleigh) at [Intridea](
 
 We welcome all contributors to the Grape ecosystem, built upon rough consensus and running code, a principle described in the [Tao of IETF](https://www.ietf.org/tao.html). We are highly inclusive, try to be nice and helpful to both experienced and new developers. We encourage you to participate and to be pragmatic. To quote David Clark, _"We reject kings, presidents and voting"_, and Jon Postel, _"Be conservative in what you send and liberal in what you accept."_
 
+We also have a [contributor code of conduct](/code_of_conduct).
+
 ### Becoming a Project Maintainer
 
 Team members from organizational maintainers down to individual project nominate individuals who have significantly contributed to the project to join the team. We recommend requiring a simple majority and no significant objections (also known as rough consensus) as a sufficient criteria for acceptance. A great first step in becoming a maintainer of any project could be making a release.