---
tags: Foundation for Public Code, organization, goals
---

# Goals Q1 2022

The sections and tables were based on the [roadmap document](https://about.publiccode.net/organization/roadmap.html). The goals were initially envisioned to be a bit more than half way to the "one year ambition" in that document.

For context, the codebase stewards [Q4 2021 goals](https://blog.publiccode.net/news/2021/11/03/stewards-end-of-year-goals.html) can be seen in an extra column in some sections.

In finding answers to the questions raised by the belastingdienst, our own awareness was raised about gaps in our own sustainability. A new secition "Operational excellence" is added. Imagining onboarding remote administrative staff further highlights gaps in our documentation of our own processes.

A central theme emerging from the first Goals Q1 2022 session is to consider how to use the non-co-located time in Q1 to strengthen our organization's process/workflows, creating a more solid base from which to work in Q2 and beyond.

## Growing the public code ecosystem

### Awareness

| One year ambition | Q1 2022 goal |
|-|-|
| Build out media production capacity | Figure out a way to host video files for archive |
| Begin producing library of media assets: videos, whitepapers, podcasts | Map out content and update About in order to produce at least ~~2~~1 explainer videos and 1 leave-behind. Identify a topic for a whitepaper. Do 2 Let's talk about Public Code podcasts. Apply for appearance on FLOSS Weekly. Host OPEN HOUSE on Twitter Space biweekly to build a following and seed Public Code. |
| Develop coherent awareness-building strategy and voice | Update existing brand content with Kehinde's discoveries and improvements (Debt). Review and revise brand guidelines to be at par with our narrative (Debt). Initiate the plans for **Public Code International Summit** |

### Partnerships

| One year ambition | Q1 2022 goal |
|-|-|
| Define and build-out Partnership relations | (Definition: complete see [pull request](https://github.com/publiccodenet/about/pull/1025), build-out is the items below) |
| International Partner | at least one US/CA public admin |
| Create narratives of collaboration with partners in order to bring more interested parties in | Not a Q1 goal (requires partner)|
| Provide firesouls with anything they need in order to advocate for us | ~~~Spin-up process pattern repos~~~ (BV: figure out future support requirements, consider open development) |

### Memberships

| One year ambition | Q1 2022 goal |
|-|-|
| At least five partner organizations moving towards membership | ~~Define pipeline and activities in this "movement"~~ |
| With one or more signing on as members | ~~at least one member likely to sign~~ |
| Establish our first international field office to develop potential members, partners, and codebases | ~~done?~~ |

## Tending to stewardship

## Activities & Processes

| One year ambition | Q4 2021 goal | Q1 2022 goal
|-|-|-|
| Launch formal process stewardship practice | 1. Clean up our own documentation 2. ~~Have an outline of how a certification process could look like~~ | ~~Have an outline of how a certification process could look like~~ (JA) |
| Help a codebase that is spun off from the host organization become its own external non-profit stewardship foundation | | ~~Identify a candidate codebase and establish first contact~~ (claus)
| Include on our website a visual and short explanation of what we do | 1. Create a communication plan (including social media plan) about stewardship 2. Create explainer on importance of international ambition for a codebase | Have a brief and a quote for a visual explainer of codebase stewardship / revisit and freshen up the explainer texts we have on about/case for support |

## Codebases

| One year ambition | Q4 2021 goal | Q1 2022 goal
|-|-|-|
| Determine how much capacity we want to invest in direct stewardship in 5 years | Make a wishlist of types of codebases we desire for direct stewardship | ~~Estimate number of stewards required to directly steward that list~~ |
| Develop pipeline for codebases to be stewarded by other organizations | (work on documenting stewardship process above) | ~~(~~not ~~a Q1 goal)~~ |
| Refine codebase routing/gating criteria for ongoing internal or external stewardship | Document criteria we use to invest time in a codebase/community, check (and document) criteria we use to commit to steward a codebase and the citeria we use to exit our activities. Document any relationship to partner / member / funding opportunity | (This one is done!)
| Directly steward an international collaboration | 1. Suggest stewardship to OpenFisca 2. Create prioritized shortlist of codebases with international potential that we would like to steward, including USA/CA codebases | ~~Engage a category leader codebase for possible Foundation stewardship, or~~ advance OpenFisca (EH)~~, Does the Notify codebase need collabortion and stewardship? if so engage. Connect/re-connect to all codebases on the shortlist to get conversations started/keep them going~~(JA) |
| Positively impact the codebases under our stewardship | Collect and list areas of impact per codebase (feed into storytelling plan) | Get Omgevingsbeleid impact story |

## Community of practice

| One year ambition | Q4 2021 goal | Q1 2022 goal
|-|-|-|
| Engage another organization in using and developing our materials and practices | Engage associations of public organizations | ~~Have at least one party use and ideally contribute to knowledge assets~~ (suggest move to Q2 -EKH) Clean up and professionalise our GitHub repositories to allow for more effective remote, asynch and open working, as well as debug and restructure the About repository' |
| Organize a conference around a stewarded codebase community of practice | Set a date and scope for the conference | Set a date and scope (including funding) for conference, ~~invite speakers and co-stakeholders~~. Also FOSDEM devroom |
| Get testimonials in our website | (see positive impact on codebases, storytelling plan) | Scan our podcasts for positive quotes |
| Regular stewardship community meetup group | ~~Make a plan (including goals, audience and formats)~~ | ~~Make a plan (including goals, audience and formats, maybe a guest presents what they do?)~~ |
| Create modular content to more easily adapt to different personas | Define the different personas we want to use | ~~Make~~ *Define* content which specifically targets an underserved audience. e.g.: civil servants who are stakeholders, or policymakers that has been tasked with implementing an open source strategy |
| Launch an online open source learning platform where we can host course material based on the stewardship framework | Select platform and get it up and running, with the Standard for Public Code course from the City by City Academy platform ported to it | ~~Launch the platform publicly~~ (JA, no rush)
| Create guidance modules for codebase lifecycles, governance, and finance | Table of Contents (and a shared understanding of the topic) | ~~Condensate and digest learnings from stewardship into discreet assets~~ |

## Achieving sustainability

### Philanthropy and grants

| One year ambition | Q1 2022 goal |
|-|-|
| A third > €1 million individual grantor | Open conversation with at least 3 potential €1m+ donors |
| Participation in multiple fundraising networking events | Identify one or more events |
| Respond to calls for proposal from at least 3 granting philanthropic organizations | ~~~Get overview of interesting granting organizations and mechanisms and know how to submit for grants~~~ (BV) |
| Produce visual content for potential investors | Get feedback on, update and produce new batch of Case for Support/partnership/donors. Draft script for introduction video to the Foundation ([inspiration](https://www.youtube.com/watch?v=bbtQcW4E_RU)) |

### Structural funding

| One year ambition | Q1 2022 goal |
|-|-|
| Secure structural funding of > €250K from at least one regional or state public administration | ~~~Proposal for Ministerie van Binnenlandse Zaken, Amsterdam, Vereniging Nederlandse Gemeenten~~~ (BV) |

### Operational excellence

Professionalize an exemplary open public organization

| One year ambition | Q1 2022 goal |
|-|-|
| A well administered institution with open and strong processes | Ensuring that our processes are documented well enough that we can onboard a new administrative assistant |
| An open organization | Remove information on About which is not accurate |
| (housekeeping)| Do an inventory of our video files and make accessible for content repurposing |
| | **Before end 2021**: policy plan |
| | **Before end 2021**: multiple ventures contract |
| | **Before end 2021**: book keepers, process |
| | **Before end 2021**: gift paperwork |
| | **Before end 2021**: general assembly to validate policy plan |
| | **Before end 2021**: follow-up with members |
| | Before 1 July: annual report |
| | gh-pages for community translations |