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

README.md

@@ -3,11 +3,15 @@
 <!-- SPDX-License-Identifier: CC0-1.0 -->
 <!-- SPDX-FileCopyrightText: 2018-2023 The Foundation for Public Code <[email protected]> -->
 
+We help open source projects for public organizations to become successful, build sustainable communities around them and create a thriving public open source ecosystem.
+
 [Our mission](organization/mission.md) is:
 
 > [...] to enable public-purpose software and policy that is open and collaborative.
 
-This repository is meant to reflect the concept of the Foundation for Public Code and hold all information about it.
+The [About site](activities/documentation/index.md) is home to all of our staff information, decision-making rules and processes.
+It is our staff manual that can be developed collaboratively with the community and reused by everyone.
+
 It's `main` branch is the official ['source of truth'](GOVERNANCE.md) and central repository for all information about the Foundation for Public Code.
 
 [![pages-build-deployment](https://github.com/publiccodenet/about/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/publiccodenet/about/actions/workflows/pages/pages-build-deployment)
@@ -18,11 +22,14 @@ It's `main` branch is the official ['source of truth'](GOVERNANCE.md) and centra
 
 We are looking for people like you to [contribute](CONTRIBUTING.md) to this project by suggesting improvements and helping develop the Foundation for Public Code. 😊
 
-Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. Please be lovely to all other community members.
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md).
+By participating in this project you agree to abide by its terms.
+Please be lovely to all other community members.
 
 ## Preview, build and deploy
 
-The repository builds to a static site deployed at [about.publiccode.net](https://about.publiccode.net/). It is built with [GitHub pages](https://pages.github.com) and [Jekyll](https://jekyllrb.com/).
+The repository builds to a static site deployed at [about.publiccode.net](https://about.publiccode.net/).
+It is built with [GitHub pages](https://pages.github.com) and [Jekyll](https://jekyllrb.com/).
 
 Releasing and deploying [is done with a release branch](activities/documentation/merge-develop-into-main.md).
 
@@ -37,6 +44,8 @@ You can use the scripts:
 
 [![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
 
-To the extent possible under law, the Foundation for Public Code has waived all copyright and related or neighboring rights to the content in this repository. It is [licensed CC0](https://creativecommons.org/publicdomain/zero/1.0/), which basically means that anyone can do anything with it. This does not apply to trademarks or logos of the Foundation for Public Code.
+To the extent possible under law, the Foundation for Public Code has waived all copyright and related or neighboring rights to the content in this repository.
+It is [licensed CC0](https://creativecommons.org/publicdomain/zero/1.0/), which basically means that anyone can do anything with it.
+This does not apply to trademarks or logos of the Foundation for Public Code.
 
 Contributors to this repository agree that their contributions also fall under this license and that they have the power and authority to grant this licence.

activities/board-support/board-meeting-process.md

@@ -44,7 +44,9 @@ Board members may be sent an overview of the open action items between meetings.
 
 The archive of the board will be kept on a secret shared drive.
 
-The drive is accessible to board members whilst a member. Future board members can also see the historical archive. Access is also granted to those assisting the secretary.
+The drive is accessible to board members whilst a member.
+Future board members can also see the historical archive.
+Access is also granted to those assisting the secretary.
 
 The drive contains:
 

activities/codebase-auditing/auditing-process.md

@@ -6,7 +6,8 @@ type: Resource
 
 # The auditing process
 
-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 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.
 

activities/codebase-auditing/certification.md

@@ -6,9 +6,12 @@ type: Resource
 
 # Public code codebase and contribution certifications
 
-If an individual contribution to a codebase passes the audit, that contribution is certified. If every contribution to a codebase has been certified – or the entire codebase has passed and been certified as one contribution – the codebase is certified.
+If an individual contribution to a codebase passes the audit, that contribution is certified.
+If every contribution to a codebase has been certified – or the entire codebase has passed and been certified as one contribution – the codebase is certified.
 
-If the public code audit process is added to a codebase later in its development, new merge requests can be certified but the existing code cannot be. By auditing every contribution the codebase can move towards being completely certified. For the codebase to be completely certified every meaningful line of code, and the commits behind the code, must meet the [Standard for Public Code](https://standard.publiccode.net/).
+If the public code audit process is added to a codebase later in its development, new merge requests can be certified but the existing code cannot be.
+By auditing every contribution the codebase can move towards being completely certified.
+For the codebase to be completely certified every meaningful line of code, and the commits behind the code, must meet the [Standard for Public Code](https://standard.publiccode.net/).
 
 Certified codebases can use [the certification badge](https://github.com/publiccodenet/standard-compliant#svg) which should link to a verification on [standard-compliant](http://standard-compliant.publiccode.net/).
 

activities/codebase-auditing/index.md

@@ -11,7 +11,8 @@ We perform audits on [codebases](../../glossary/codebase-definition.md) – incl
 * the [Standard for Public Code](https://standard.publiccode.net/)
 * the standards set out in the codebase itself
 
-The audit performed by auditors of the Foundation for Public Code is meant to complement machine testing. Auditors test for whether documentation is actually understandable and attached, the commit messages make sense, community-oriented guidelines are being followed and other factors that cannot be machine tested.
+The audit performed by auditors of the Foundation for Public Code is meant to complement machine testing.
+Auditors test for whether documentation is actually understandable and attached, the commit messages make sense, community-oriented guidelines are being followed and other factors that cannot be machine tested.
 
 Certification by the Foundation for Public Code on suggested contributions can provide reassurance to maintainers when deciding whether to incorporate them.
 

activities/codebase-stewardship/for-existing-projects.md

@@ -6,7 +6,8 @@ type: Resource
 
 # Codebase stewardship for existing projects
 
-Codebase stewardship can be provided to an existing codebase. In this case, there might be some important considerations about how to transition and budget for that.
+Codebase stewardship can be provided to an existing codebase.
+In this case, there might be some important considerations about how to transition and budget for that.
 
 ## How to start
 

activities/codebase-stewardship/stewardship-proposal-template.md

@@ -6,8 +6,10 @@ type: Resource
 
 # Codebase stewardship proposal template
 
-The purpose of this document is to build a shared understanding and commitment to a common stewardship trajectory. It also includes an annex with example timeline and practical next steps for discussion.
+The purpose of this document is to build a shared understanding and commitment to a common stewardship trajectory.
+It also includes an annex with example timeline and practical next steps for discussion.
 
-We can send this document to the principal maintainer, as well as other members of the community. We can do this after one or several introductory meetings with the maintainers and other members of the community.
+We can send this document to the principal maintainer, as well as other members of the community.
+We can do this after one or several introductory meetings with the maintainers and other members of the community.
 
 [Template for codebase stewardship proposal](https://docs.google.com/document/d/1YzmfYm1G7jBfqyh5HMrkr1XM2jQMtz7P-mXoTk5m4BQ/edit).

activities/codebase-stewardship/user-personas/index.md

@@ -6,7 +6,9 @@ type: Index
 
 # User personas
 
-In order to understand better the behavior and aspirations of our community, we've developed this *personas* template folder. In user-centered design and marketing, a persona or user persona is a fictional character created to represent a user type. Our community members have important needs and frustrations that must be kept in mind when developing a resource for them.
+In order to understand better the behavior and aspirations of our community, we've developed this *personas* template folder.
+In user-centered design and marketing, a persona or user persona is a fictional character created to represent a user type.
+Our community members have important needs and frustrations that must be kept in mind when developing a resource for them.
 
 Once again, every persona represented here describes the behavior of a hypothesized contributor of our community.
 

activities/communication/basic-tweet-template.md

@@ -14,8 +14,11 @@ Our tweets are often accompanied by relevant images or emoji.
 
 ## When to use this template
 
-When suggesting something for social sharing, use this template to create a draft tweet or toot (for Mastodon). Also consider images, gifs or emoji. Note that Twitter's algorithm prioritizes tweets with images or video.
+When suggesting something for social sharing, use this template to create a draft tweet or toot (for Mastodon).
+Also consider images, gifs or emoji.
+Note that Twitter's algorithm prioritizes tweets with images or video.
 
 Add a link to your draft tweet to column J of the [communications calendar](https://docs.google.com/spreadsheets/d/1me6eipaLCHH4GUWlZtPC_cQku0xRUiCqhfUOU2VtXHE/edit?usp=sharing) (not shared publicly).
 
-This helps the communications coordinator by clearly providing basic facts. It also acts as the basis for a conversation about the best possible hook, timing of your tweet, or other communications activity we can plan around your thing.
+This helps the communications coordinator by clearly providing basic facts.
+It also acts as the basis for a conversation about the best possible hook, timing of your tweet, or other communications activity we can plan around your thing.

activities/communication/blogging.md

@@ -7,7 +7,8 @@ Explains: how to blog
 
 # How and why we blog
 
-[We blog](https://blog.publiccode.net/) for a number of different reasons. This guide gives background information about the blog and instructions on how to blog.
+[We blog](https://blog.publiccode.net/) for a number of different reasons.
+This guide gives background information about the blog and instructions on how to blog.
 
 ## Why we have a blog
 
@@ -20,13 +21,18 @@ The blog is our primary tool for talking about:
 
 Not all information published on the blog needs to support our marketing strategy - for example, an in-depth discussion about a technology choice we’ve made may not persuade potential Foundation for Public Code partners, but will be interesting to technologists in our community.
 
-To make sure we have the editorial freedom to publish about all of our work (no matter how niche), there’s no direct link to the blog on [publiccode.net](https://publiccode.net/). Instead, we may feature important blogposts. (We’ll build this functionality once we have important blogposts.)
+To make sure we have the editorial freedom to publish about all of our work (no matter how niche), there’s no direct link to the blog on [publiccode.net](https://publiccode.net/).
+Instead, we may feature important blogposts.
+(We’ll build this functionality once we have important blogposts.)
 
 ## Blogposts are ephemera
 
-Blogposts are different from [resources and guides published on About](../documentation/index.md), which we keep updating. By contrast, a blogpost is only true at that moment in time. We shouldn’t ever update a blogpost with more current information.
+Blogposts are different from [resources and guides published on About](../documentation/index.md), which we keep updating.
+By contrast, a blogpost is only true at that moment in time.
+We shouldn’t ever update a blogpost with more current information.
 
-Instead, we can add a note with a link to follow up blogposts or new information published on the same topic. Adding links from older blogposts to newer blogposts also lets new blogposts benefit from the greater search engine weighting given to older, still popular pages.
+Instead, we can add a note with a link to follow up blogposts or new information published on the same topic.
+Adding links from older blogposts to newer blogposts also lets new blogposts benefit from the greater search engine weighting given to older, still popular pages.
 
 This approach reduces our [future content debt](https://18f.gsa.gov/2016/05/19/content-debt-what-it-is-where-to-find-it-and-how-to-prevent-it-in-the-first-place/) and avoids undermining our position of authority - for example, we'll never have to change a blogpost to say that due to a government policy shift, an expert we’ve interviewed is no longer in post (which might cast doubt on that expert’s still-relevant advice).
 
@@ -42,7 +48,8 @@ This approach reduces our [future content debt](https://18f.gsa.gov/2016/05/19/c
 
 ## Write your blogpost
 
-Write your draft blogpost using a collaborative document tool. This lets you share it for pair writing, factchecking, feedback or proofreading.
+Write your draft blogpost using a collaborative document tool.
+This lets you share it for pair writing, factchecking, feedback or proofreading.
 
 Don't hesitate to involve other people in your writing process - we want you to succeed, and we know how helpful an external perspective can be once something starts to feel like a slog.
 

activities/communication/communications-plan.md

@@ -10,9 +10,11 @@ The Foundation for Public Code relies on communications to [achieve its mission]
 
 ## Principles
 
-Our communications need to reflect our core values: open, quality, trust, community, helpful. They must also be non-partisan, in line with our [founding principles](../../organization/mission.md#founding-principles).
+Our communications need to reflect our core values: open, quality, trust, community, helpful.
+They must also be non-partisan, in line with our [founding principles](../../organization/mission.md#founding-principles).
 
-Our messages range from neutral in tone to positive and inspirational. Our community won’t be sustainable if we attract people motivated by fear or anger.
+Our messages range from neutral in tone to positive and inspirational.
+Our community won’t be sustainable if we attract people motivated by fear or anger.
 
 Our communications are usually in plain English, but we link to highly relevant pages in other languages, for example about our partners’ work.
 
@@ -45,7 +47,8 @@ We believe we'll find them in fora organized by and for:
 
 ## Success criteria and indicators for target fora
 
-Note: none of these goals contain 'hype' or 'coolness'. This is because being perceived as trendy or zeitgeisty will not help us build the trustworthy reputation or longterm relationships we need to succeed.
+Note: none of these goals contain 'hype' or 'coolness'.
+This is because being perceived as trendy or zeitgeisty will not help us build the trustworthy reputation or longterm relationships we need to succeed.
 
 ### Public tech fora
 
@@ -269,7 +272,8 @@ Blogposts should have a more personal authorial voice, while still showcasing ou
 
 ## Messaging matrix
 
-We don’t know what the ideal ratio of audiences to target is yet. We’ll develop as we learn more about who actually engages with us.
+We don’t know what the ideal ratio of audiences to target is yet.
+We’ll develop as we learn more about who actually engages with us.
 
 ## Campaigns
 
@@ -281,7 +285,8 @@ We run a campaign every time:
 
 ### Campaign template
 
-This should be tied into general strategy sessions, so we get the maximum impact from each event or milestone. These are generally structured as:
+This should be tied into general strategy sessions, so we get the maximum impact from each event or milestone.
+These are generally structured as:
 
 * announcement that thing is happening (give teaser)
 * join in on other related conversations and hashtags (monitor conversation)

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

@@ -18,7 +18,9 @@ DD Mon Foundation for Public Code community call
 
 Our next Foundation for Public Code community call will take place at hh.mm on Weekday, DD Month.
 
-[Insert line om what the topic of the call is. Also add a line on why we want to talk with the community about this. If participants can benefit of preparing, mention it as well.]
+[Insert line om what the topic of the call is.
+Also add a line on why we want to talk with the community about this.
+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.
 

activities/communication/community-call.md

@@ -6,7 +6,8 @@ type: Resource
 
 # Foundation for Public Code community call
 
-We run regular [community calls](../community-calls/index.md) for the Foundation for Public Code. These invite our community to join us in discussing big questions, approaches we're considering for the future or things we've learned.
+We run regular [community calls](../community-calls/index.md) for the Foundation for Public Code.
+These invite our community to join us in discussing big questions, approaches we're considering for the future or things we've learned.
 
 [See the community calls guidance](../community-calls/index.md) for our current community call schedule, how to join and guidance on how to run a community call.
 

activities/communication/how-to-post-to-social-media.md

@@ -7,7 +7,8 @@ explains: how to use Planable
 
 # How to post to social media
 
-We use Planable to draft, review and post social media posts on Twitter, LinkedIn and Facebook. Planable is set up so that many people on the team can propose social media posts, but no posts can go live without a review.
+We use Planable to draft, review and post social media posts on Twitter, LinkedIn and Facebook.
+Planable is set up so that many people on the team can propose social media posts, but no posts can go live without a review.
 
 Our goals for Planable are:
 
@@ -17,7 +18,8 @@ Our goals for Planable are:
 
 ## Why we post to social media
 
-We use social media to share information that's interesting or exciting to us. Our information should be timely, and it's ok if posts are no longer relevant a week after they're published.
+We use social media to share information that's interesting or exciting to us.
+Our information should be timely, and it's ok if posts are no longer relevant a week after they're published.
 
 Typical content for our social posts includes: