Merge pull request #499 from publiccodenet/linkfix-20240328T072334Z

Linkfix 20240328 072334

_posts/2020-06-22-notes-from-community-call-3-june-2020.md

@@ -50,7 +50,7 @@ If that urge decreases, it is a good sign of maturity. So observing our own reac
 Another way would be to talk with people in our community that are using the Standard. The best way to do this would probably be long form qualitative interviews to tease this out.
 
 To push the Standard towards maturity, we discussed the idea of doing more quick iterations.
-This could possibly build on the idea of a shorter version questionnaire, like the one we had planned for a drop-in session at the March 2020 [SCORE developer week in Ghent](https://score.community/t/score-developer-sprint-week-in-ghent-2020/806/22).
+This could possibly build on the idea of a shorter version questionnaire, like the one we had planned for a drop-in session at the March 2020 [SCORE developer week in Ghent](https://score.community/t/score-developer-sprint-week-in-ghent-2020/806/).
 
 As a side track we discussed the template we used for the analysis, since it was when using it that we felt the need for deep links.
 Jan expressed that what was hard sometimes was to keep the context of each requirement in mind. Elena showed [an example of expandable requirements](https://www.gov.uk/service-manual/service-standard/point-6-have-a-multidisciplinary-team) from the UK.

_posts/2021-04-08-March-2021-newsletter.md

@@ -72,7 +72,7 @@ We also ran sessions at Mozilla Festival on [how public code can transform the f
 
 We'd love to see you at our monthly community calls:
 
-* [Standard for Public Code call](https://hackmd.io/-OegeqvoThCbAsw3c3gIjw), 1st Thursday of the month, 15.00 CEST
-* [Foundation for Public Code call](https://hackmd.io/9THmWbpQTLi8L9UIzczSyw), 3rd Thursday of the month, 15.00 CEST
+* Standard for Public Code call, 1st Thursday of the month, 15.00 CEST
+* Foundation for Public Code call, 3rd Thursday of the month, 15.00 CEST
 
 The topic is published the week before the call.

_posts/2021-06-30-join-demodam-hackathon.md

@@ -30,4 +30,4 @@ The Demodam website is currently under development, so meet the community by:
 - Following their [LinkedIn updates](https://www.linkedin.com/company/demodam)
 - Suscribing to their [mailing list](https://lists.publiccode.net/mailman/postorius/lists/demodam-discuss.lists.publiccode.net/)
 
-You can find more information about Demodam in [this blogpost by Edo Plantinga](https://commonground.nl/blog/view/6c422c0a-e541-41c8-8261-9c8bc90f4d87/doe-mee-met-demodam-de-common-ground-showcase-website) and on [Demodam.org](https://demodam.org)
+You can find more information about Demodam in [this blogpost by Edo Plantinga](https://commonground.nl/blog/view/6c422c0a-e541-41c8-8261-9c8bc90f4d87/doe-mee-met-demodam-de-common-ground-showcase-website) and on [Demodam.org](https://web.archive.org/web/20231204123513/https://demodam.org/).

_posts/2021-11-09-notes-from-community-call-4-november-2021.md

@@ -21,7 +21,7 @@ categories:
 * We have [launched a strategic council]({% post_url 2021-09-13-launching-our-strategic-council %})
 * Dan Hill is [joining us in our strategic council](https://about.publiccode.net/organization/strategic-council.html)
 * Signalen is [live in a third municipality](https://meldingen.alphenaandenrijn.nl/)
-* We will start hosting (unofficial) [community translations](https://github.com/publiccodenet/community-translations-standard) of the Standard for Public Code
+* We will start hosting (unofficial) [community translations](https://github.com/standard-for-public-code/community-translations-standard) of the Standard for Public Code
 
 ## Glossary
 

_posts/2021-12-13-notes-from-community-call-2-december-2021.md

@@ -46,4 +46,4 @@ While talking, we also identified a need of expanding the value of this under th
 
 ### Community translations
 
-We briefly informed about the new [community translations for the Standard for public Code](https://github.com/publiccodenet/community-translations-standard).
+We briefly informed about the new [community translations for the Standard for public Code](https://github.com/standard-for-public-code/community-translations-standard).

_posts/2022-01-27-goals-for-the-first-quarter-2022.md

@@ -115,4 +115,4 @@ Professionalize an exemplary open public organization
 | | **ASAP**: Get general assembly to validate policy plan |
 | | **ASAP**: Follow-up with members |
 | | Before 1 July: Create annual report |
-| | Establish publishing process for [Standard community translations](https://github.com/publiccodenet/community-translations-standard) |
+| | Establish publishing process for [Standard community translations](https://github.com/standard-for-public-code/community-translations-standard) |

_posts/2022-02-03-notes-from-community-call-3-february-2022.md

@@ -18,7 +18,7 @@ categories:
 ## Updates from the Foundation
 
 * FOSDEM is this weekend, [check out the schedule](https://fosdem.org/2022/schedule/room/dpublic_code/)
-* We have published the [community translations of the Standard for Public Code](https://publiccodenet.github.io/community-translations-standard/)
+* We have published the [community translations of the Standard for Public Code](https://standard-for-public-code.github.io/community-translations-standard/)
 
 ## Notes
 

_posts/2022-09-02-notes-from-community-call-1-september-2022.md

@@ -19,7 +19,7 @@ categories:
 
 ## Updates from the Foundation
 
-* The [Implementation guide for the Standard for Public Code](https://publiccodenet.github.io/community-implementation-guide-standard/) is now live - please add to it!
+* The [Implementation guide for the Standard for Public Code](https://standard-for-public-code.github.io/community-implementation-guide-standard/) is now live - please add to it!
 
 ## Notes
 

_posts/2022-09-08-pruning-the-oldest-issues.md

@@ -32,4 +32,4 @@ Then we continued with:
 * [Add further reading for Ethics considerations #357](https://github.com/publiccodenet/standard/issues/357) - transferred to the implementation guide repository
 * [Add how the Standard supports the SDGs to the intro #358](https://github.com/publiccodenet/standard/issues/358) - commented about usability in the publiccode.net repository, made a [pull request](https://github.com/publiccodenet/standard/pull/695) for partial solution, stays open
 
-Last, we reviewed the [roadmap](https://standard.publiccode.net/docs/roadmap.html) and [proposed a small update](https://github.com/publiccodenet/standard/pull/696) that adjusts it to be inline with the [latest release](https://github.com/publiccodenet/standard/releases/tag/0.4.0) and the [implementation guide](https://publiccodenet.github.io/community-implementation-guide-standard/).
+Last, we reviewed the [roadmap](https://standard.publiccode.net/docs/roadmap.html) and [proposed a small update](https://github.com/publiccodenet/standard/pull/696) that adjusts it to be inline with the [latest release](https://github.com/publiccodenet/standard/releases/tag/0.4.0) and the [implementation guide](https://standard-for-public-code.github.io/community-implementation-guide-standard/).

_posts/2022-09-13-launching-community-built-implementation-guide.md

@@ -25,7 +25,7 @@ What we are launching now is a standalone guide, in which examples, methods, tem
 As we are keeping it separate, we can add as many resources we feel are relevant without affecting the standard's readability.
 This should make it easier to use the standard as a reference when auditing a codebase, and allows the guide to be full of alternatives when thinking about how a codebase could meet a certain requirement.
 
-The guide can be found at [publiccodenet.github.io/community-implementation-guide-standard/](https://publiccodenet.github.io/community-implementation-guide-standard/).
+The guide can be found at [standard-for-public-code.github.io/community-implementation-guide-standard/](https://standard-for-public-code.github.io/community-implementation-guide-standard/).
 
 Everything you can find in the guide could be considered to be “pre-approved”.
 By that, we mean that if you are using the guide in good faith to meet a requirement, you should be confident that the codebase would pass when assessed by the Foundation for Public Code.
@@ -44,5 +44,5 @@ Some existing examples and further reading in the standard have been moved to th
 But we know there is much more knowledge in the public code community.
 
 Please help us to add resources and examples that can help others to implement the Standard for Public Code.
-Start a [pull request](https://github.com/publiccodenet/community-implementation-guide-standard#contribute) yourself, or explain what you want added in a [new issue](https://github.com/publiccodenet/community-implementation-guide-standard/issues/new/choose).
+Start a [pull request](https://github.com/standard-for-public-code/community-implementation-guide-standard#contribute) yourself, or explain what you want added in a [new issue](https://github.com/standard-for-public-code/community-implementation-guide-standard/issues/new/choose).
 If you feel more at home with email than GitHub, you can also [sign up to our Standard for Public Code mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/) and make your suggestions there.

_posts/2023-05-08-notes-from-community-call-4-may-2023.md

@@ -21,7 +21,7 @@ categories:
 ## Updates from the Foundation
 
 * New release of the Standard for Public Code: [version 0.6.0](https://github.com/publiccodenet/standard/releases/tag/0.6.0).
-* We have made [a bootstrap script](https://github.com/publiccodenet/community-translations-standard#contribute) that makes starting a community translation of the Standard less tedious.
+* We have made [a bootstrap script](https://github.com/standard-for-public-code/community-translations-standard#contribute) that makes starting a community translation of the Standard less tedious.
 
 ## Notes
 

_posts/2023-08-07-notes-from-community-call-3-august-2023.md

@@ -43,4 +43,4 @@ When it comes to long-term archiving, we haven't learned from any codebases exac
 Therefore, we should try to reach out to them and learn about what they do.
 
 We also discussed if this should be an entire criterion or be added as requirements in existing ones like Make your codebase findable or Make the codebase reusable and portable, but it depends on what we learn.
-What we will do right now is to add some guidance in the [Community implementation guide](https://publiccodenet.github.io/community-implementation-guide-standard/) under Bundle policy and code that there might be laws about this and that the community should describe what their process is for abiding by them.
+What we will do right now is to add some guidance in the [Community implementation guide](https://standard-for-public-code.github.io/community-implementation-guide-standard/) under Bundle policy and code that there might be laws about this and that the community should describe what their process is for abiding by them.

_posts/2024-03-27-notes-from-community-call-26-march-2024.md

@@ -56,7 +56,7 @@ The OSPO alliance kindly offered to provide infrastructure for the continued wor
 Luckily, the existing infrastructure will continue to exist, so there is no urgent need of that to date.
 
 Besides the governance question, it was expressed that continued knowledge sharing between users of the Standard is important.
-Partly, the [Community built companion](https://publiccodenet.github.io/community-implementation-guide-standard/) can solve this already, by being a place to share good ways of implementing the Standard for Public Code.
+Partly, the [Community built companion](https://standard-for-public-code.github.io/community-implementation-guide-standard/) can solve this already, by being a place to share good ways of implementing the Standard for Public Code.
 Similarly, a wish for the community to help disseminating the Standard for Public Code and showing good examples was expressed.
 Also there the Community built companion could be a solution, not to mention the [list of codebases that are compliant](https://standard-compliant.publiccode.net/).
 For the rest, using [the mailing list](https://lists.publiccode.net/mailman/postorius/lists/standard.lists.publiccode.net/) to share knowledge and examples might be a good start.