Link to code of conduct (#922)

* Link to code of contact

* Update docs/sphinx/source/contributing.rst

Co-Authored-By: Cliff Hansen <cwhanse@sandia.gov>

* remove CoC contact proj-team and shell prompts

* update what's new re: CoC link in contributing

Co-authored-by: Cliff Hansen <cwhanse@sandia.gov>

Author: mikofski

docs/sphinx/source/contributing.rst

@@ -309,22 +309,22 @@ To run the tests locally, install the ``test`` dependencies specified in the
 file. See :ref:`installation` instructions for more information.
 
 pvlib's unit tests can easily be run by executing ``pytest`` on the
-pvlib directory:
+pvlib directory::
 
-``pytest pvlib``
+    pytest pvlib
 
-or, for a single module:
+or, for a single module::
 
-``pytest pvlib/test/test_clearsky.py``
+    pytest pvlib/test/test_clearsky.py
 
-or, for a single test:
+or, for a single test::
 
-``pytest pvlib/test/test_clearsky.py::test_ineichen_nans``
+    pytest pvlib/test/test_clearsky.py::test_ineichen_nans
 
 We suggest using pytest's ``--pdb`` flag to debug test failures rather
-than using ``print`` or ``logging`` calls. For example:
+than using ``print`` or ``logging`` calls. For example::
 
-``pytest pvlib --pdb``
+    pytest pvlib --pdb
 
 will drop you into the
 `pdb debugger <https://docs.python.org/3/library/pdb.html>`_ at the
@@ -333,9 +333,9 @@ code does not use ``print`` or ``logging`` calls, and this also applies
 to the test suite (with rare exceptions).
 
 To include all network-dependent tests, include the ``--remote-data`` flag to
-your ``pytest`` call:
+your ``pytest`` call::
 
-``pytest pvlib --remote-data``
+    pytest pvlib --remote-data
 
 And consider adding ``@pytest.mark.remote_data`` to any network dependent test
 you submit for a PR.
@@ -460,3 +460,8 @@ If this documentation is unclear, help us improve it! Consider looking
 at the `pandas
 documentation <http://pandas.pydata.org/pandas-docs/stable/
 contributing.html>`_ for inspiration.
+
+Code of Conduct
+~~~~~~~~~~~~~~~
+All contributors are expected to adhere to the `Contributor Code of Conduct
+<https://github.com/pvlib/pvlib-python/blob/master/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct>`_.

docs/sphinx/source/whatsnew/v0.7.2.rst

@@ -61,9 +61,10 @@ Testing
 
 Documentation
 ~~~~~~~~~~~~~
-* Add NumFOCUS affiliation to Sphinx documentation (:pull:`862`)
-* Add example of IV curve generation (:pull:`872`)
-* Add section about gallery examples to Contributing guide (:pull:`905`)
+* Add NumFOCUS affiliation to Sphinx documentation. (:pull:`862`)
+* Add example of IV curve generation. (:pull:`872`)
+* Add section about gallery examples to Contributing guide. (:pull:`905`)
+* Add section with link to Code of Conduct in Contributing guide. (:pull:`922`)
 
 Requirements
 ~~~~~~~~~~~~