DOC: adapt the text of the code of conduct

SciPy->PyWavelets
Add committee members
Remove mention of NumFOCUS

Author: grlee77

doc/source/dev/conduct/code_of_conduct.rst

@@ -1,26 +1,31 @@
-SciPy Code of Conduct
-=====================
+PyWavelets Code of Conduct
+==========================
 
 
 Introduction
 ------------
 
-This code of conduct applies to all spaces managed by the SciPy project,
+This code of conduct applies to all spaces managed by the PyWavelets project,
 including all public and private mailing lists, issue trackers, wikis, blogs,
-Twitter, and any other communication channel used by our community.  The SciPy
-project does not organise in-person events, however events related to our
-community should have a code of conduct similar in spirit to this one.
+Twitter, and any other communication channel used by our community. The
+PyWavelets project does not organise in-person events, however events related
+to our community should have a code of conduct similar in spirit to this one.
 
 This code of conduct should be honored by everyone who participates in
-the SciPy community formally or informally, or claims any affiliation with the
-project, in any project-related activities and especially when representing the
-project, in any role.
+the PyWavelets community formally or informally, or claims any affiliation with
+the project, in any project-related activities and especially when representing
+the project, in any role.
 
 This code is not exhaustive or complete. It serves to distill our common
 understanding of a collaborative, shared environment and goals. Please try to
 follow this code in spirit as much as in letter, to create a friendly and
 productive environment that enriches the surrounding community.
 
+This code of conduct was adapted from SciPy's code of conduct without any
+substantial modification in terms. We wish to thank the SciPy contributors for
+their hard work in authoring these terms and in helping develop a community
+consensus them.
+
 
 Specific Guidelines
 -------------------
@@ -53,7 +58,7 @@ We strive to:
 
 5. Be careful in the words that we choose.  We are careful and respectful in
    our communication and we take responsibility for our own speech. Be kind to
-   others. Do not insult or put down other participants.  We will not accept
+   others. Do not insult or put down other participants. We will not accept
    harassment or other exclusionary behaviour, such as:
 
   - Violent threats or language directed against another person.
@@ -72,8 +77,8 @@ We strive to:
 Diversity Statement
 -------------------
 
-The SciPy project welcomes and encourages participation by everyone. We are
-committed to being a community that everyone enjoys being part of. Although
+The PyWavelets project welcomes and encourages participation by everyone. We
+are committed to being a community that everyone enjoys being part of. Although
 we may not always be able to accommodate each individual's preferences, we try
 our best to treat everyone kindly.
 
@@ -84,11 +89,10 @@ national origin, neurotype, phenotype, political beliefs, profession, race,
 religion, sexual orientation, socioeconomic status, subculture and technical
 ability, to the extent that these do not conflict with this code of conduct.
 
-
-Though we welcome people fluent in all languages, SciPy development is
+Though we welcome people fluent in all languages, PyWavelets development is
 conducted in English.
 
-Standards for behaviour in the SciPy community are detailed in the Code of
+Standards for behaviour in the PyWavelets community are detailed in the Code of
 Conduct above. Participants in our community should uphold these standards
 in all their interactions and help others to do so as well (see next section).
 
@@ -109,20 +113,18 @@ most appropriate). If you would prefer not to do that, please feel free to
 report to the Code of Conduct Committee directly, or ask the Committee for
 advice, in confidence.
 
-You can report issues to the SciPy Code of Conduct committee, at
-scipy-conduct@googlegroups.com. Currently, the committee consists of:
+You can report issues to the PyWavelets Code of Conduct committee, at
+PyWavelets-conduct@googlegroups.com. Currently, the committee consists of:
 
-- Stefan van der Walt
-- Nathaniel J. Smith
+- Gregory Lee
 - Ralf Gommers
 
 If your report involves any members of the committee, or if they feel they have
 a conflict of interest in handling it, then they will recuse themselves from
 considering your report. Alternatively, if for any reason you feel
 uncomfortable making a report to the committee, then you can also contact:
 
-- Chair of the SciPy Steering Committee: Ralf Gommers, or
-- Senior `NumFOCUS staff <https://numfocus.org/code-of-conduct#persons-responsible>`__: conduct@numfocus.org
+- Chair of the PyWavelets Steering Committee: Gregory Lee
 
 
 Incident reporting resolution & Code of Conduct enforcement
@@ -131,14 +133,14 @@ Incident reporting resolution & Code of Conduct enforcement
 *This section summarizes the most important points, more details can be found
 in* :ref:`CoC_reporting_manual`.
 
