Merge pull request #1421 from publiccodenet/release-20231213

Release 20231213

activities/financial-administration/bank.md

@@ -18,3 +18,7 @@ These people have bank access:
 * The chief executive has a debit card (wereldpas) and credit card
 * The operations coordinator is authorized to make € 5000 payments without a co-sign
 * The chief executive’s daily limit is € 50,000 and can be temporarily raised if needed by calling the bank
+
+## Bank account number
+
+Our bank account number (IBAN) is NL78 RABO 0342 6453 31 (BIC/SWIFT: RABONL2U).

activities/grant-applications/index.md

@@ -0,0 +1,14 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2023 The Foundation for Public Code <[email protected]>
+type: Index
+---
+
+# Institutional fundraising and grant applications
+
+Our [financial model](../../organization/financial-model.md) includes applying for structural funding and grants from institutions.
+
+## European Commission funding information
+
+Our European Commission Participant Identification Code (PIC) number is: 879731122.
+Jan Ainali and Elena Findley-de Regt are [registered for PIC administration](https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/home).

activities/index.md

@@ -24,6 +24,7 @@ Activities that support the above as well as make staff operations work:
 * [Events](events/index.md)
 * [Explaining codebase stewardship](explaining-codebase-stewardship/index.md)
 * [Financial administration](financial-administration/index.md)
+* [Institutional fundraising and grant applications](grant-applications/index.md)
 * [Live streaming and podcasting](live-streaming/index.md)
 * [Maintenance of the Standard for Public Code](standard-maintenance/index.md)
 * [Office management](office-management/index.md)

activities/live-streaming/manage-live-stream.md

@@ -23,6 +23,7 @@ When running a [live stream](index.md) of 'Let's talk about  public code' there
 12. The last question we always ask our guest is "Please name someone you think we should interview in our upcoming episodes, and explain why?"
 13. Remind the audience at the end of ways of keeping in touch with us.
 14. When the show is over start the outro video and quickly press Stop recording.
+15. Make sure that the guests stay in Streamyard until their audio has uploaded, or if they have to leave quickly, ask them to go to [streamyard.com/upload](https://streamyard.com/upload) later to finish uploading.
 
 ## See also
 

activities/live-streaming/post-production.md

@@ -11,6 +11,7 @@ When doing post-production of a 'Let's talk about public code' [live stream](ind
 
 * Attendee and viewer follow up: 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).
 * Create an audio version of the podcast.
+  * Download the audio files from Streamyard, either using the direct link when ending the stream, or by finding them in the "Library" later.
   * Use the [Audacity project template](https://files.publiccode.net/nextcloud/index.php/s/aEoGGTNbJzw6iGx) to get started.
   * Cut out long pauses, coughs and other noise, but try to keep the content similar to the recording.
   * Compress and normalize.

activities/live-streaming/prepare-live-stream.md

@@ -28,6 +28,7 @@ When setting up a new [live stream](index.md) for 'Let's talk about public code'
 3. In the week before the stream, create a new broadcast in [StreamYard](../tool-management/streamyard.md)
 4. Upload the new intro video in Streamyard and remove the old one to avoid confusion during the stream
 5. Update banners with links related to the upcoming show
+6. When entering the podcast studio, make sure the settings under Recording are set to Record locally for each participant - Record audio only
 
 ## Communication
 

glossary/general-public-definition.md

@@ -1,5 +1,9 @@
-<!-- SPDX-License-Identifier: CC0-1.0 -->
-<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]> -->
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]>
+type: Resource
+---
+
 # General public
 
 The public at large: end users of code and the services based upon it.

glossary/index.md

@@ -6,7 +6,11 @@ redirect_from:
     - /glossary/public-member-definition
 ---
 
-# Glossary terms
+# Glossary
+
+The glossary serves to standardise the meaning of commonly used words and concepts in our communications.
+
+## Glossary terms
 
 For the terms below we believe it is important that we have a clear definition of their meaning.
 If we use one of the following terms in any of our communications they will mean their definition in this glossary.
