openstef 4.1.1.dev0__tar.gz → 4.1.2__tar.gz

openstef-4.1.2/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,70 @@
+---
+name: Bug report
+about: Report a problem with OpenSTEF to help us reproduce and fix it
+title: ''
+labels: ['bug']
+type: Bug
+assignees: ''
+---
+
+<!--
+Thanks for taking the time to file a bug report! Please search existing
+issues first to avoid duplicates: https://github.com/OpenSTEF/openstef/issues
+-->
+
+## Describe the bug and its impact
+
+<!-- A clear and concise description of the bug, and how it affects you as an OpenSTEF user. -->
+
+## Affected package(s)
+
+<!-- Check all that apply. -->
+
+- [ ] openstef-core
+- [ ] openstef-models
+- [ ] openstef-beam
+- [ ] openstef-foundation-models
+- [ ] openstef-meta
+- [ ] examples / deployment
+- [ ] docs
+- [ ] not sure
+
+## Steps / code to reproduce
+
+<!--
+A minimal, self-contained code example that reproduces the problem. Prefer
+synthetic data (e.g. numpy/pandas generated data) over external files. If the
+bug only reproduces with realistic load/weather shapes, you can also point to
+the published Liander benchmark dataset:
+https://huggingface.co/datasets/OpenSTEF/liander2024-energy-forecasting-benchmark
+-->
+
+```python
+# Minimal example to reproduce the bug
+```
+
+## Expected behavior
+
+## Actual behavior
+
+<!-- If an exception was raised, please include the full traceback. -->
+
+```python-traceback
+Paste the full traceback here
+```
+
+## Environment
+
+<!-- OpenSTEF package version(s) (`uv pip list | grep openstef`), Python version, and OS. -->
+
+```shell
+openstef-core:
+Python:
+OS:
+```
+
+## Additional context
+
+## Would you be interested in submitting a fix?
+
+- [ ] I'd be interested in opening a PR for this once triaged

openstef-4.1.2/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask a question on Slack
+    url: https://slack.lfenergy.org/
+    about: Join the #openstef channel on the LF Energy Slack workspace for questions and discussion.
+  - name: Four-weekly co-coding meetings
+    url: https://lf-energy.atlassian.net/wiki/spaces/OS/pages/32278358/Four-weekly+community+meeting
+    about: Join a community meeting to get help or discuss ideas in real time.
+  - name: Documentation
+    url: https://openstef.github.io/openstef/
+    about: Check the docs, user guide, and API reference before opening an issue.

openstef-4.1.2/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,51 @@
+---
+name: Feature request
+about: Suggest an idea or improvement for OpenSTEF
+title: ''
+labels: ['enhancement']
+type: Feature
+assignees: ''
+---
+
+<!--
+Thanks for suggesting an improvement! Please search existing issues first to
+avoid duplicates: https://github.com/OpenSTEF/openstef/issues
+-->
+
+## Is your feature request related to a problem?
+
+<!-- A clear and concise description of the problem. Ex. I'm always frustrated when [...] -->
+
+## Describe the solution you'd like
+
+## Describe alternatives you've considered
+
+## Affected package(s)
+
+<!-- Check all that apply. -->
+
+- [ ] openstef-core
+- [ ] openstef-models
+- [ ] openstef-beam
+- [ ] openstef-foundation-models
+- [ ] openstef-meta
+- [ ] examples / deployment
+- [ ] docs
+- [ ] not sure
+
+## Would this require breaking changes to the public API?
+
+<!--
+Consider public API changes, and, for anything that gets pickled (transforms,
+scalers, models), whether existing serialized objects would need a state
+migration. See the breaking changes checklist in the PR template:
+https://github.com/OpenSTEF/openstef/blob/main/.github/PULL_REQUEST_TEMPLATE.md
+-->
+
+- [ ] No
+- [ ] Yes
+- [ ] Not sure
+
+## Additional context
+
+<!-- Add any other context, mockups, or references here. -->

openstef-4.1.2/.github/ISSUE_TEMPLATE/task.md