-We will investigate and respond to all complaints. The SciPy Code of Conduct
-Committee and the SciPy Steering Committee (if involved) will protect the
-identity of the reporter, and treat the content of complaints as confidential
-(unless the reporter agrees otherwise).
+We will investigate and respond to all complaints. The PyWavelets Code of
+Conduct Committee and the PyWavelets Steering Committee (if involved) will
+protect the identity of the reporter, and treat the content of complaints as
+confidential (unless the reporter agrees otherwise).
 
 In case of severe and obvious breaches, e.g. personal threat or violent, sexist
-or racist language, we will immediately disconnect the originator from SciPy
-communication channels; please see the manual for details.
+or racist language, we will immediately disconnect the originator from
+PyWavelets communication channels; please see the manual for details.
 
 In cases not involving clear severe and obvious breaches of this code of
 conduct, the process for acting on any received code of conduct violation
@@ -157,8 +159,12 @@ within 72 hours.
 Endnotes
 --------
 
-We are thankful to the groups behind the following documents, from which we
-drew content and inspiration:
+We are thankful to the SciPy developers for creating the code of conduct we
+have adapated here.
+
+- `Scipy Code of Conduct <http://scipy.github.io/devdocs/dev/conduct/code_of_conduct.html>`_
+
+The SciPy code of conduct was in turn inspired by the following documents:
 
 - `The Apache Foundation Code of Conduct <https://www.apache.org/foundation/policies/conduct.html>`_
 - `The Contributor Covenant <https://www.contributor-covenant.org/version/1/4/code-of-conduct/>`_

doc/source/dev/conduct/report_handling_manual.rst

@@ -2,11 +2,11 @@
 
 .. _CoC_reporting_manual:
 
-SciPy Code of Conduct - How to follow up on a report
-----------------------------------------------------
+PyWavelets Code of Conduct - How to follow up on a report
+---------------------------------------------------------
 
-This is the manual followed by SciPy's Code of Conduct Committee. It's used
-when we respond to an issue to make sure we're consistent and fair.
+This is the manual followed by PyWavelets's Code of Conduct Committee. It's
+used when we respond to an issue to make sure we're consistent and fair.
 
 Enforcing the Code of Conduct impacts our community today and for the future.
 It's an action that we do not take lightly. When reviewing enforcement
@@ -100,15 +100,16 @@ severe breaches like personal threats, violent, sexist or racist language.
 When a member of the Code of Conduct committee becomes aware of a clear and
 severe breach, they will do the following:
 
-* Immediately disconnect the originator from all SciPy communication channels.
+* Immediately disconnect the originator from all PyWavelets communication
+  channels.
 * Reply to the reporter that their report has been received and that the
   originator has been disconnected.
 * In every case, the moderator should make a reasonable effort to contact the
   originator, and tell them specifically how their language or actions
   qualify as a "clear and severe breach".  The moderator should also say
   that, if the originator believes this is unfair or they want to be
-  reconnected to SciPy, they have the right to ask for a review, as below, by
-  the Code of Conduct Committee.
+  reconnected to PyWavelets, they have the right to ask for a review, as below,
+  by the Code of Conduct Committee.
   The moderator should copy this explanation to the Code of Conduct Committee.
 * The Code of Conduct Committee will formally review and sign off on all cases
   where this mechanism has been applied to make sure it is not being used to
@@ -195,22 +196,22 @@ Possible responses may include:
   temporarily refrain from community participation. If the individual chooses
   not to take a temporary break voluntarily, the committee may issue a
   "mandatory cooling off period".
-* A permanent or temporary ban from some or all SciPy spaces (mailing lists,
-  gitter.im, etc.). The group will maintain records of all such bans so that
-  they may be reviewed in the future or otherwise maintained.
+* A permanent or temporary ban from some or all PyWavelets spaces (mailing
+  lists, gitter.im, etc.). The group will maintain records of all such bans so
+  that they may be reviewed in the future or otherwise maintained.
 
 Once a resolution is agreed upon, but before it is enacted, the committee will
 contact the original reporter and any other affected parties and explain the
 proposed resolution. The committee will ask if this resolution is acceptable,
 and must note feedback for the record.
 
-Finally, the committee will make a report to the SciPy Steering Council (as
-well as the SciPy core team in the event of an ongoing resolution, such as a
-ban).
+Finally, the committee will make a report to the PyWavelets Steering Council
+(as well as the PyWavelets core team in the event of an ongoing resolution,
+such as a ban).
 
 The committee will never publicly discuss the issue; all public statements will
-be made by the chair of the Code of Conduct Committee or the SciPy Steering
-Council.
+be made by the chair of the Code of Conduct Committee or the PyWavelets
+Steering Council.
 
 
 Conflicts of Interest