Add structure for coc

Author: meatballs

docs/community/coc.rst

@@ -0,0 +1,74 @@
+.. _coc:
+
+Code of Conduct
+===============
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

docs/community/communication.rst

@@ -0,0 +1,16 @@
+.. _communication:
+
+Communication
+-------------
+
+There are various ways of communicating with the team:
+
+- `Gitter: a web based chat client, you can talk directly to the users and
+  maintainers of the library. <https://gitter.im/Axelrod-Python/Axelrod>`_
+- Irc: we have an irc channel. It's #axelrod-python on freenode.
+- `Email forum. <https://groups.google.com/forum/#!forum/axelrod-python>`_
+- `Issues: you are also very welcome to open an issue on
+  github <https://github.com/Axelrod-Python/Axelrod/issues>`_
+- `Twitter. <https://twitter.com/AxelrodPython>`_ This account periodically
+  tweets out random match and tournament results; you're welcome to get in
+  touch through twitter as well.

docs/community/index.rst

@@ -0,0 +1,13 @@
+.. _community:
+
+Community
+=========
+
+Contents:
+
+.. toctree::
+   :maxdepth: 2
+
+   team.rst
+   communication.rst
+   coc.rst

docs/community.rst renamed to docs/community/team.rst

@@ -1,7 +1,4 @@
-.. _community:
-
-Community
-=========
+.. _team:
 
 Part of the team
 ----------------
@@ -26,18 +23,3 @@ positive experience.
 **If you are using the library for your own work** and there's anything in the
 documentation that is unclear: we want to know so that we can fix it. We also
 want to help so please don't hesitate to get in touch.
-
-Communication
--------------
-
-There are various ways of communicating with the team:
-
-- `Gitter: a web based chat client, you can talk directly to the users and
-  maintainers of the library. <https://gitter.im/Axelrod-Python/Axelrod>`_
-- Irc: we have an irc channel. It's #axelrod-python on freenode.
-- `Email forum. <https://groups.google.com/forum/#!forum/axelrod-python>`_
-- `Issues: you are also very welcome to open an issue on
-  github <https://github.com/Axelrod-Python/Axelrod/issues>`_
-- `Twitter. <https://twitter.com/AxelrodPython>`_ This account periodically
-  tweets out random match and tournament results; you're welcome to get in
-  touch through twitter as well.

docs/index.rst

@@ -95,7 +95,7 @@ Table of Contents
 
    tutorials/index.rst
    reference/index.rst
-   community.rst
+   community/index.rst
    citing_the_library.rst