[GOV] Use the NumFOCUS code of conduct and rename aeon workgroup (#2852)

* code of conduct update and readmes

* typo

---------

Co-authored-by: Sebastian Schmidl <10573700+SebastianSchmidl@users.noreply.github.com>

Author: MatthewMiddlehurst

.github/ISSUE_TEMPLATE/config.yml

@@ -9,5 +9,5 @@ contact_links:
     url: https://mailxto.com/jbp3ave49x
     about: Send an email to the aeon developers at contact@aeon-toolkit.org. Checked periodically.
   - name: "\u2709\uFE0F CoC Report"
-    url: https://www.aeon-toolkit.org/en/latest/code_of_conduct.html
-    about: Report an incident to the Code of Conduct Workgroup.
+    url: https://www.aeon-toolkit.org/en/stable/code_of_conduct.html
+    about: Report an incident to the Code of Conduct Moderators.

.github/utilities/generate_developer_tables.py

@@ -42,8 +42,8 @@ def get(url, auth):
 
 def get_contributors(auth):
     """Get the list of contributor profiles. Require admin rights."""
-    cocw = []
-    cocw_slug = "aeon-code-of-conduct-workgroup"
+    cocm = []
+    cocm_slug = "aeon-code-of-conduct-moderators"
     cw = []
     cw_slug = "aeon-communications-workgroup"
     cd = []
@@ -60,15 +60,15 @@ def get_contributors(auth):
     entry_point = "https://api.github.com/orgs/aeon-toolkit/"
 
     for team_slug, lst in zip(
-        (cocw_slug, cw_slug, cd_slug, fw_slug, iw_slug, rmw_slug, sd_slug),
-        (cocw, cw, cd, fw, iw, rmw, sd),
+        (cocm_slug, cw_slug, cd_slug, fw_slug, iw_slug, rmw_slug, sd_slug),
+        (cocm, cw, cd, fw, iw, rmw, sd),
     ):
         for page in range(5):  # 5 pages, 30 per page
             reply = get(f"{entry_point}teams/{team_slug}/members?page={page}", auth)
             lst.extend(reply.json())
 
     # keep only the logins
-    cocw = {c["login"] for c in cocw}
+    cocm = {c["login"] for c in cocm}
     cw = {c["login"] for c in cw}
     cd = {c["login"] for c in cd}
     fw = {c["login"] for c in fw}
@@ -77,7 +77,7 @@ def get_contributors(auth):
     sd = {c["login"] for c in sd}
 
     # get profiles from GitHub
-    cocw = [get_profile(login, auth) for login in cocw]
+    cocm = [get_profile(login, auth) for login in cocm]
     cw = [get_profile(login, auth) for login in cw]
     cd = [get_profile(login, auth) for login in cd]
     fw = [get_profile(login, auth) for login in fw]
@@ -86,7 +86,7 @@ def get_contributors(auth):
     sd = [get_profile(login, auth) for login in sd]
 
     # sort by last name
-    cocw = sorted(cocw, key=key)
+    cocm = sorted(cocm, key=key)
     cw = sorted(cw, key=key)
     cd = sorted(cd, key=key)
     fw = sorted(fw, key=key)
@@ -95,7 +95,7 @@ def get_contributors(auth):
     sd = sorted(sd, key=key)
 
     return (
-        cocw,
+        cocm,
         cw,
         cd,
         fw,
@@ -154,7 +154,7 @@ def generate_table(contributors):
         auth = ("user", token)
 
     (
-        cocw,
+        cocm,
         cw,
         cd,
         fw,
@@ -164,11 +164,11 @@ def generate_table(contributors):
     ) = get_contributors(auth)
 
     with open(
-        REPO_FOLDER / "docs" / "about" / "code_of_conduct_workgroup.md",
+        REPO_FOLDER / "docs" / "about" / "code_of_conduct_moderators.md",
         "w+",
         encoding="utf-8",
     ) as rst_file:
-        rst_file.write(generate_table(cocw))
+        rst_file.write(generate_table(cocm))
 
     with open(
         REPO_FOLDER / "docs" / "about" / "communications_workgroup.md",

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-You can find the aeon changelog on our [website](https://www.aeon-toolkit.org/en/stable/changelog.html).
+You can find the `aeon` changelog pages on our [website](https://www.aeon-toolkit.org/en/stable/changelog.html).
 
 `aeon` adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html>) and the source code for
 all [releases](https://github.com/aeon-toolkit/aeon/releases>) is available on GitHub.

CODE_OF_CONDUCT.md

@@ -1,12 +1,66 @@
 # Code of Conduct
 
-You can find our full Code of Conduct (CoC) on our [website](https://www.aeon-toolkit.org/en/stable/code_of_conduct.html).
+We value the participation of every member in our community and want to
+ensure that every contributor has an enjoyable experience. Accordingly, those who
+participate in the `aeon` project are expected to show respect and courtesy to other
+community members at all times.
 
-The code of conduct aims to ensure a positive and respectful experience for all
-members of the community. Community members should follow the principles set out in
-the [Python Software Foundation Code of Conduct](https://www.python.org/psf/codeofconduct/).
+`aeon` uses the NumFOCUS Code of Conduct (CoC). You can find the [whole document
+here](https://numfocus.org/code-of-conduct).
 
-If you want to make a CoC report, contact the general `aeon` email
-[contact@aeon-toolkit.org](mailto:contact@aeon-toolkit.org) or message a member of the
-[Code of Conduct Workgroup (COCW)](https://www.aeon-toolkit.org/en/stable/about.html#code-of-conduct-workgroup)
-directly on [Slack](https://join.slack.com/t/aeon-toolkit/shared_invite/zt-36dlmbouu-vajTShUYAHopSXUUVtHGzw).
+Everyone participating in activities associated with the `aeon` project (whether
+in-person or remote) is required to conform to this Code of Conduct regardless
+of platform.
+
+## The Short Version
+
+`aeon` and NumFOCUS are dedicated to providing a harassment-free community for everyone,
+regardless of gender, sexual orientation, gender identity and expression, disability,
+physical appearance, body size, race, or religion. We do not tolerate harassment of
+community members in any form.
+
+Be kind to others. Do not insult or put down others. Behave professionally. Remember
+that harassment and sexist, racist, or exclusionary jokes are not appropriate for
+`aeon` or NumFOCUS.
+
+All communication should be appropriate for a professional audience, including people
+of many different backgrounds. Sexual language and imagery are not appropriate.
+
+Thank you for helping make this a welcoming, friendly community for all.
+
+## How to Report
+
+If you feel that the Code of Conduct has been violated, feel free to Contact a member of
+the `aeon` [Code of Conduct Moderators](https://www.aeon-toolkit.org/en/stable/about.html#code-of-conduct-moderators)
+directly on [Slack](https://join.slack.com/t/aeon-toolkit/shared_invite/zt-36dlmbouu-vajTShUYAHopSXUUVtHGzw)
+or through the general `aeon` email ([contact@aeon-toolkit.org](mailto:contact@aeon-toolkit.org)).
+
+OR
+
+Submit a report directly to the NumFOCUS Code of Conduct Working Group by using
+[NumFOCUS Code of Conduct Reporting Form](https://numfocus.typeform.com/to/ynjGdT?typeform-source=numfocus.org).
+
+## Who Will Receive Your Report
+
+If you have contacted the `aeon` Code of Conduct Moderators, the group will decide
+whether to take action directly or forward it to the NumFOCUS Code of Conduct Working
+Group. The workgroup may take immediate action if the situation requires it (e.g.
+deleting a post, banning a user from a channel, etc.).
+
+Using the NumFOCUS form, your report will be received and handled by NumFOCUS Code of
+Conduct Working Group; trained and experienced contributors with diverse backgrounds.
+The group is making decisions independently of `aeon`, PyData, NumFOCUS or any other
+organisation. You can learn more about the current NumFOCUS group members, as well as
+the reporting procedure [here](https://numfocus.org/code-of-conduct).
+
+## Actions Taken on Reports
+
+Final decision-making on any report actions lies with the `aeon` Code of Conduct
+Moderators. In most cases, however, the moderators will enforce the recommendations
+made by the NumFOCUS Code of Conduct Working Group. If you are unhappy with a decision
+made directly by the `aeon` Code of Conduct Moderators, you can contact the NumFOCUS
+Code of Conduct Working Group directly through the reporting form.
+
+Breaking the Code of Conduct may result in a range of actions, from a warning
+to removal from `aeon` and its community spaces depending on the severity of the
+action and prior history of violations.

CONTRIBUTING.md

@@ -1,3 +1,8 @@
-# Contributing guide
+# Contributing Guide
 
-You can find our contributing guide on our [website](https://www.aeon-toolkit.org/en/stable/contributing.html).
+`aeon` is a community-driven project and contributions are most welcome. We value
+all kinds of contributions, not just code. Improvements to docs, bug reports, and
+taking on communications or code of conduct responsibilities are all examples of
+valuable contributions beyond code which help make aeon a great package.
+
+You can find our full contributing guide on our [website](https://www.aeon-toolkit.org/en/stable/contributing.html).

GOVERNANCE.md

@@ -9,7 +9,7 @@ engaging with the community, and steering the project. Tasks are delegated to
 workgroups, which are groups of core developers and contributors assigned by
 core developers to fulfil a specific role.
 
-aeon's decision-making process is transparent and consensus-based.
+`aeon`'s decision-making process is transparent and consensus-based.
 Most decisions involve seeking consensus among contributors and core developers.
 If consensus is not reached, a vote can be called, requiring a two-thirds majority
 of core developers for approval. The process emphasises transparency and open

docs/about.md

@@ -5,12 +5,12 @@
 The roles are described in `aeon`'s [governance](governance.md) document.
 A list of all contributors can be found [here](contributors.md).
 
-### Code of Conduct Workgroup
+### Code of Conduct Moderators
 
-The code of conduct workgroup maintains the code of conduct and handles any
-issues related that arise.
+The code of conduct moderators maintain the code of conduct and make decisions on any
+code of conduct related issues.
 
-```{include} about/code_of_conduct_workgroup.md
+```{include} about/code_of_conduct_moderators.md
 ```
 
 ### Communications Workgroup

docs/about/code_of_conduct_workgroup.md renamed to docs/about/code_of_conduct_moderators.md

@@ -1,43 +1,2 @@
-# Code of Conduct
-
-We value the participation of every member in our community and want to
-ensure that every contributor has an enjoyable experience. Accordingly, those who
-participate in the `aeon` project are expected to show respect and courtesy to other
-community members at all times.
-
-Everyone participating in activities associated with the `aeon` project (whether
-in-person or remote) is required to conform to this Code of Conduct (CoC) regardless
-of platform.
-
-It is expected that community members will abide by the principles of the [Python
-Software Foundation Code of Conduct](https://www.python.org/psf/codeofconduct/) to
-help maintain an open, considerate and respectful environment.
-
-Unacceptable behaviour and code of conduct violations are determined and dealt with
-at the discretion of the `aeon` [Code of Conduct Workgroup (COCW)](./governance.md#code-of-conduct-workgroup).
-Possible actions taken include warnings, mediated meeting and/or apologies, and
-expulsion from the project depending on the severity of the breach. The COCW can edit
-and remove comments and other contributions that are not aligned to this Code of
-Conduct.
-
-Examples of unacceptable behaviour include (but are not limited to):
-- Personal attacks, insults and threats
-- Harassment of individuals or groups both publicly and privately
-- Publishing private information of others, such as physical or electronic
-addresses, without explicit permission
-- The use of sexualised language or imagery in conversation or talks
-- Jokes or insults based on stereotypes, slurs or other exclusionary language
-- Continued one-on-one communication after requests to cease
-- General unethical and unprofessional conduct
-
-Community members asked to stop any inappropriate behaviour are expected to comply
-immediately.
-
-If you believe someone is violating the CoC, we ask that you report it by
-contacting the COCW. All reports will be kept confidential. You can make a report by
-emailing the general `aeon` contact address [contact@aeon-toolkit.org](mailto:contact@aeon-toolkit.org),
-or by messaging [members of the COCW](./about.md#code-of-conduct-workgroup)
-directly on [Slack](https://join.slack.com/t/aeon-toolkit/shared_invite/zt-36dlmbouu-vajTShUYAHopSXUUVtHGzw).
-
-Thank you for reading and helping make this a welcoming, friendly community for
-everyone.
+```{include} ../CODE_OF_CONDUCT.md
+```

docs/code_of_conduct.md

@@ -100,17 +100,19 @@ responsible for managing access to the `aeon` email address. To help manage
 GitHub discussions, the communication workgroup is given triage access to the `aeon`
 GitHub repository.
 
-#### Code of Conduct Workgroup
+#### Code of Conduct Moderators
 
-The Code of Conduct Workgroup (CoCW) consists of contributors tasked with making sure
-`aeon` remains a welcoming and inclusive community. CoCW responsibilities include
-maintaining the `aeon` Code of Conduct (CoC) and managing reports of breaking the CoC.
-CoCW members are expected to review reports of CoC violations, contact and discuss with
-involved individuals and make recommendations on actions to take.
+The Code of Conduct Moderators (CoCM) consists of contributors tasked with making sure
+`aeon` remains a welcoming and inclusive community. CoCM responsibilities include
+ensuring the Code of Conduct (CoC) remains up to date, keeping contact with the
+NumFOCUS Code of Conduct Workgroup and managing reports of breaking the CoC.
+CoCM members are expected to review reports of CoC violations, refer cases to the
+NumFOCUS workgroup when applicable and make decisions on report actions while
+consulting with the greater community.
 
-Any CoCW members involved in a CoC report or CoCW members which have a conflict of
+Any CoCM members involved in a CoC report or CoCM members which have a conflict of
 interest regarding the report are expected to recuse themselves from the process. The
-CoCW is given triage access to the `aeon` GitHub repository to moderate discussions if
+CoCM is given triage access to the `aeon` GitHub repository to moderate discussions if
 necessary.
 
 ## Decision-Making Process
@@ -165,7 +167,7 @@ submitted to the community for discussion and comment.
 
 ## Acknowledgements
 
-Significant portions of this document were adapted from or inspired by the following
+Portions of this document were adapted from or inspired by the following
 projects governance documents:
 
 - [Scikit-learn](https://scikit-learn.org/stable/governance.html)