Merge branch 'develop' into updates-governance-model-without-members

activities/communication/blogging.md

@@ -95,6 +95,14 @@ Example:
 {% raw %}![alternative text]({{site.url}}/assets/image.jpg){% endraw %}
 ```
 
+If you would like to link to another blogpost, use a [dynamic link](https://www.digitalocean.com/community/tutorials/how-to-control-urls-and-links-in-jekyll#making-robust-links-to-posts).
+
+Example:
+
+```
+{% raw %}[Text you want to hyperlink]({% post_url yyyy-mm-dd-title-of-the-post-you-want-to-link %}){% endraw %}
+```
+
 ### Step 3: create a pull request and release the new blogpost
 
 Commit your changes and create a pull request.

activities/documentation/index.md

@@ -37,4 +37,4 @@ In order to make it easier to navigate and contribute information we try to limi
 * [How to publish on About (merging develop into main)](merge-develop-into-main.md)
 * [How to move, merge and delete pages](move-merge-delete-pages.md)
 
-See also our [trainings](../trainings/index.md), which have tips on Github, issues, and more.
+See also our [trainings](../trainings/index.md), which have tips on Github, issues, Jekyll, and more.

activities/tool-management/etherpad.md

@@ -0,0 +1,22 @@
+---
+# SPDX-License-Identifier: CC0-1.0
+# SPDX-FileCopyrightText: 2023 The Foundation for Public Code <[email protected]>
+type: resource
+---
+
+# Etherpad
+
+We have an Etherpad lite running at [write.publiccode.net](https://write.publiccode.net/).
+
+## What to do with people's data
+
+A user can provide their name or a pseudonym as author.
+All authorships can be cleared from the current version but it will still be shown in the Timeslider functionality.
+
+## How we handle code of conduct violations
+
+By default, the full [Foundation for Public Code code of conduct](../../CODE_OF_CONDUCT.md) applies to all of our pads.
+
+## Etherpad management
+
+The Etherpad is hosted on a VPS at [Maadix](https://maadix.net/en), an independent service provider.

activities/tool-management/index.md

@@ -33,6 +33,7 @@ Our guidance covers:
 
 * [1password](1password.md) (password management)
 * [Docusign](docusign.md) (contract management)
+* [Etherpad](etherpad.md) (shared text editing)
 * [Excalidraw](excalidraw.md) (online collaborative whiteboard)
 * [GitHub](github.md) (version control and codebase management)
 * [Google Workspace](google-workspace.md) (email, calendaring and internal document management)

activities/tool-management/jitsi-meet.md

@@ -25,11 +25,18 @@ We also have a Jitsi instance running for our community on 'meet.community.publi
 
 Jitsi is running on a VPS with 8 GB of RAM for resilience and scalability. The VPS is maintained by the operations coordinator who also takes care of user administration and customizations.
 
+The internal `meet.publiccode.net` system is configured with Ubuntu LTS, with the following additions:
+
+```
+/etc/apt/sources.list.d/jitsi-stable.list
+/etc/apt/sources.list.d/prosody.list
+```
+
 SSH keys are needed to perform updates, as one needs to access the machines as root. Log into the machine via the command line with:
 
-`Jitsi internal: ssh root@188.166.30.33`
+Jitsi internal: `ssh root@meet.publiccode.net`
 
-`Jitsi community: ssh root@161.35.83.251`
+Jitsi community: `ssh root@meet.community.publiccode.net`
 
 The following commands perform general updates and upgrades:
 
@@ -53,15 +60,25 @@ If you need to make tweaks to the configuration files, then these can be accesse
 
 `nano /etc/prosody/conf.avail/meet.publiccode.net.cfg.lua`
 
-`prosodyctl register user meet.publiccode.net password`
-
 `nano /usr/share/jitsi-meet/interface_config.js`
 
+If you are making changes or updates to the Jitsi Community configuration `meet.publiccode.net` needs to be replaced with `meet.community.publiccode.net`
+
+On the internal server,
 [Prosody](https://prosody.im/) is used for creating and managing user accounts.
 
 `ls -l /var/lib/prosody/*/accounts/*`
 
-If you are making changes or updates to the Jitsi Community configuration `meet.publiccode.net` needs to be replaced with `meet.community.publiccode.net`
+Accounts can be created from the commandline:
+
+```
+register ${NEW_USER_NAME} meet.publiccode.net $(random-string)
+cat /var/lib/prosody/meet%2epubliccode%2enet/accounts/${NEW_USER_NAME}.dat
+```
+
+On the meet.community.publiccode.net server, accounts are created and managed with
+[publiccodenet/jitsi-community](https://github.com/publiccodenet/jitsi-community)
+as described in [jitsi-guides](jitsi-guides.md).
 
 ## Jitsi customization
 

activities/tool-management/mattermost.md

@@ -21,7 +21,7 @@ This includes uploading important emojis :)
 
 General updates and upgrades by SSH-ing into the machine as root:
 
-`ssh root@64.227.76.103`
+`ssh root@chat.publiccode.net`
 
 `apt update`
 

activities/tool-management/odoo.md

@@ -15,6 +15,8 @@ Odoo is a suite of open source business apps. We use Odoo for:
 
 ## Using Odoo
 
+The operations coordinator will invite you to join.
+Once signed up, you can login via [our login portal](https://odoo.publiccode.net/web/login).
 We offer training to new staff.
 
 ## Odoo management

activities/trainings/index.md

@@ -17,6 +17,7 @@ Here is a list of trainings developed or used by the Foundation for Public Code:
 * [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
 
 As a Foundation for Public Code staff member, you can also [request professional development](../staff-information/request-professional-development.md) training.
 Here is a non-exhaustive and running list of [potential training providers](https://docs.google.com/spreadsheets/d/19tAALXVNk9P27nmI6Qe_4_ppaDIeEtexeKMyUvTTkH4/edit#gid=0) compiled by staff.

activities/value-and-impact/policy-documents.md

@@ -9,6 +9,7 @@ explains: where we are mentioned in public policy documents
 
 ## 2023
 
+* Swedish Working group for coordination of software (asom): [Meeting minutes 2023-08-31: strategically strive for Standard for Public Code certification](https://ocis.sma.owncloud.works/s/AeJtUOAPYxjeUnl) (in Swedish)
 * T20 India: [Laying the Foundation for the Future: Open Source Sustainability and the Adoption of Digital Public Goods](https://t20ind.org/research/laying-the-foundation-for-the-future/)
 
 ## 2022

index.md

@@ -29,8 +29,6 @@ Our [home page at publiccode.net](https://publiccode.net) features a [high level
 
 Additionally, we have separate sites that show our [projects](https://projects.publiccode.net), [how to use the brand](https://brand.publiccode.net/) and our [blog](https://blog.publiccode.net).
 
-## We need you
+## Open to contribution
 
-We can [use your help](CONTRIBUTING.md) to make the Foundation for Public Code a success.
-
-If you want to get our news delivered directly to you, [join our mailing list](https://odoo.publiccode.net/survey/start/594b9243-c7e5-4bc1-8714-35137c971842).
+We [encourage contributions](CONTRIBUTING.md) by anyone to help improve the Foundation for Public Code.

organization/board-of-directors-meetings/2023-01-11-minutes.md

@@ -4,7 +4,7 @@
 type: Resource
 ---
 
-# Board meeting January 11th 2022
+# Board meeting January 11th 2023
 
 Attendees:
 

organization/index.md

@@ -10,8 +10,6 @@ redirect_from: members/
 The Foundation for Public Code's mission is to enable public-purpose software and policy that is open and collaborative.
 Read more about [our mission, founding principles and current priorities](mission.md).
 
-[Contact us](contact-details.md) – we'd love to hear from you.
-
 ## How we're organized
 
 This is how we're building the organization to support our mission:

organization/roadmap.md

@@ -6,11 +6,12 @@ type: Resource
 
 # Roadmap
 
-This roadmap serves as a model for how we're developing, growing and scaling our organization. It sets out the roles for both the staff and the members of the Foundation for Public Code.
+This roadmap serves as a model for how we're developing, growing and scaling our organization.
+It is defined and approved by the board of directors.
 
 ## Growing the public code ecosystem
 
-> Awareness, Partnership, and Membership
+> Awareness, Partnership, and Chapters
 
 The Foundation for Public Code will continue to transform and expand to meet the growing needs for digital infrastructure stewardship in the public sector.
 
@@ -30,29 +31,27 @@ To this end we will expand our capabilities and capacity to continuously produce
 
 ### Partnerships
 
-The Foundation for Public Code is an Association, which means that it is owned by its members.
-Only public administrations can become members, which will make them part owners of the Foundation, participating directly in its governance and sustainability.
-Membership of globally widespread public organizations is the long-term goal of the Foundation.
-However, we recognize that the hurdles for them to make such a commitment are significant.
-So going forward, we will first establish partnerships with interested public organizations, and help them prepare to participate in the codebase stewardship collaboration process.
-By building networks of collaboration with partners at the municipal and regional levels, it will become easier to bring the case for membership to national governments and larger states or provinces, as many of the gains in sharing public software across cities are recognized most easily by these ‘parent’ organizations.
+The Foundation for Public Code seeks to establish partnerships with interested public organizations, and help them prepare to participate in the codebase stewardship collaboration process.
+By building networks of collaboration with partners at the municipal and regional levels, it will become easier to bring the case for structural financial support to national governments and larger states or provinces, as many of the gains in sharing public software across cities are recognized most easily by these ‘parent’ organizations.
 
 A focus for the partnership program will be global diversification, with an interest in discovering and supporting existing open software infrastructure that has been developed by cities and their vendors regionally, and which solves a problem for multiple other potential replicating organizations.
 In addition, we will seek organizations that are planning similar large procurements, and help them collaborate around a single shared codebase instead of working in in parallel.
 
 | One year | Five years | Twenty years |
 |---|---|---|
-| {::nomarkdown}<ul><li>Define and build-out Partnership relations</li><li>International Partner</li><li>Create narratives of collaboration with partners in order to bring more interested parties in</li><li>Provide firesouls with anything they need in order to advocate for us</li></ul>{:/} | {::nomarkdown}<ul><li>Multiple international partners (for instance OS2)</li><li>Examples of networks of partners leading to structural funding or membership in their parent organizations</li><li>Example of shared procurement amongst partners (and members)</li></ul>{:/} | {::nomarkdown}<ul><li>Vast global ecosystem of partners on many levels of public administration</li><li>Significant percentage of partners heading towards membership or structural funding</li></ul>{:/} |
+| {::nomarkdown}<ul><li>Define and build-out Partnership relations</li><li>International Partner</li><li>Create narratives of collaboration with partners in order to bring more interested parties in</li><li>Provide firesouls with anything they need in order to advocate for us</li></ul>{:/} | {::nomarkdown}<ul><li>Multiple international partners (for instance OS2)</li><li>Examples of networks of partners leading to structural funding</li><li>Example of shared procurement amongst partners</li></ul>{:/} | {::nomarkdown}<ul><li>Vast global ecosystem of partners on many levels of public administration</li><li>Significant percentage of partners heading towards structural funding</li></ul>{:/} |
 
-### Memberships
+### Chapters
 
-Our most active focus for membership in the Foundation will shift toward provinces, states, and national governments.
-If the Foundation for Public Code begins to prove value within a network of regional municipal partners, it makes most sense to take the case for structural support to the infrastructural agencies of the ‘parent’ state.
-We are moving conversations forward with national governments in Europe and North America, and expect to slowly scale the rate at which we add state-level members.
+The Foundation for Public Code is transforming its organizational model to enable international chapters.
+There will be a global umbrella organization, along with local chapter organizations.
+The umbrella organization will be an association in which the strategic council, board of directors, and delegates from the chapter organizations work together to define long term priorities.
+Local chapters will tailor their work based on the needs of the local public code ecosystem and participating public organizations.
+The North America chapter is the Foundation for Public Code's first local chapter.
 
 | One year | Five years | Twenty years |
 |---|---|---|
-| {::nomarkdown}<ul><li>At least five partner organizations moving towards membership</li><li>With one or more signing on as members</li><li>Establish our first international field office to develop potential members, partners, and codebases</li></ul>{:/} | {::nomarkdown}<ul><li>Members from at least two nations</li><li>A national-level public organization is a member</li></ul>{:/} | {::nomarkdown}<ul><li>The Foundation for Public Code is a global public organization owned by numerous international public members</li><li>Governance model and support activities recognized akin to other global orgs (e.g. Red Cross)</li></ul>{:/} |
+| {::nomarkdown}<ul><li>Consolidate and grow the North American chapter</li><li>Launch the European chapter</li><li>Identify opportunities for future chapters</li></ul>{:/} | {::nomarkdown}<ul><li>Chapters in 3 to 5 geographical regions</li><li>Wide financial and political support for chapters from within their respective regions</li></ul>{:/} | {::nomarkdown}<ul><li>Chapters in all or most geographical regions, supporting public code regionally</li><li>Global umbrella organization setting the global agenda for public code</li></ul>{:/} |
 
 ## Tending to stewardship
 

organization/staff.md

@@ -8,7 +8,7 @@ type: Resource
 
 The staff of the Foundation for Public Code Vereniging are employees that execute the work agreed on by the [general assembly](../organization/governance-model.md#general-assembly) under direction of the [board of directors](../organization/governance-model.md#board-of-directors).
 
-[Meet our team](https://publiccode.net/who-we-are/) or [come work with us](https://publiccode.net/careers).
+All staff are represented on our ["who we are" page](https://publiccode.net/who-we-are/) and we hire through our [careers page](https://publiccode.net/careers).
 
 As we are a community leadership organization that mostly helps others, we aim for minimal hierarchy and overhead and maximal autonomy for the specialists who further [our mission](mission.md).