Merge pull request #407 from softwarepub/feature/347-update-build_backend

Fix #347: Rebuild `pyproject.toml` to adhere to PEP 621 & update poetry version

Author: sdruskat

.readthedocs.yaml

@@ -9,10 +9,15 @@ build:
   tools:
     python: "3.10"
   jobs:
+    post_create_environment:
+      # Install poetry
+      # https://python-poetry.org/docs/#installing-manually
+      - pip install "poetry>=2.1.3,<3.0.0"
     post_install:
-      - pip install "poetry>=1.2.0,<1.3.0"
-      - poetry config virtualenvs.create false
-      - poetry install --with docs
+        # Install dependencies with 'docs' dependency group
+        # https://python-poetry.org/docs/managing-dependencies/#dependency-groups
+        # VIRTUAL_ENV needs to be set manually for now, see #11150
+        - VIRTUAL_ENV=$READTHEDOCS_VIRTUALENV_PATH poetry install --with docs
 
 # Build documentation in the docs/source directory with Sphinx
 sphinx:

GOVERNANCE.md

@@ -80,5 +80,5 @@ If no successor is named,
 the Steering Group seeks a successor.
 One member of the Steering Group steps in as interim maintainer until a successor is found.
 
-In addition, all contributors with write access to repositories and regular activities should be added as "authors" to project and build system metadata in alphabetical order.
-They may also qualify for scholarly authorship, which is managed in citation metadata as necessary and may be ordered by other criteria.
+Authorship is defined by the [steering group](#hermes-steering-group) and declared in
+[`CITATION.cff`](https://github.com/softwarepub/hermes/blob/main/CITATION.cff).