@@ -0,0 +1,86 @@
+---
+name: Task
+about: Track a piece of planned work (feature, chore, refactor, etc.) to be picked up later
+title: ''
+labels: ['to refine']
+type: Task
+assignees: ''
+---
+
+<!--
+Use this template to track planned work — a feature to build, a chore, a
+refactor, or anything else that isn't a bug report. See the development
+workflow for how work gets picked up:
+https://openstef.github.io/openstef/contribute/development_workflow.html
+-->
+
+## Type of work
+
+<!-- Check one. -->
+
+- [ ] Feature
+- [ ] Chore / refactor
+- [ ] Documentation
+- [ ] Performance
+- [ ] Epic (spans multiple issues)
+
+## Summary
+
+<!--
+What needs to be done, and why? ("As a ..., I want ..., so that ..." is fine
+if it helps, but a plain description works too.)
+-->
+
+## Background
+
+<!--
+Context that helps a contributor understand the "why": what prompted this,
+links to related discussions/issues/docs, current behavior vs. desired
+behavior.
+-->
+
+## Priority
+
+<!--
+What happens if this isn't done? Any deadlines or dependencies driving the
+timing? Leave blank if there's no particular urgency.
+-->
+
+## Affected package(s)
+
+<!-- Check all that apply. -->
+
+- [ ] openstef-core
+- [ ] openstef-models
+- [ ] openstef-beam
+- [ ] openstef-foundation-models
+- [ ] openstef-meta
+- [ ] examples / deployment
+- [ ] docs
+- [ ] not sure
+
+## Definition of done
+
+**Acceptance criteria** — what does "done" look like?
+
+- [ ]
+- [ ]
+
+**Documentation** — does this need user guide, API reference, or example updates?
+
+- [ ] No documentation changes needed
+- [ ] Documentation will be updated as part of this work
+
+**Tests** — how will this be verified?
+
+- [ ] No new tests needed
+- [ ] Unit/integration tests will be added
+
+## Dependencies
+
+<!-- Blocking issues, related PRs, or prerequisite work. Leave blank if none. -->
+
+<!--
+Maintainers will triage this with the appropriate labels (feature, chore,
+enhancement, good first issue, ready-to-implement, ...) during refinement.
+-->

