Merge branch 'develop' into draft-policy-plan-2024

publiccodenet · Mar 5, 2024 · 33c0bbe · 33c0bbe
2 parents ad252b1 + 9764da1
commit 33c0bbe
Show file tree

Hide file tree

Showing 287 changed files with 366 additions and 333 deletions.
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -1,4 +1,4 @@
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 # Only directors of the Foundation for Public Code are allowed to approve releases.
 *       @publiccodenet/directors
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
@@ -1,5 +1,5 @@
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 name: Test
 on:
   - push
@@ -13,7 +13,7 @@ jobs:
   cibuild:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - uses: ruby/setup-ruby@v1
         with:
           ruby-version: '2.7'

diff --git a/.gitignore b/.gitignore
@@ -1,5 +1,5 @@
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 
 Gemfile.lock
 _site

diff --git a/404.md b/404.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2022-2024 The Foundation for Public Code <info@publiccode.net>
 layout: default
 title: Page not found
 toc: false

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 type: Guide
 explains: ways in which people and organizations can contribute to the Foundation for Public Code
 ---
@@ -29,7 +29,7 @@ We’re especially interested in learning what you need to implement the [Standa
 
 ## Public organizations
 
-We’re looking for public partners to help shape the Foundation for Public Code’s long term future. Find out more about the [benefits and requirements of becoming a partner](organization/partnerships.md) and get in touch with us at <partnerships@publiccode.net>.
+We’re looking for public partners to help shape the Foundation for Public Code’s long term future. Find out more about the [benefits and requirements of becoming a partner](organization/partners.md) and get in touch with us at <partnerships@publiccode.net>.
 
 ## Institutional giving and philanthropy
 

diff --git a/GOVERNANCE.md b/GOVERNANCE.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/README.md b/README.md
@@ -1,7 +1,7 @@
 # About the Foundation for Public Code
 
 <!-- SPDX-License-Identifier: CC0-1.0 -->
-<!-- SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net> -->
+<!-- SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net> -->
 
 We help open source projects for public organizations to become successful, build sustainable communities around them and create a thriving public open source ecosystem.
 
@@ -51,8 +51,7 @@ If run with `./script/test.sh --all`, then it also includes
 
 * `./script/test-with-link-check.sh` which uses `html-proofer` to verify that all of the external links, even ones not related to the patch, are valid; a failure of this test may not be related to your work
 
-The `test-with-link-check.sh` is [scheduled to run daily](https://github.com/publiccodenet/about/blob/develop/.github/workflows/link-check.yml).
-This helps the maintainers identify links which have gone stale.
+The `test-with-link-check.sh` helps the maintainers identify links which have gone stale.
 
 ## License
 

diff --git a/_config.yml b/_config.yml
@@ -1,5 +1,5 @@
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 title: About the Foundation for Public Code
 permalinks: pretty
 

diff --git a/activities/board-support/board-meeting-process.md b/activities/board-support/board-meeting-process.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---
 

diff --git a/activities/board-support/index.md b/activities/board-support/index.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: index
 ---
 

diff --git a/activities/codebase-auditing/auditing-process.md b/activities/codebase-auditing/auditing-process.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-auditing/certification.md b/activities/codebase-auditing/certification.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-auditing/index.md b/activities/codebase-auditing/index.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 type: Index
 ---
 

diff --git a/activities/codebase-auditing/open-audits.md b/activities/codebase-auditing/open-audits.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2022-2024 The Foundation for Public Code <info@publiccode.net>
 type: Guide
 explains: how we do audits in the open
 ---
@@ -15,12 +15,21 @@ As much as possible, audits should take place in the open and be done together w
 
 ## Steps
 
-1. Get explicit approval to start an open audit by asking the maintainer. Consider communicating that audit is starting, preferrably by encouraging the maintainer to do it, and possibly on [the blog](https://blog.publiccode.net) as well.
+1. Get explicit approval to start an open audit by asking the maintainer. Consider communicating that audit is starting, preferably by encouraging the maintainer to do it, and possibly on [the blog](https://blog.publiccode.net) as well.
 2. Create an issue in the repository for the codebase using the [review template](https://github.com/publiccodenet/standard/blob/develop/docs/review-template.html).
-3. Start auditing the codebase in collaboration with the community. Preferrably, this involves more than one key contributor from the community and more than one codebase steward working together.
-4. If the audit makes discoveries that can be addresses, create issues for those in the repository for the codebase, preferrably by encouraging the maintainer to do so.
+3. Start auditing the codebase in collaboration with the community. Preferably, this involves more than one key contributor from the community and more than one codebase steward working together.
+4. If the audit makes discoveries that can be addresses, create issues for those in the repository for the codebase, preferably by encouraging the maintainer to do so.
 5. If many issues get created, ask to setup a Kanban in the repository for the audit with the columns Backlog, In progress, Done.
 
+### Codebases which span two or more repositories
+
+Sometimes, for instance in the case of Omgevingsbeleid, there are multiple repositories that makeup the software.
+In these cases, we separately evaluate each repository, with the understanding that some requirements are not applicable to one or another.
+Once each repository has been assessed, we can do an assessment of the whole stack, paying careful attention to whether or not there are any requirements which are not fulfilled by any repository.
+So far, the developers of the different repositories have been known to each other and thus it has been easy to gain a shared understanding of which repository is responsible for various aspects when they are divided.
+As an example, the documentation requirements of a feature may have different expectations in the front-end repository, back-end repository, and documentation repository.
+Naturally, careful note-taking and reference-documenting in the assessment templates is even more important in these cases.
+
 ## Audits
 
 Public assessments are linked from each codebase on [standard-compliant](https://standard-compliant.publiccode.net/#public-commitment) and if appropriate on our [page for codebases in stewardship](https://publiccode.net/codebases/).
diff --git a/activities/codebase-stewardship/community-assets.md b/activities/codebase-stewardship/community-assets.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---
 

diff --git a/activities/codebase-stewardship/for-existing-projects.md b/activities/codebase-stewardship/for-existing-projects.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/goals.md b/activities/codebase-stewardship/goals.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/index.md b/activities/codebase-stewardship/index.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2018-2024 The Foundation for Public Code <info@publiccode.net>
 type: Index
 redirect_from:
     - activities/codebase-stewardship/activities
@@ -91,6 +91,6 @@ It is useful even as a handbook when trying to guide a community through any sit
 ### Templates
 
 * [Standard for Public Code auditing template](https://github.com/publiccodenet/standard/blob/develop/docs/review-template.html) - this is the template we use when auditing a codebase towards the Standard for Public Code
-* [User personas templates](/user-personas/index.md) - template personas that are typical in the type of codebases we work with that can be used as a starting point
+* [User personas templates](user-personas/index.md) - template personas that are typical in the type of codebases we work with that can be used as a starting point
 * [Codebase in Odoo](odoo-codebase-template.md) - template to use when we add a new codebase in Odoo
 * [Stewardship proposal](stewardship-proposal-template.md) - a template proposal we can send to principal maintainers to get informed consent to steward the codebase
diff --git a/activities/codebase-stewardship/lifecycle-diagram.md b/activities/codebase-stewardship/lifecycle-diagram.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2022-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 bpmn: lifecycle.bpmn
 redirect_from:

diff --git a/activities/codebase-stewardship/odoo-codebase-template.md b/activities/codebase-stewardship/odoo-codebase-template.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/odoo-codebases.md b/activities/codebase-stewardship/odoo-codebases.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Guide
 explains: How we use Odoo for keeping track of the codebases we work with
 ---

diff --git a/activities/codebase-stewardship/product-assets-for-early-incubation.md b/activities/codebase-stewardship/product-assets-for-early-incubation.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---
 

diff --git a/activities/codebase-stewardship/reviewing-codebase-incubation-progress.md b/activities/codebase-stewardship/reviewing-codebase-incubation-progress.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2022-2024 The Foundation for Public Code <info@publiccode.net>
 type: guide
 explains: how we review the progress of a codebase in incubation
 ---

diff --git a/activities/codebase-stewardship/stewardship-proposal-template.md b/activities/codebase-stewardship/stewardship-proposal-template.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/user-personas/communications-manager.md b/activities/codebase-stewardship/user-personas/communications-manager.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/user-personas/index.md b/activities/codebase-stewardship/user-personas/index.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Index
 ---
 

diff --git a/activities/codebase-stewardship/user-personas/policy-maker-officer.md b/activities/codebase-stewardship/user-personas/policy-maker-officer.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/user-personas/project-manager-association.md b/activities/codebase-stewardship/user-personas/project-manager-association.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/user-personas/project-manager-municipality.md b/activities/codebase-stewardship/user-personas/project-manager-municipality.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/codebase-stewardship/user-personas/vendor-owner-developer.md b/activities/codebase-stewardship/user-personas/vendor-owner-developer.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/communication/adding-a-phone-user.md b/activities/communication/adding-a-phone-user.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Guide
 explains: How to add a user to the Voys phone infrastructure and connect them to a phone number
 ---

diff --git a/activities/communication/basic-tweet-template.md b/activities/communication/basic-tweet-template.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---
 

diff --git a/activities/communication/blogging.md b/activities/communication/blogging.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 Type: guide
 Explains: how to blog
 ---

diff --git a/activities/communication/communication-principles.md b/activities/communication/communication-principles.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/communication/communication-remote-first.md b/activities/communication/communication-remote-first.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2021-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/communication/communications-plan.md b/activities/communication/communications-plan.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---
 

diff --git a/activities/communication/community-call-invite-template.md b/activities/communication/community-call-invite-template.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2019-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 
@@ -24,7 +24,9 @@ If participants can benefit of preparing, mention it as well.]
 
 If you have something else you would like to discuss please let us know, we are happy to make modifications to the agenda.
 
-[Read the full agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?view).
+```
+[Read the full agenda](INSERT LINK).
+```
 
 We look forward to seeing you on the call!
 
@@ -34,6 +36,4 @@ Our next Foundation for Public Code community call will take place at hh.mm on W
 
 If you have something specific you would like to discuss please let us know, we are happy to add items to the agenda.
 
-[Read the full agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?view).
-
 We look forward to seeing you on the call!
diff --git a/activities/communication/community-call.md b/activities/communication/community-call.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: Resource
 ---
 

diff --git a/activities/communication/conference-call-etiquette.md b/activities/communication/conference-call-etiquette.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---
 

diff --git a/activities/communication/email-signature-template.md b/activities/communication/email-signature-template.md
@@ -1,6 +1,6 @@
 ---
 # SPDX-License-Identifier: CC0-1.0
-# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <info@publiccode.net>
+# SPDX-FileCopyrightText: 2020-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
 ---