Create CODE_OF_CONDUCT.md (readthedocs#562)

* Create CODE_OF_CONDUCT.md

* Point to the RTD code of conduct

* Docs: Add intersphinx

* Docs: add link to our code of conduct

* Add missing sphinx link

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,5 @@
+# Code of Conduct
+
+A copy of our code of conduct can be found on Read the Docs as seen below.
+
+http://docs.readthedocs.io/en/latest/code-of-conduct.html

docs/conf.py

@@ -33,6 +33,7 @@
 # Add any Sphinx extension module names here, as strings. They can be extensions
 # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
 extensions = [
+    'sphinx.ext.intersphinx',
     'sphinx.ext.autodoc',
     'sphinx.ext.mathjax',
     'sphinx.ext.viewcode',
@@ -101,6 +102,8 @@
 # A list of ignored prefixes for module index sorting.
 #modindex_common_prefix = []
 
+intersphinx_mapping = {'rtd': ('https://docs.readthedocs.io/en/latest/', None)}
+
 
 # -- Options for HTML output ---------------------------------------------------
 

docs/contributing.rst

@@ -10,6 +10,11 @@ for changes, rebuild the sphinx demo docs and build a distributable version of t
 The bad news is this means you'll need to set up your environment similar to that
 of a front-end developer (vs. that of a python developer). That means installing node and ruby.
 
+.. seealso::
+
+   If you are unsure of approptiate actions to take while interacting with our
+   communinty please read our :doc:`Code of Conduct <rtd:/code-of-conduct>`.
+
 
 Set up your environment
 =======================
@@ -54,24 +59,27 @@ This default task will do the following **very cool things that make it worth th
 #. Rebuild the sphinx docs anytime it notices a change to ``.rst``, ``.html``, ``.js``
    or ``.css`` files.
 
+.. _bower: http://www.bower.io
+.. _sass: http://www.sass-lang.com
+.. _wyrm: http://www.github.com/snide/wyrm/
+.. _grunt: http://www.gruntjs.com
+.. _node: http://www.nodejs.com
+.. _sphinx: http://www.sphinx-doc.org/en/stable/
+
 
 Releasing the Theme
 ===================
 
 When you release a new version,
 you should do the following:
 
-#. Bump the version in ``sphinx_rtd_theme/__init__.py`` – we try to follow `semver <http://semver.org/>`_, so be careful with breaking changes.
+#. Bump the version in ``sphinx_rtd_theme/__init__.py`` --
+   we try to follow `semver <http://semver.org/>`_, so be careful with breaking changes.
 #. Run a ``grunt build`` to rebuild all the theme assets.
 #. Commit that change.
 #. Tag the release in git: ``git tag $NEW_VERSION``.
 #. Push the tag to GitHub: ``git push --tags origin``.
 #. Upload the package to PyPI: ``python setup.py sdist bdist_wheel upload``.
-#. In the ``readthedocs.org`` repo, edit the ``bower.json`` file to point at the correct version (``sphinx-rtd-theme": "https://github.com/rtfd/sphinx-rtd-theme.git#$NEW_VERSION"``).
+#. In the ``readthedocs.org`` repo, edit the ``bower.json`` file to point at the correct version
+   (``sphinx-rtd-theme": "https://github.com/rtfd/sphinx-rtd-theme.git#$NEW_VERSION"``).
 #. In the ``readthedocs.org`` repo, run ``gulp build`` to update the distributed theme files.
-
-.. _bower: http://www.bower.io
-.. _sass: http://www.sass-lang.com
-.. _wyrm: http://www.github.com/snide/wyrm/
-.. _grunt: http://www.gruntjs.com
-.. _node: http://www.nodejs.com