openstef-4.1.2/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,50 @@
+<!--
+Thanks for contributing to OpenSTEF! Please fill out this template to help us
+review your PR efficiently. See the contributing guide for more details:
+https://openstef.github.io/openstef/contribute/index.html
+-->
+
+## What does this PR do?
+
+<!-- Describe the change and the motivation behind it. -->
+
+Closes #
+
+## Type of change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change (see checklist below)
+- [ ] Documentation
+- [ ] Refactor / chore / CI
+
+## Breaking changes checklist
+
+<!-- Only relevant if you checked "Breaking change" above, or are unsure. -->
+
+- [ ] Public API, config schema, or serialized/pickled objects changed in a way that affects existing users
+- [ ] If yes: see the [breaking changes guide](https://openstef.github.io/openstef/contribute/development_workflow.html#breaking-changes) for the pickle/`_migrate_state` migration pattern
+
+Migration path for existing users (e.g. "old pickled `XScaler` objects auto-migrate on load", "users must now pass `X` explicitly"):
+
+<!-- describe here -->
+
+## AI disclosure
+
+<!--
+See our AI-assisted contributions guidelines:
+https://openstef.github.io/openstef/contribute/contributing_guide.html#ai-assisted-contributions
+-->
+
+- [ ] No AI assistance was used (beyond grammar/spelling)
+- [ ] AI assistance was used — tool(s): <!-- e.g. GitHub Copilot, Claude, ChatGPT -->
+  - [ ] I have reviewed, understand, and can explain all AI-generated code in this PR
+  - [ ] This is disclosed in a commit message (e.g. `Assisted-by: <tool name>`)
+
+## Checklist
+
+- [ ] `poe all --check` passes locally
+- [ ] Tests added/updated for the change
+- [ ] Documentation updated (docstrings, user guide, examples) if needed
+- [ ] Commits are signed off per our [DCO](https://openstef.github.io/openstef/contribute/contributing_guide.html#signing-the-developer-certificate-of-origin-dco) (`git commit -s`)
+- [ ] PR title follows [Conventional Commits](https://www.conventionalcommits.org/) (e.g. `feat: ...`, `fix: ...`, `feat!: ...` for breaking changes)

openstef-4.1.2/.github/pr-labeler.yml

@@ -0,0 +1,18 @@
+# SPDX-FileCopyrightText: 2017-2025 Contributors to the OpenSTEF project <openstef@lfenergy.org>
+#
+# SPDX-License-Identifier: MPL-2.0
+# config of action in ./workflows/...
+feature:
+  - head-branch:
+      - "^feature.*"
+      - "^feat.*"
+fix:
+  - head-branch:
+      - "^fix.*"
+      - "^bugfix.*"
+      - "^hotfix.*"
+      - "^bug.*"
+chore:
+  - head-branch:
+      - "^chore.*"
+      - "^doc.*"

openstef-4.1.2/.github/workflows/codeql.yaml

@@ -0,0 +1,46 @@
+# SPDX-FileCopyrightText: 2026 Contributors to the OpenSTEF project <openstef@lfenergy.org>
+# SPDX-License-Identifier: MPL-2.0
+
+name: CodeQL
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+on:
+  push:
+    branches: ['main']
+  pull_request:
+    types: [opened, synchronize, reopened]
+  schedule:
+    # Weekly full scan so advisories that land after a merge still surface.
+    - cron: '30 4 * * 1'
+
+permissions:
+  contents: read
+
+jobs:
+  analyze:
+    name: Analyze (Python)
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write # Upload results to the Security tab
+      actions: read
+      contents: read
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@411c4c9a36b3fca4d674f06b6396b2c6d23522c6 # v3
+        with:
+          languages: python
+          build-mode: none # Python is interpreted; no build step required
+          # security-extended keeps CodeQL focused on vulnerability queries;
+          # the maintainability/reliability queries in security-and-quality
+          # overlap ruff and SonarCloud.
+          queries: security-extended
+
+      - name: Perform CodeQL analysis
+        uses: github/codeql-action/analyze@411c4c9a36b3fca4d674f06b6396b2c6d23522c6 # v3
+        with:
+          category: '/language:python'

{openstef-4.1.1.dev0 → openstef-4.1.2}/.github/workflows/pr-labeler.yaml

@@ -1,21 +1,19 @@
 # SPDX-FileCopyrightText: 2017-2022 Contributors to the OpenSTEF project <openstef@lfenergy.org>
 #
 # SPDX-License-Identifier: MPL-2.0
-# Automatically label PRs, config in ../pr-labler.yml
+# Automatically label PRs, config in ../pr-labeler.yml
 name: PR Labeler
 on:
-  pull_request:
+  pull_request_target:
     types: [opened]
 
 jobs:
   pr-labeler:
     permissions:
-        contents: read # To read config file
-        pull-requests: write # To add labels
+      contents: read # To read config file
+      pull-requests: write # To add labels
     runs-on: ubuntu-latest
     steps:
-      - uses: TimonVS/pr-labeler-action@f9c084306ce8b3f488a8f3ee1ccedc6da131d1af # v5
+      - uses: actions/labeler@f27b608878404679385c85cfa523b85ccb86e213 # v6.1.0
         with:
           configuration-path: .github/pr-labeler.yml
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

{openstef-4.1.1.dev0 → openstef-4.1.2}/.gitignore

@@ -71,6 +71,8 @@ docs/source/user_guide/**/quick_start_tutorial.py
 docs/source/user_guide/**/feature_engineering_tutorial.py
 docs/source/user_guide/**/datasets_tutorial.py
 docs/source/user_guide/**/backtesting_tutorial.py
+docs/source/user_guide/**/foundation_model_forecasting_quickstart.py
+docs/source/user_guide/**/foundation_model_forecasting.py
 
 # docs/_doctrees/
 # docs/_static_gen/

{openstef-4.1.1.dev0 → openstef-4.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: openstef
-Version: 4.1.1.dev0
+Version: 4.1.2
 Summary: Open Short Term Energy forecasting library
 Project-URL: Documentation, https://openstef.github.io/openstef/index.html
 Project-URL: Homepage, https://lfenergy.org/projects/openstef/
@@ -16,26 +16,26 @@ Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: <4.0,>=3.12
-Requires-Dist: openstef-core==4.1.1.dev0
-Requires-Dist: openstef-models[xgb-cpu]==4.1.1.dev0
+Requires-Dist: openstef-core==4.1.2
+Requires-Dist: openstef-models[xgb-cpu]==4.1.2
 Provides-Extra: all
-Requires-Dist: openstef-beam[all]==4.1.1.dev0; extra == 'all'
-Requires-Dist: openstef-core==4.1.1.dev0; extra == 'all'
-Requires-Dist: openstef-foundation-models[cpu]==4.1.1.dev0; extra == 'all'
-Requires-Dist: openstef-meta==4.1.1.dev0; extra == 'all'
-Requires-Dist: openstef-models[xgb-cpu]==4.1.1.dev0; extra == 'all'
+Requires-Dist: openstef-beam[all]==4.1.2; extra == 'all'
+Requires-Dist: openstef-core==4.1.2; extra == 'all'
+Requires-Dist: openstef-foundation-models[cpu]==4.1.2; extra == 'all'
+Requires-Dist: openstef-meta==4.1.2; extra == 'all'
+Requires-Dist: openstef-models[xgb-cpu]==4.1.2; extra == 'all'
 Provides-Extra: beam
 Requires-Dist: huggingface-hub>=0.35.3; extra == 'beam'
-Requires-Dist: openstef-beam==4.1.1.dev0; extra == 'beam'
+Requires-Dist: openstef-beam==4.1.2; extra == 'beam'
 Provides-Extra: core
-Requires-Dist: openstef-core==4.1.1.dev0; extra == 'core'
+Requires-Dist: openstef-core==4.1.2; extra == 'core'
 Provides-Extra: foundation-models
-Requires-Dist: openstef-foundation-models[cpu]==4.1.1.dev0; extra == 'foundation-models'
+Requires-Dist: openstef-foundation-models[cpu]==4.1.2; extra == 'foundation-models'
 Provides-Extra: meta
-Requires-Dist: openstef-meta==4.1.1.dev0; extra == 'meta'
+Requires-Dist: openstef-meta==4.1.2; extra == 'meta'
 Provides-Extra: models
-Requires-Dist: openstef-meta==4.1.1.dev0; extra == 'models'
-Requires-Dist: openstef-models[xgb-cpu]==4.1.1.dev0; extra == 'models'
+Requires-Dist: openstef-meta==4.1.2; extra == 'models'
+Requires-Dist: openstef-models[xgb-cpu]==4.1.2; extra == 'models'
 Description-Content-Type: text/markdown
 
 <!--

{openstef-4.1.1.dev0 → openstef-4.1.2}/REUSE.toml

@@ -3,6 +3,7 @@ version = 1
 [[annotations]]
 path = [
     ".github/ISSUE_TEMPLATE/**",
+    ".github/PULL_REQUEST_TEMPLATE.md",
     ".python-version",
     "uv.lock",
     "examples/*/*.ipynb",

{openstef-4.1.1.dev0 → openstef-4.1.2}/docs/pyproject.toml

@@ -35,6 +35,7 @@ dependencies = [
   "openstef",
   "openstef-beam",
   "openstef-core",
+  "openstef-foundation-models",
   "openstef-models",
   "optuna>=4.7",
   "pydata-sphinx-theme>=0.16.1",
@@ -56,4 +57,5 @@ packages = []
 sources.openstef = { workspace = true }
 sources.openstef-beam = { workspace = true }
 sources.openstef-core = { workspace = true }
+sources.openstef-foundation-models = { workspace = true }
 sources.openstef-models = { workspace = true }

openstef-4.1.2/docs/source/api/foundation_models.rst

@@ -0,0 +1,39 @@
+.. SPDX-FileCopyrightText: 2026 Contributors to the OpenSTEF project <openstef@lfenergy.org>
+..
+.. SPDX-License-Identifier: MPL-2.0
+
+.. _foundation-models-api:
+
+Foundation Models Package (:mod:`openstef_foundation_models`)
+=============================================================
+
+.. currentmodule:: openstef_foundation_models
+
+Pretrained foundation-model forecasters that run on an ONNX inference runtime and plug
+into openstef-models workflows and openstef-beam backtesting. Chronos-2 is the first model
+family the package ships; the inference backend, provider selection, checkpoint catalog,
+and workflow machinery are model-agnostic.
+
+The package is split into four subpackages:
+
+- ``models`` holds the checkpoint catalog (:class:`~openstef_foundation_models.models.catalog.Chronos2`,
+  :class:`~openstef_foundation_models.models.catalog.CheckpointVariant`), the checkpoint
+  resolution types, and the :class:`~openstef_foundation_models.models.forecasting.chronos2_forecaster.Chronos2Forecaster`.
+- ``presets`` holds :class:`~openstef_foundation_models.presets.forecasting_workflow.ForecastingWorkflowConfig`
+  and :func:`~openstef_foundation_models.presets.forecasting_workflow.create_forecasting_workflow`,
+  the one-call path from config to a runnable workflow.
+- ``inference`` holds the :class:`~openstef_foundation_models.inference.backend.InferenceBackend`
+  protocol, the ONNX backend, the execution-provider configs, and the host-aware
+  provider selection policy.
+- ``integrations`` holds :class:`~openstef_foundation_models.integrations.beam.FoundationModelBacktestForecaster`,
+  the beam backtesting adapter.
+
+.. autosummary::
+   :toctree: generated/
+   :template: package_overview.rst
+   :recursive:
+
+   models
+   presets
+   inference
+   integrations

{openstef-4.1.1.dev0 → openstef-4.1.2}/docs/source/api/index.rst

@@ -36,6 +36,12 @@ This is the complete API reference for OpenSTEF. The API is organized into sever
 
         Ensemble forecasting and preset workflows
 
+    .. grid-item-card:: :fa:`wand-sparkles` Foundation Models Package
+        :link: foundation-models-api
+        :link-type: ref
+
+        Pretrained foundation-model forecasters on an ONNX runtime
+
 .. toctree::
    :maxdepth: 2
    :hidden:
@@ -44,6 +50,7 @@ This is the complete API reference for OpenSTEF. The API is organized into sever
    models
    beam
    meta
+   foundation_models
 
 Core Package (:mod:`openstef_core`)
 -----------------------------------
@@ -100,3 +107,15 @@ Meta Package (:mod:`openstef_meta`)
    models
    presets
    utils
+
+Foundation Models Package (:mod:`openstef_foundation_models`)
+-------------------------------------------------------------
+
+.. currentmodule:: openstef_foundation_models
+
+.. autosummary::
+
+   models
+   presets
+   inference
+   integrations

{openstef-4.1.1.dev0 → openstef-4.1.2}/docs/source/contribute/development_workflow.rst

@@ -186,6 +186,45 @@ structured commit messages that enable automated changelog generation and semant
 * Explain *what* and *why*, not just *how*
 * Use ``!`` after the type to indicate breaking changes
 
+.. _breaking-changes:
+
+Breaking changes
+=================
+
+A change is breaking if it changes public API behavior, removes/renames something
+public, or changes what gets (de)serialized. If your PR does any of this, describe
+the migration path for existing users in the pull request.
+
+Public API
+----------
+
+Renaming, removing, or changing the signature/default/behavior of a public class,
+function, method, or parameter is breaking. Prefer deprecating (with a warning) over
+removing outright when possible.
+
+Serialization / pickle compatibility
+-------------------------------------
+
+If a field was added, renamed, removed, or changed type on a ``Stateful``/``Transform``
+subclass (e.g. a scaler, encoder, or other fitted transform), previously-pickled
+instances of that class will fail to load correctly unless you migrate them:
+
+1. Bump ``_VERSION`` on the affected class.
+2. Add or update ``_migrate_state`` to migrate previously-pickled state to the new
+   shape — see `openstef_core.mixins.stateful.Stateful
+   <https://github.com/OpenSTEF/openstef/blob/main/packages/openstef-core/src/openstef_core/mixins/stateful.py>`_.
+3. Add a test that restores an old-version state and asserts it migrates correctly —
+   see `test_stateful.py
+   <https://github.com/OpenSTEF/openstef/blob/main/packages/openstef-core/tests/unit/mixins/test_stateful.py>`_
+   for the pattern.
+
+Config/settings and defaults
+-----------------------------
+
+A config/settings schema change that breaks existing configs (a field renamed,
+removed, or newly required), or a default value/behavior change that affects
+existing users' results, is also breaking and should be called out in the PR.
+
 Testing your changes
 ====================
 

{openstef-4.1.1.dev0 → openstef-4.1.2}/docs/source/examples.rst

@@ -47,8 +47,10 @@ Training & Forecasting
      - Combine multiple models into an ensemble for improved accuracy and robustness.
    * - :doc:`Hyperparameter Tuning <tutorials/hyperparameter_tuning_with_optuna>`
      - Optimize model hyperparameters using Optuna integration with cross-validated backtesting.
-   * - :doc:`Foundation-Model Forecasting <tutorials/foundation_model_forecasting>`
+   * - :doc:`Foundation Model Forecasting Quickstart <tutorials/foundation_model_forecasting_quickstart>`
      - Produce a zero-shot probabilistic forecast with the pretrained Chronos-2 model via OpenSTEF's ONNX backend, including batched multi-origin inference.
+   * - :doc:`Foundation Model Forecasting <tutorials/foundation_model_forecasting>`
+     - Choose a checkpoint, run one from disk, pick the execution provider for your hardware, and backtest with openstef-beam.
 
 Evaluation & Analysis
 ^^^^^^^^^^^^^^^^^^^^^
@@ -103,7 +105,8 @@ the docs build — run them locally to reproduce results.
    Feature Engineering <tutorials/feature_engineering>
    Ensemble Forecasting <tutorials/ensemble_forecasting>
    Hyperparameter Tuning <tutorials/hyperparameter_tuning_with_optuna>
-   Foundation-Model Forecasting <tutorials/foundation_model_forecasting>
+   Foundation Model Forecasting Quickstart <tutorials/foundation_model_forecasting_quickstart>
+   Foundation Model Forecasting <tutorials/foundation_model_forecasting>
 
 .. toctree::
    :maxdepth: 1

{openstef-4.1.1.dev0 → openstef-4.1.2}/docs/source/index.rst

@@ -119,6 +119,7 @@ Learn
                 - :doc:`openstef-beam <api/beam>` backtesting, evaluation, analysis and metrics
                 - :doc:`openstef-core <api/core>` utilities, dataset types, shared types
                 - :doc:`openstef-meta <api/meta>` metalearning and model selection
+                - :doc:`openstef-foundation-models <api/foundation_models>` pretrained foundation-model forecasters on ONNX
 
 
 What's new
@@ -170,7 +171,6 @@ About OpenSTEF
 
         * `Linux Foundation project page <https://www.lfenergy.org/projects/openstef/>`_
         * `Video About OpenSTEF <https://www.lfenergy.org/forecasting-to-create-a-more-resilient-optimized-grid/>`_
-        * :doc:`project/committee`
-        * :doc:`project/maintainers`
+        * :doc:`project/governance`
         * :doc:`project/citing`
         * :doc:`project/license`

openstef-4.1.2/docs/source/project/governance.rst

@@ -0,0 +1,14 @@
+.. SPDX-FileCopyrightText: 2025 Contributors to the OpenSTEF project <openstef@lfenergy.org>
+..
+.. SPDX-License-Identifier: MPL-2.0
+
+.. _project_governance:
+
+.. Project governance (Technical Steering Committee, Maintainers, Contributors,
+.. PyPI project management) is maintained as Markdown in the org-level
+.. OpenSTEF/.github repository (the single source of truth) and materialized
+.. into ``_community/`` at build time by ``docs/sync_sources.py``. Edit it
+.. there, not here.
+
+.. include:: ../contribute/_community/PROJECT_GOVERNANCE.md
+    :parser: myst_parser.sphinx_

{openstef-4.1.1.dev0 → openstef-4.1.2}/docs/source/project/index.rst

@@ -15,9 +15,7 @@ Community
 =========
 Here you can find all information about the OpenSTEF community.
 
-.. include:: committee.rst
-
-.. include:: maintainers.rst
+.. include:: governance.rst
 
 
 Roadmap