Fix: update governance --> handbook

pyOpenSci · Apr 4, 2024 · c2e8d10 · c2e8d10
1 parent 4b0f79c
commit c2e8d10
Show file tree

Hide file tree

Showing 7 changed files with 17 additions and 15 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,7 +1,7 @@
 # Contributing Guide for the Python open source software packaging book
 
 Important! Before contributing to this repository, please be sure to review
-our [organization-wide contributing guide](https://www.pyopensci.org/governance/CONTRIBUTING.html) which contains guidelines for
+our [organization-wide contributing guide](https://www.pyopensci.org/handbook/CONTRIBUTING.html) which contains guidelines for
 contributions.
 
 This is a community resource. We welcome contributions in the form of issues and/or pull requests to this guide.

diff --git a/code-of-conduct.md b/code-of-conduct.md
@@ -3,4 +3,4 @@
 All individuals participating in any pyOpenSci program such as our peer review process, need to abide by our code of conduct.
 
 [Click here to
-read our full code of conduct now.](https://www.pyopensci.org/governance/CODE_OF_CONDUCT.html)
+read our full code of conduct now.](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html)
diff --git a/conf.py b/conf.py
@@ -15,7 +15,9 @@
 
 # Get the latest Git tag - there might be a prettier way to do this but...
 try:
-    release_value = subprocess.check_output(["git", "describe", "--tags"]).decode("utf-8").strip()
+    release_value = (
+        subprocess.check_output(["git", "describe", "--tags"]).decode("utf-8").strip()
+    )
     release_value = release_value[:4]
 except subprocess.CalledProcessError:
     release_value = "0.1"  # Default value in case there's no tag
@@ -61,12 +63,12 @@
 # Theme options
 html_theme_options = {
     "favicons": [
-      {
-         "rel": "icon",
-         "sizes": "16x16",
-         "href": "https://www.pyopensci.org/images/favicon.ico",
-      },
-   ],
+        {
+            "rel": "icon",
+            "sizes": "16x16",
+            "href": "https://www.pyopensci.org/images/favicon.ico",
+        },
+    ],
     "announcement": "<p><a href='https://www.github.com/pyopensci/software-submission/'>Submit Your Python Package for Peer Review!</a></p>",
     "external_links": [
         {
@@ -78,8 +80,8 @@
             "name": "Python Packaging Guide",
         },
         {
-            "url": "https://pyopensci.org/governance",
-            "name": "Governance",
+            "url": "https://pyopensci.org/handbook",
+            "name": "Handbook",
         },
     ],
     "icon_links": [

diff --git a/how-to/editors-guide.md b/how-to/editors-guide.md
@@ -346,7 +346,7 @@ reviews has been considered and implemented
 
 ## Closing notes about the editorial process
 
-- If the package raises a new issue for pyOpenSci policy, create an issue on [pyOpenSci's governance repo](https://github.com/pyOpenSci/governance).
+- If the package raises a new issue for pyOpenSci policy, create an issue on [pyOpenSci's handbook repo](https://github.com/pyOpenSci/handbook).
 - If the package review raises a new issue in our peer review process, please [open an issue in our peer review guide repo.](https://github.com/pyOpenSci/peer-review-guide).
 
 ## ✔️ OPTIONAL: Instructions for Submitting to JOSS

diff --git a/how-to/reviewer-guide.md b/how-to/reviewer-guide.md
@@ -8,7 +8,7 @@ our editors or to post a question on our [discourse forum](https://pyopensci.dis
 ```
 
 Please be respectful and kind to the authors in your reviews. Our
-[code of conduct](https://www.pyopensci.org/governance/CODE_OF_CONDUCT.html) is mandatory for everyone involved in our
+[code of conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html) is mandatory for everyone involved in our
 review process.
 
 ## A guide for new reviewers

diff --git a/our-process/how-review-works.md b/our-process/how-review-works.md
@@ -20,7 +20,7 @@ that package reviews move through the review process efficiently;
 * Authors create, submit and improve their package;
 * Reviewers, two per submission, examine the software code and user experience.
 
-Our [governance documentation](https://www.pyopensci.org/governance) clarifies
+Our [handbook documentation](https://www.pyopensci.org/handbook/) clarifies
 the various roles that support running our peer review process.
 
 ## Software reviews are contained within [GitHub](https://www.github.com/pyOpenSci) issues

diff --git a/partners/scientific-communities.md b/partners/scientific-communities.md
@@ -310,4 +310,4 @@ Over time, this investment will yield significant rewards.
 
 All our reviews are open on GitHub, ensuring transparency. Everyone
 participating in the peer review process is also expected to adhere to [our
-code of conduct.](https://www.pyopensci.org/governance/CODE_OF_CONDUCT.html)
+code of conduct.](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html)