Merge pull request #1444 from publiccodenet/20240306-release

20240306 release

CONTRIBUTING.md

@@ -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
 

activities/codebase-auditing/auditing-process.md

@@ -6,17 +6,26 @@ type: Resource
 
 # The auditing process
 
+Initially, codebase stewards schedule time with codebase maintainers in order to review each requirement of each criterion relative to the codebase.
+For each requirement, the stewards and the maintainers come to a shared understanding of what the current state is as well as what changes, if any, should be made to bring the codebase closer to compliance with the requirement.
+
+As a help to review a codebase, [this template](https://github.com/publiccodenet/standard/blob/develop/docs/review-template.html) can be used.
+
+By recording the current state, and taking notes including links to supporting documentation in the template, progress can be tracked over time.
+
+Assessments are typically added to the codebase repository, which allows others to verify or challenge the evaluation.
+
+The initial assessments can usually be performed with two to three sessions of two to three hours each for the maintainers and the stewards.
+
+## Continuous auditing
+
 The audit happens completely in the version control platform and is designed to fit in to a regular agile software development process.
 When a contribution is presented for inclusion in the codebase, a Foundation for Public Code staff auditor familiar with the codebase will provide a review or certify the contribution.
 
 The review or certification will happen within 2 business days to enable agile development and not block users and maintainers from making progress.
 
 The codebase maintainers will be notified when a contribution passes the audit and is certified.
 
-## Template
-
-As a help to review a codebase, [this template](https://github.com/publiccodenet/standard/blob/develop/docs/review-template.html) can be used.
-
 ## List of assessments
 
 For any codebase where there is not yet an explicit agreement to publish an assessment, or one in progress, add the link to the assessment to [this spreadsheet](https://docs.google.com/spreadsheets/d/1wUrlZ73S-4BK3sGz87C28d0ReYELCCP4MZnKpB0UKqM/edit#gid=2105222073) (only accessible for staff).

activities/communication/community-call-invite-template.md

@@ -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!

activities/communication/running-community-call.md

@@ -17,10 +17,10 @@ The roles on the community call are:
 
 The chair and the notetaker:
 
-* create a notes HackMD.io document for this call
+* create a notes document for this call
 * add "updates since the last community call" to the notes - keep this to three items or fewer (we want the community call to be a dialogue, not a broadcast). If possible, focus on community related updates
 * put these in the call notes doc
-* update the [agenda](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw?edit)
+* update the agenda and link it
 * send out invitations ([template](community-call-invite-template.md))
 
 Ask the [communications coordinator](../../organization/staff.md#communications) if you need help with Foundation updates.
@@ -40,8 +40,6 @@ Have each person join the call on a separate connection aligned with our [confer
 
 Call-in link: <https://meet.publiccode.net/FoundationCommunityCall>
 
-Agenda link: <https://hackmd.io/9THmWbpQTLi8L9UIzczSyw>
-
 ### No show
 
 If nobody joins at the call starting time, wait at least 15 minutes before closing the call.

activities/creating-partnerships/index.md

@@ -14,7 +14,7 @@ redirect _from:
 
 The Foundation for Public Code is actively looking for diverse public organizations to collaborate with.
 
-[See our current partnerships](../../organization/partnerships.md).
+[See our current partners](../../organization/partners.md).
 
 Only public organizations can become partners.
 Other organizations can become [affiliates](../creating-affiliations/index.md)

activities/trainings/index.md

@@ -15,7 +15,6 @@ Here is a list of trainings developed or used by the Foundation for Public Code:
 * Rewriting Git History - Amend, Reword, Delete, Reorder, Squash and Split ([video](https://www.youtube.com/watch?v=ElRzTuYln0M), [article](https://www.themoderncoder.com/rewriting-git-history/)) - for making the git history as clear and understandable as possible
 * [Git Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf) - for a list of the most common used git commands
 * [Reviewing contributions](https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/)
-* [HackMD.io](https://hackmd.io/) - for collaborating on draft documents in Markdown with people outside the organization (especially helpful for content we plan to publish)
 * [Markdown Here](https://markdown-here.com/) - for formatting emails written using Markdown
 * [Jekyll tutorial](https://jekyllrb.com/docs/step-by-step/01-setup/) - for understanding the templates which underpin our website
 

organization/affiliates.md

@@ -6,7 +6,7 @@ type: resource
 
 # Affiliates
 
-The Foundation for Public Code is a member-owned association that exists in an ecosystem of affiliates and [partners](partnerships.md).
+The Foundation for Public Code is a member-owned association that exists in an ecosystem of affiliates and [partners](partners.md).
 Affiliates are non-profit organizations whose work aligns with ours and that help us to [achieve our mission](mission.md).
 The Foundation for Public Code does not do work to benefit affiliates unless that work is for the direct benefit of public organizations.
 Read more about [becoming an affiliate](../activities/creating-affiliations/index.md).

organization/index.md

@@ -15,8 +15,8 @@ Read more about [our mission, founding principles and current priorities](missio
 This is how we're building the organization to support our mission:
 
 * [Strategic council](strategic-council.md)
-* [Partnerships](partnerships.md)
 * [Affiliates](affiliates.md)
+* [Partners](partners.md)
 * [Governance model](governance-model.md)
 * [Financial model](financial-model.md)
 * [Articles of association](articles-of-association.md) with translations in [Spanish (Español)](articles-of-association.es.md) and [Dutch (Nederlands)](articles-of-association.nl.md)

organization/partnerships.md → organization/partners.md

@@ -2,9 +2,11 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2021-2024 The Foundation for Public Code <info@publiccode.net>
 type: resource
+redirect_from:
+    - partnerships
 ---
 
-# Partnerships
+# Partners
 
 The Foundation for Public Code is a member-owned association that exists in an ecosystem of partners and [affiliates](affiliates.md).
 Our partners are integral to our ability to [achieve our mission](mission.md).