@@ -28,3 +32,11 @@ If we use one of the following terms in any of our communications they will mean
 * [Resource](resource-definition.md)
 * [Staff](staff-definition.md)
 * [User](user-definition.md)
+
+## Requesting of adding a new term
+
+If there is a term you are unsure about or you think should be in the glossary, please [create an issue](https://github.com/publiccodenet/about/issues).
+
+If you want to add a term, please follow the steps set out in the [contributing guide](../CONTRIBUTING.md) and make a pull request.
+Please add the term in the correct alphabetical order.
+For example: `* [Public code](publiccode.md)` between Public administration and Public sector.

glossary/open-source-definition.md

@@ -1,5 +1,9 @@
-<!-- SPDX-License-Identifier: CC0-1.0 -->
-<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]> -->
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <[email protected]>
+type: Resource
+---
+
 # Open source
 
 Open source is defined by the Open Source Initiative in their [Open Source Definition](https://opensource.org/osd-annotated).

glossary/open-standard-definition.md

@@ -1,5 +1,9 @@
-<!-- SPDX-License-Identifier: CC0-1.0 -->
-<!-- SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]> -->
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2020-2023 The Foundation for Public Code <[email protected]>
+type: Resource
+---
+
 # Open standard
 
 An open standard is any standard that meets the Open Source Initiative's [Open Standard Requirements](https://opensource.org/osr).

organization/general-assemblies/minutes-28-06-2021.md

@@ -32,7 +32,7 @@ Alongside this, we would like this general assembly to have a program for a wide
 
 ## 3. Policy plan 2022-2026
 
-The board of directors would like to invite the members to work with them on the updated policy plan for 2022-2026, which will succeed [our policy plan 2019-2022](../policy-plan.md).
+The board of directors would like to invite the members to work with them on the updated policy plan for 2022-2026, which will succeed [our policy plan 2019-2022](../policy-plans/index.md).
 
 * *Eric will lead a working group to create the policy plan. Ben and Boris offered to support.*
 

organization/index.md

@@ -24,7 +24,7 @@ This is how we're building the organization to support our mission:
 * [Staff](staff.md)
 * [Remuneration policy](remuneration-policy.md)
 * [Roadmap](roadmap.md)
-* [Policy plan](policy-plan.md)
+* [Policy plan](policy-plans/)
 * [Measurable goals](measurable-goals/)
 * [Board meeting minutes](board-of-directors-meetings/)
 * [General assemblies minutes](general-assemblies/)

organization/measurable-goals/index.md

@@ -8,7 +8,7 @@ redirect_from:
 
 # Measurable goals
 
-Currently, the Foundation for Public Code don't use timebound measurable goals.
+Currently, the Foundation for Public Code doesn't use timebound measurable goals.
 
 ## Archive
 

organization/mission.md

@@ -26,10 +26,9 @@ The current priorities of the organization are set
 by the [board of directors](governance-model.md)
 and reviewed every meeting.
 
-On [4 August 2022](board-of-directors-meetings/2022-08-04-minutes.md),
-the priorities were confirmed as:
+The priorities are:
 
-1. Organizational restructuring: align with the needs of public organizations
+1. Organizational restructuring: enable and set up chapter organizations
 1. Codebases: international collaboration
 1. Funding: secure funding for the next years
 1. Partnerships: collaborate with more organizations

organization/policy-plan.md → organization/policy-plans/index.md

@@ -2,6 +2,7 @@
 # SPDX-License-Identifier: CC0-1.0
 # SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]>
 type: resource
+redirect_from: organization/policy-plan
 ---
 
 # Foundation for Public Code Vereniging Policy Plan: 2022
@@ -10,7 +11,7 @@ type: resource
 
 This policy plan sets out the Foundation for Public Code Vereniging’s current plan of action, as established by the board of directors.
 
-This policy plan was adopted at the [12 May 2021 board of directors meeting](board-of-directors-meetings/2022-05-12-minutes.md) and approved by the [general assembly](general-assemblies/minutes-2022-06-29.md).
+This policy plan was adopted at the [12 May 2021 board of directors meeting](../board-of-directors-meetings/2022-05-12-minutes.md) and approved by the [general assembly](../general-assemblies/minutes-2022-06-29.md).
 This policy plan covers 2022-2027, but can be modified annually by the general assembly if needed.
 
 The Foundation for Public Code Vereniging (referred to hereafter as the Foundation for Public Code or ‘the association’) was established to solve an infrastructure gap in public sector collaboration.
