Merge pull request #1450 from publiccodenet/fix-links-20240328T080652Z

Ainali · web-flow · commit eb2ee65b76f7 · 2024-03-28T09:25:14.000+01:00
Fix links 20240328 t080652 z
diff --git a/activities/communication/running-community-call.md b/activities/communication/running-community-call.md
@@ -38,7 +38,7 @@ Have each person join the call on a separate connection aligned with our [confer
 
 ## 1. Opening the call
 
-Call-in link: <https://meet.publiccode.net/FoundationCommunityCall>
+Call-in link: <https://meet.na.publiccode.net/FoundationCommunityCall>
 
 ### No show
 
diff --git a/activities/live-streaming/post-production.md b/activities/live-streaming/post-production.md
@@ -26,7 +26,7 @@ When doing post-production of a 'Let's talk about public code' [live stream](ind
 * Update stream destinations.
   * Fix the tense in the language of the description.
   * If possible, add the recording to a playlist.
-  * Optionally, add subtitles (can be created with [Whisper AI](https://github.com/openai/whisper)).
+  * Optionally, add subtitles (can be created with [Whisper AI](https://github.com/openai/whisper) and then checked for correctness).
 * Update Odoo by moving the card to the Produced column.
 * Send the guest a thank you email with request for feedback and links to the episode and blog post.
   * Connect them to a call to action such as [sign up for our tailored-to-your-preferences-newsletter](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842).
diff --git a/activities/releasing-the-standard/index.md b/activities/releasing-the-standard/index.md
@@ -27,5 +27,5 @@ Follow the [instructions](https://github.com/publiccodenet/standard/blob/develop
 * Bring up as news in the next [community call](../community-calls/index.md).
 * Send new printed standards to firesouls.
 * Offer to mail a printed copy to each new contributor.
-* Give guidance on how to update the [community translations of the standard](https://github.com/publiccodenet/community-translations-standard) by sending a link with the comparison of the latest tag and the tag of the current translation.
-* Update the [Community implementation guide](https://github.com/publiccodenet/community-implementation-guide-standard). The patch for the [assessment update](assessment-update.md) might be useful.
+* Give guidance on how to update the [community translations of the standard](https://github.com/standard-for-public-code/community-translations-standard) by sending a link with the comparison of the latest tag and the tag of the current translation.
+* Update the [Community implementation guide](https://github.com/standard-for-public-code/community-implementation-guide-standard). The patch for the [assessment update](assessment-update.md) might be useful.
diff --git a/activities/standard-maintenance/backlog-pruning.md b/activities/standard-maintenance/backlog-pruning.md
@@ -11,7 +11,7 @@ Over time, unresolved issues will gather in the repository.
 In order to not forget important ideas and to not become overwhelmed by a huge backlog, we dedicate time to look through our oldest issues to see if they have been resolved, become obsolete or can be addressed in other ways.
 
 This work is done during a backlog pruning session.
-The session is open for anyone to attend at [https://meet.publiccode.net/backlogpruning](https://meet.publiccode.net/backlogpruning).
+The session is open for anyone to attend at [https://meet.na.publiccode.net/backlogpruning](https://meet.na.publiccode.net/backlogpruning).
 We aim to hold sessions monthly on the second Thursday of the month, but may skip them if the schedule is too tight.
 
 ## Holding a backlog pruning session
diff --git a/activities/standard-maintenance/running-community-call.md b/activities/standard-maintenance/running-community-call.md
@@ -11,7 +11,7 @@ redirect_from:
 
 ## 1. Opening the call
 
-Call-in link: <https://meet.publiccode.net/StandardforPublicCode>
+Call-in link: <https://meet.na.publiccode.net/StandardforPublicCode>
 
 Agenda link: <https://write.publiccode.net/pads/Community-Call-Standard-for-Public-Code>
 
diff --git a/activities/tool-management/jitsi-meet.md b/activities/tool-management/jitsi-meet.md
@@ -7,6 +7,9 @@ type: resource
 # Jitsi Meet
 
 Jitsi Meet is our videocall and conference tool.
+
+The information on this page does not cover meet.na.publiccode.net instance, but rather the former meet.publiccode.net instance.
+
 Jitsi is an open source project that allows us to deploy secure video conferencing solutions.
 At the heart of Jitsi are Jitsi Videobridge and Jitsi Meet, which lets us have conferences on the internet, while other projects in the community enable other features such as audio, dial-in, recording, and simulcasting.
 
diff --git a/activities/tool-management/tool-and-email-naming-conventions.md b/activities/tool-management/tool-and-email-naming-conventions.md
@@ -45,7 +45,7 @@ These tools have their own URL and associated email:
 * client relationship management: odoo.publiccode.net (Odoo)
 * internal chat: chat.publiccode.net (Mattermost)
 * file sharing: collaboration.publiccode.net (Nextcloud)
-* video calling: meet.publiccode.net (Jitsi)
+* video calling: meet.na.publiccode.net (Jitsi)
 
 ## Email address uses and formatting
 
diff --git a/organization/annual-reports/annual-report-2021.md b/organization/annual-reports/annual-report-2021.md
@@ -81,7 +81,7 @@ As a public benefit organization and with the [KBFUS Public Code US fund](https:
 
 ### The Standard for Public Code
 
-In 2021, the Standard continued to prove its value to public code communities. Developers from three codebases worked with Foundation for Public Code stewards to evaluate their codebases with the Standard. Additionally, the stewards  discussed the self evaluations performed by developers of two other codebases. Responding to community requests, we established a [process for unofficial community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/README.html) into other languages. It is already [translated into Spanish](https://publiccodenet.github.io/community-translations-standard/es/).
+In 2021, the Standard continued to prove its value to public code communities. Developers from three codebases worked with Foundation for Public Code stewards to evaluate their codebases with the Standard. Additionally, the stewards  discussed the self evaluations performed by developers of two other codebases. Responding to community requests, we established a [process for unofficial community translations of the Standard](https://standard-for-public-code.github.io/community-translations-standard/README.html) into other languages. It is already [translated into Spanish](https://standard-for-public-code.github.io/community-translations-standard/es/).
 
 In July, the Standard for Public Code was recognized as a [Digital Public Goods](https://digitalpublicgoods.net/) by the Digital Public Goods Alliance, a multi-stakeholder initiative endorsed by the United Nations Secretary-General’s Roadmap for Digital Cooperation.
 
@@ -107,7 +107,7 @@ In October, we started working with Matthew Claudel to explore open source softw
 
 ### Codebase stewardship
 
-In 2021, we had 2 codebases in Incubation ([Signalen](https://publiccode.net/codebases/signalen.html) and [OpenZaak](https://publiccode.net/codebases/openzaak.html)) and one in Assessment ([Digital Omgevingsbeleid](https://publiccode.net/codebases/omgevingsbeleid.html)). We also worked closely with [Demodam](https://demodam.org/en/).
+In 2021, we had 2 codebases in Incubation ([Signalen](https://publiccode.net/codebases/signalen.html) and [OpenZaak](https://publiccode.net/codebases/openzaak.html)) and one in Assessment ([Digital Omgevingsbeleid](https://publiccode.net/codebases/omgevingsbeleid.html)). We also worked closely with [Demodam](https://web.archive.org/web/20231204123513/https://demodam.org/en/).
 
 #### Signalen
 
diff --git a/organization/annual-reports/annual-report-2022.md b/organization/annual-reports/annual-report-2022.md
@@ -62,7 +62,7 @@ In 2022, we:
 
 * [launched a community-built implementation guide](https://blog.publiccode.net/news/2022/09/13/launching-community-built-implementation-guide.html)
 * released 4 iterations, going from version 0.2.3 to 0.4.1 - including adding a new findability criterion and clarifying that policy doesn’t need to be fully translated to English, both based on community feedback
-* launched [a home for community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/)
+* launched [a home for community translations of the Standard](https://standard-for-public-code.github.io/community-translations-standard/)
 * launched a simple [assessment eligibility tool](https://publiccodenet.github.io/assessment-eligibility)
 * had 3 new contributors
 
