From c2220af885c7b330076f04c049bd9554220097c5 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 13:46:41 +0200 Subject: [PATCH 1/7] Bump node.js to version 22. Some modules complained on version 20. Signed-off-by: Kurt Garloff --- .github/workflows/build.yml | 2 +- .github/workflows/build_and_deploy.yml | 2 +- .github/workflows/build_and_staging.yml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 4439e44350..fb7c2cf42a 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -16,7 +16,7 @@ jobs: - name: Setup Node uses: actions/setup-node@v3 with: - node-version: 20 + node-version: 22 - name: Cache dependencies uses: actions/cache@v3 with: diff --git a/.github/workflows/build_and_deploy.yml b/.github/workflows/build_and_deploy.yml index 5ee0439170..c4d7d106eb 100644 --- a/.github/workflows/build_and_deploy.yml +++ b/.github/workflows/build_and_deploy.yml @@ -22,7 +22,7 @@ jobs: - name: Setup Node uses: actions/setup-node@v3 with: - node-version: 20 + node-version: 22 - name: Cache dependencies uses: actions/cache@v3 diff --git a/.github/workflows/build_and_staging.yml b/.github/workflows/build_and_staging.yml index a9753f2674..d422a3cde0 100644 --- a/.github/workflows/build_and_staging.yml +++ b/.github/workflows/build_and_staging.yml @@ -20,7 +20,7 @@ jobs: - name: Setup Node uses: actions/setup-node@v3 with: - node-version: 20 + node-version: 22 - name: Cache dependencies uses: actions/cache@v3 From 75b3bf512ba6976778e66eea1bfb043c497316a5 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 13:49:33 +0200 Subject: [PATCH 2/7] One more place to put v22. Signed-off-by: Kurt Garloff --- .nvmrc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.nvmrc b/.nvmrc index 0828ab7947..53d1c14db3 100644 --- a/.nvmrc +++ b/.nvmrc @@ -1 +1 @@ -v18 \ No newline at end of file +v22 From 01702bfec565adb4ae261ba62118cd693a9f1d21 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 13:50:17 +0200 Subject: [PATCH 3/7] Use node v20. Signed-off-by: Kurt Garloff --- .nvmrc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.nvmrc b/.nvmrc index 0828ab7947..9a2a0e219c 100644 --- a/.nvmrc +++ b/.nvmrc @@ -1 +1 @@ -v18 \ No newline at end of file +v20 From b40bea4d4ae3d7125dbc9e63b31cff0dfb4e78c5 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 14:09:35 +0000 Subject: [PATCH 4/7] Fix the "here" links that are complained about. Signed-off-by: Kurt Garloff --- blog/2026-01-22-introducing-docs-blog.md | 4 ++-- community/cloud-resources/cloud-resources.md | 6 +++--- community/contribute/adding-docs-guide.md | 2 +- community/contribute/styleguides/ansible_styleguide.md | 2 +- community/tools/zuul.md | 6 +++--- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/blog/2026-01-22-introducing-docs-blog.md b/blog/2026-01-22-introducing-docs-blog.md index 7e21e22019..2df2e36e5e 100644 --- a/blog/2026-01-22-introducing-docs-blog.md +++ b/blog/2026-01-22-introducing-docs-blog.md @@ -41,8 +41,8 @@ it assembles documentation from various places. Unlike the Forum, it does not ne to prioritize neutrality as top priority, but benefits and prefers those projects that contribute useful content to it. -We have decided to use docusaurus' blog feature to publish blog articles -[here](https://docs.scs.community/blog/). We appreciate contributions. +We have decided to use docusaurus' blog feature to publish +[blog articles](https://docs.scs.community/blog/). We appreciate contributions. ## Old blog content diff --git a/community/cloud-resources/cloud-resources.md b/community/cloud-resources/cloud-resources.md index 0d12659ff9..77d37798e3 100644 --- a/community/cloud-resources/cloud-resources.md +++ b/community/cloud-resources/cloud-resources.md @@ -34,7 +34,7 @@ Once the PR has been accepted, [configure your VPN access by following the steps ### SCS Hardware Landscape Usage -More information on how to use the Hardware Landscape can be found [here](hardware-landscape.md). +Here is [more information on how to use the Hardware Landscape](hardware-landscape.md). ## SCS2 @ plusserver @@ -44,7 +44,7 @@ To apply for a new project, please create a pull request against this document ( ### SCS2 Usage -A brief guide on how to use the resources provided by plusserver GmbH can be found [here](plusserver-gx-scs.md). +Here is a [brief guide on how to use the resources provided by plusserver GmbH](plusserver-gx-scs.md). ### SCS2 Users @@ -101,7 +101,7 @@ To apply for a new project, please create a pull request against this document ( ### Wavestack Usage -A brief guide on how to use the resources provided by Wavecon GmbH can be found [here](wavestack.md). +Here is [a brief guide on how to use the resources provided by Wavecon GmbH](wavestack.md). ### Wavestack Service Users diff --git a/community/contribute/adding-docs-guide.md b/community/contribute/adding-docs-guide.md index 0dfe141991..7e0c0a4ef1 100644 --- a/community/contribute/adding-docs-guide.md +++ b/community/contribute/adding-docs-guide.md @@ -53,7 +53,7 @@ File a Pull Request within the [docs](https://github.com/SovereignCloudStack/doc Once it is approved and merged, a postinstall script will be triggered within the build process. This initiates downloading, copy and distilling which results in this static generated [documentation](https://docs.scs.community) page – now with your content. -An explanation on how the sync & distill workflow and a guide on how to test it in a local development environment you will find [here](https://github.com/SovereignCloudStack/docs/blob/main/community/contribute/docs-workflow-explanation.md). +Here is an explanation on how the [sync & distill workflow works and a guide on how to test it in a local development environment](https://github.com/SovereignCloudStack/docs/blob/main/community/contribute/docs-workflow-explanation.md). ## 2. Operational documentation diff --git a/community/contribute/styleguides/ansible_styleguide.md b/community/contribute/styleguides/ansible_styleguide.md index 060be3851e..74bb4e4d46 100644 --- a/community/contribute/styleguides/ansible_styleguide.md +++ b/community/contribute/styleguides/ansible_styleguide.md @@ -15,7 +15,7 @@ disable the package_latest rule. ## Key Order -To check the key order we use our own rule. This can be found [here](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/files). +To check the key order we use [our own rule](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/files). ### Positioning and use of the become directive diff --git a/community/tools/zuul.md b/community/tools/zuul.md index f2abba96c5..93d289af88 100644 --- a/community/tools/zuul.md +++ b/community/tools/zuul.md @@ -10,14 +10,14 @@ use Zuul as our main pipeline solution. - Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul_deployment) - Create a file _.zuul.yaml_ - - An example can be found [here](https://github.com/SovereignCloudStack/zuul-sandbox/blob/main/.zuul.yaml) + - Here is [an example](https://github.com/SovereignCloudStack/zuul-sandbox/blob/main/.zuul.yaml) - You can have a job section containing _self-defined_ jobs which you need to write on your own - You have to have a project section containing - the default-branch name - the merge-mode which should be used to auto-merge - the jobs to run in each pipeline (gh_check, gh_gate, gh_post, gh_tag) - - these pipelines are triggered by events which can be looked up [here](https://github.com/SovereignCloudStack/zuul_config/blob/main/zuul.d/gh_pipelines.yaml) - - some default jobs can be found [here](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks) + - these [pipelines](https://github.com/SovereignCloudStack/zuul_config/blob/main/zuul.d/gh_pipelines.yaml) are triggered by events + - ihere are [some default jobs](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks) - If you have _self-defined_ jobs, you need to create a folder _.playbooks_ - this folder containers ansible playbooks which will be triggered From 98baba74e896af65951cf9dfe5d16784bba8231b Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 14:43:31 +0000 Subject: [PATCH 5/7] Fix links. Signed-off-by: Kurt Garloff --- blog/2026-01-22-introducing-docs-blog.md | 2 +- community/contribute/adding-docs-guide.md | 2 +- community/contribute/styleguides/ansible_styleguide.md | 2 +- community/tools/zuul.md | 8 +++++--- 4 files changed, 8 insertions(+), 6 deletions(-) diff --git a/blog/2026-01-22-introducing-docs-blog.md b/blog/2026-01-22-introducing-docs-blog.md index 7e21e22019..5419d65ed7 100644 --- a/blog/2026-01-22-introducing-docs-blog.md +++ b/blog/2026-01-22-introducing-docs-blog.md @@ -17,7 +17,7 @@ it was somewhat hard to distill the various aspects and goals of SCS though. With the end of the funded project, we split the activities into different organizations with distinct goals: -1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/network/) is +1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/) is responsible for governing the standardization process. While it pulls significant input from the various software projects that belong to the SCS ecosystem, it is neutral towards them beyond the preference for standards compliance. This reflects that there can and diff --git a/community/contribute/adding-docs-guide.md b/community/contribute/adding-docs-guide.md index 0dfe141991..2440bf463f 100644 --- a/community/contribute/adding-docs-guide.md +++ b/community/contribute/adding-docs-guide.md @@ -10,7 +10,7 @@ Determine the type of your documentation and click to continue. 2. [Operational documentation](#2-operational-documentation) 3. [Community documentation](#3-community-documentation) -If unsure don't hestitate to ask us at [Matrix](https://github.com/SovereignCloudStack/docs/blob/main/community/communication/matrix.md) +If unsure don't hestitate to ask us at [Matrix](https://docs.scs.community/community/tools/matrix) ## 1. Technical Documentation diff --git a/community/contribute/styleguides/ansible_styleguide.md b/community/contribute/styleguides/ansible_styleguide.md index 060be3851e..9730ea8385 100644 --- a/community/contribute/styleguides/ansible_styleguide.md +++ b/community/contribute/styleguides/ansible_styleguide.md @@ -15,7 +15,7 @@ disable the package_latest rule. ## Key Order -To check the key order we use our own rule. This can be found [here](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/files). +To check the key order we use our [own rule](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/). ### Positioning and use of the become directive diff --git a/community/tools/zuul.md b/community/tools/zuul.md index f2abba96c5..b49f9ef110 100644 --- a/community/tools/zuul.md +++ b/community/tools/zuul.md @@ -8,15 +8,17 @@ use Zuul as our main pipeline solution. ### How to make a repo use Zuul -- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul_deployment) +Note: This needs to be updated! + +- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul-scs-jobs) - Create a file _.zuul.yaml_ - - An example can be found [here](https://github.com/SovereignCloudStack/zuul-sandbox/blob/main/.zuul.yaml) + - An example can be found [here](https://github.com/SovereignCloudStack/zuul-config/) - You can have a job section containing _self-defined_ jobs which you need to write on your own - You have to have a project section containing - the default-branch name - the merge-mode which should be used to auto-merge - the jobs to run in each pipeline (gh_check, gh_gate, gh_post, gh_tag) - - these pipelines are triggered by events which can be looked up [here](https://github.com/SovereignCloudStack/zuul_config/blob/main/zuul.d/gh_pipelines.yaml) + - these pipelines are triggered by events which can be looked up [here](https://github.com/SovereignCloudStack/zuul-config/blob/main/zuul.d/) - some default jobs can be found [here](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks) - If you have _self-defined_ jobs, you need to create a folder _.playbooks_ - this folder containers ansible playbooks which will be triggered From 1b87d6166a7c9158aec7084b64df056a88a3ec53 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 14:43:31 +0000 Subject: [PATCH 6/7] Fix links. Signed-off-by: Kurt Garloff --- blog/2026-01-22-introducing-docs-blog.md | 2 +- community/contribute/adding-docs-guide.md | 2 +- community/contribute/styleguides/ansible_styleguide.md | 2 +- community/tools/zuul.md | 8 +++++--- 4 files changed, 8 insertions(+), 6 deletions(-) diff --git a/blog/2026-01-22-introducing-docs-blog.md b/blog/2026-01-22-introducing-docs-blog.md index 2df2e36e5e..ede9ae77dc 100644 --- a/blog/2026-01-22-introducing-docs-blog.md +++ b/blog/2026-01-22-introducing-docs-blog.md @@ -17,7 +17,7 @@ it was somewhat hard to distill the various aspects and goals of SCS though. With the end of the funded project, we split the activities into different organizations with distinct goals: -1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/network/) is +1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/) is responsible for governing the standardization process. While it pulls significant input from the various software projects that belong to the SCS ecosystem, it is neutral towards them beyond the preference for standards compliance. This reflects that there can and diff --git a/community/contribute/adding-docs-guide.md b/community/contribute/adding-docs-guide.md index 7e0c0a4ef1..93c6f69332 100644 --- a/community/contribute/adding-docs-guide.md +++ b/community/contribute/adding-docs-guide.md @@ -10,7 +10,7 @@ Determine the type of your documentation and click to continue. 2. [Operational documentation](#2-operational-documentation) 3. [Community documentation](#3-community-documentation) -If unsure don't hestitate to ask us at [Matrix](https://github.com/SovereignCloudStack/docs/blob/main/community/communication/matrix.md) +If unsure don't hestitate to ask us at [Matrix](https://docs.scs.community/community/tools/matrix) ## 1. Technical Documentation diff --git a/community/contribute/styleguides/ansible_styleguide.md b/community/contribute/styleguides/ansible_styleguide.md index 74bb4e4d46..9730ea8385 100644 --- a/community/contribute/styleguides/ansible_styleguide.md +++ b/community/contribute/styleguides/ansible_styleguide.md @@ -15,7 +15,7 @@ disable the package_latest rule. ## Key Order -To check the key order we use [our own rule](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/files). +To check the key order we use our [own rule](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/). ### Positioning and use of the become directive diff --git a/community/tools/zuul.md b/community/tools/zuul.md index 93d289af88..db7e2adfe5 100644 --- a/community/tools/zuul.md +++ b/community/tools/zuul.md @@ -8,15 +8,17 @@ use Zuul as our main pipeline solution. ### How to make a repo use Zuul -- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul_deployment) +Note: This needs to be updated! + +- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul-scs-jobs) - Create a file _.zuul.yaml_ - - Here is [an example](https://github.com/SovereignCloudStack/zuul-sandbox/blob/main/.zuul.yaml) + - Here is [an example](https://github.com/SovereignCloudStack/zuul-config/) - You can have a job section containing _self-defined_ jobs which you need to write on your own - You have to have a project section containing - the default-branch name - the merge-mode which should be used to auto-merge - the jobs to run in each pipeline (gh_check, gh_gate, gh_post, gh_tag) - - these [pipelines](https://github.com/SovereignCloudStack/zuul_config/blob/main/zuul.d/gh_pipelines.yaml) are triggered by events + - these [pipelines](https://github.com/SovereignCloudStack/zuul-config/blob/main/zuul.d/) are triggered by events - ihere are [some default jobs](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks) - If you have _self-defined_ jobs, you need to create a folder _.playbooks_ - this folder containers ansible playbooks which will be triggered From 8224caf313dd9e5523a543702a13957315bbc9e1 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Sat, 9 May 2026 14:49:14 +0000 Subject: [PATCH 7/7] One more link. Signed-off-by: Kurt Garloff --- community/contribute/adding-docs-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/contribute/adding-docs-guide.md b/community/contribute/adding-docs-guide.md index 93c6f69332..92cfac9025 100644 --- a/community/contribute/adding-docs-guide.md +++ b/community/contribute/adding-docs-guide.md @@ -68,6 +68,6 @@ File a Pull Request within the [docs](https://github.com/SovereignCloudStack/doc ## 3. Community documentation -Your doc files contain knowledge regarding our community? Choose the right directory. If unsure don't hestitate to ask us at [Matrix](https://github.com/SovereignCloudStack/docs/blob/main/community/communication/matrix.md). +Your doc files contain knowledge regarding our community? Choose the right directory. If unsure don't hestitate to ask us at [Matrix](https://docs.scs.community/community/tools/matrix). File a Pull Request within the `docs` repository and add your markdown files to the fitting directory.