@@ -26,11 +27,11 @@ Supporting other organizations in using open public code benefits everyone, but
 But public organizations have recognized that by pooling resources they can enable this for everyone.
 Thus the Foundation for Public Code was created to help open source projects for public organizations become successful, build sustainable communities around them and create a thriving public open source ecosystem.
 
-We do this through ecosystem level [codebase stewardship](../activities/index.md) of both software and civic code (policy), enabling collaboration and re-use at scale.
+We do this through ecosystem level [codebase stewardship](../../activities/index.md) of both software and civic code (policy), enabling collaboration and re-use at scale.
 Codebase stewardship consists of quality auditing of source code, nurturing developer communities, strengthening marketing and product management to increase reusability, and helping public organizations and their vendors understand how they could best use public code with their existing systems.
 The [Standard for Public Code](https://standard.publiccode.net/) operationalizes our mission - it provides concrete standards and best practice for how to make public code reusable, maintainable, findable and procurable.
 
-New members of the Foundation for Public Code Vereniging must be wholly publicly owned organizations ([article 4.2 of the association bylaws](articles-of-association.md)), benefiting all citizens and taxpayers.
+New members of the Foundation for Public Code Vereniging must be wholly publicly owned organizations ([article 4.2 of the association bylaws](../articles-of-association.md)), benefiting all citizens and taxpayers.
 Public code stewarded by the Foundation for Public Code is available online for reuse by anyone anywhere, worldwide.
 
 ## 2. Strategy
@@ -73,7 +74,7 @@ The Foundation for Public Code is completely unique.
 There is no other organization that provides impartial codebase stewardship services designed to support public organizations collaborating with each other for the benefit of citizens and taxpayers.
 This distinguishes it from organizations providing open source codebase stewardship for private sector projects, from vendors selling open source software development to public organizations, and from activist groups lobbying governments to spend taxpayer money only on open source software.
 
-[Our founding principles](mission.md) are:
+[Our founding principles](../mission.md) are:
 
 * We are a non-profit and non-partisan organization.
 * We publish under licenses approved by the Open Source Initiative or Creative Commons licenses that do not limit commercial reuse.
@@ -83,10 +84,10 @@ This distinguishes it from organizations providing open source codebase stewards
 * We prioritize long term sustainability and growth for the benefit of our members.
 * Our work is open by default and welcomes contributions.
 
-[Our cultural values](cultural-values.md) are: open, quality, trust, community, helpful.
+[Our cultural values](../cultural-values.md) are: open, quality, trust, community, helpful.
 These words signify the qualities we strive for in our activities, products, staff and resources.
 
-[The Foundation for Public Code will deliver its mission](mission.md) by:
+[The Foundation for Public Code will deliver its mission](../mission.md) by:
 
 * enabling an ecosystem of Public Code software products, developed by and for public administrations to solve real problems for citizens
 * building a collaborative community of developers and public organizations, which continuously improves and maintains public code products
@@ -143,7 +144,7 @@ In practice we expect to not keep more than the cash equivalent of 36 months’
 
 ### 4.3 Remuneration
 
-[Our remuneration policy](remuneration-policy.md) states that members of the board of directors are not paid for their work as directors.
+[Our remuneration policy](../remuneration-policy.md) states that members of the board of directors are not paid for their work as directors.
 A director may separately be hired and paid by the Foundation for Public Code for work carried out in a different role (for example as a manager or contractor).
 The Foundation for Public Code will reimburse directors for reasonable expenses incurred as a result of their role as director.
 
@@ -174,4 +175,4 @@ The members of the board of directors for the Foundation for Public Code are:
 
 ## 7. Publication
 
-This policy plan and the financial statement are published on the [Foundation for Public Code website](index.md).
+This policy plan and the financial statement are published on the [Foundation for Public Code website](../index.md).