-
Notifications
You must be signed in to change notification settings - Fork 16
Draft policy plan 2024 #1401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
clausmullie
wants to merge
30
commits into
develop
Choose a base branch
from
draft-policy-plan-2024
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Draft policy plan 2024 #1401
Changes from 19 commits
Commits
Show all changes
30 commits
Select commit
Hold shift + click to select a range
accb7bb
replaces minute links with placeholders
clausmullie ea1b5a7
bumps dates
clausmullie c6f3858
removes reference to members
clausmullie 09d4f41
updates to match current bullets on mission.md
clausmullie 305441b
repeats line 33 - redundant
clausmullie 4b77af5
strategic council has been set up
clausmullie 33427fd
switches member dues to contributions from public orgs
clausmullie 99a44c4
adds chapter model
clausmullie 3779ffa
add chapters and partners to phase 2
clausmullie e9fd8d6
tweaks long term chapter goal
clausmullie 47d4b19
philanthropy as current main source of finance
clausmullie 80b93ff
removes note on not pursuing philanthropy
clausmullie 49cc201
remove reference to member dues
clausmullie 3ae1d11
updates board
clausmullie fc11ce9
changes about link to .net link
clausmullie e98f308
adds process codes
clausmullie a101840
adds oxford comma
clausmullie 94adf66
replaces 'and' with '&' for readability
clausmullie f8c0e47
Merge branch 'develop' into draft-policy-plan-2024
clausmullie 50db2a1
Merge branch 'develop' into draft-policy-plan-2024
ElenaFdR 0353c3b
Update organization/policy-plan.md
clausmullie b10ac22
Merge branch 'develop' into draft-policy-plan-2024
clausmullie cead8de
Updates to bring in line with develop
clausmullie 91e8c4c
Merge branch 'develop' of github.com:publiccodenet/about into draft-p…
clausmullie f168afd
replaces old policy plan with new
clausmullie 216dff3
moves old policy plan
clausmullie fa4f3d1
links to old policy plan
clausmullie 7bc1e5b
fixing pathing
clausmullie ad252b1
Merge branch 'develop' into draft-policy-plan-2024
ElenaFdR 33c0bbe
Merge branch 'develop' into draft-policy-plan-2024
ElenaFdR File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,8 +10,8 @@ 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 covers 2022-2027, but can be modified annually by the general assembly if needed. | ||
This policy plan was adopted at the [*BOARD MEETING*](*minutes url*) and approved by the [*GENERAL ASSEMBLY*](*minutes url*). | ||
This policy plan covers 2024-2030, 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. | ||
Public organizations (like cities) are both more interested in and producing more open source software than ever before. | ||
|
@@ -26,11 +26,10 @@ 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. | ||
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. | ||
We do this through ecosystem level [codebase stewardship](https://publiccode.net/codebase-stewardship/) 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 & product management to increase reusability, and helping public organizations & their vendors understand how they could best use public code with their existing systems. | ||
clausmullie marked this conversation as resolved.
Show resolved
Hide resolved
|
||
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. | ||
Public code stewarded by the Foundation for Public Code is available online for reuse by anyone anywhere, worldwide. | ||
|
||
## 2. Strategy | ||
|
@@ -41,12 +40,10 @@ Public code stewarded by the Foundation for Public Code is available online for | |
|
||
The goal of the Foundation for Public Code is “to support collective development and maintenance of public code (software and policy with a public purpose) in order to reduce risks, increase quality, reduce costs and increase sustainability” (article 3.1 of the association bylaws). | ||
|
||
Public code stewarded by the Foundation is openly available for reuse by everyone, but only members (wholly publicly owned organizations) can determine the governance and the organization’s stewardship priorities. | ||
|
||
The association seeks to achieve its goal by carrying out the following activities (article 3.2. of the association bylaws): | ||
|
||
* a. the provision of services that can increase the sustainability, quality and re-use of public code | ||
* b. facilitating and encouraging the sharing of existing public code between public members and other public organizations | ||
* b. facilitating and encouraging the sharing of existing public code between public organizations | ||
* c. carrying out research for the (further) development of public code | ||
* d. drawing attention to problems ascertained and giving advice with regard to the public code they use | ||
* e. everything related to or conducive to the above, all in the broadest sense | ||
|
@@ -76,12 +73,10 @@ This distinguishes it from organizations providing open source codebase stewards | |
[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. | ||
* We are controlled by our members, who are wholly publicly controlled organizations. | ||
* We strive to keep our membership as accessible as possible to potential members, regardless of size or location. | ||
* We publish under licenses approved by the [Open Source Initiative](https://opensource.org/licenses) or [Creative Commons](https://creativecommons.org/licenses/) licenses that do not limit commercial reuse. | ||
* We are committed to working with other organizations (commercial or non-profit) to achieve our mission. | ||
* We prioritize long term sustainability and growth for the benefit of our members. | ||
* Our work is open by default and welcomes contributions. | ||
* We prioritize long term sustainability for the benefit of the communities we work with. | ||
|
||
[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. | ||
|
@@ -95,49 +90,48 @@ These words signify the qualities we strive for in our activities, products, sta | |
|
||
## 3. Policy and plan of work | ||
|
||
This policy plan covers the period between 2022 and 2027. | ||
This policy plan covers the period between 2024 and 2030. | ||
We’ve divided this into three phases, each containing separate activities. We are currently on track for Phase 1. | ||
|
||
### Phase 1: Short term (2022) | ||
### Phase 1: Short term (2024) | ||
|
||
* Increase awareness and illustrate the value of public code by further developing knowledge assets, such as explainer videos, case studies, testimonials, business cases, online learning platform, as well as host a conference for public code. | ||
* Increase awareness and illustrate the value of public code by further developing knowledge assets, such as process codes, explainer videos, case studies, testimonials, business cases, online learning platform, as well as host a conference for public code. | ||
* Scale the impact of codebase stewardship through continued support to existing codebases in stewardship, working towards stewardship of at least an international codebase, aiming for certificated maturity of at least one codebase, and publishing community translations of the Standard for Public Code. | ||
* Strengthen and diversify our collaborations, including involvement of our strategic council in the development of the roadmap, creating partnerships and getting additional members. | ||
* Continue to secure the organization's sustainability by ensuring additional philanthropic support, public contributions to our mission in forms other than membership dues, improving the transparency and openness of our internal processes, and laying the groundwork for building an international organization. | ||
* Establish a strategic council. | ||
* Strengthen and diversify our collaborations, including involvement of our strategic council in the development of the roadmap and creating partnerships with public organizations. | ||
* Transform our organizational model to include an umbrella organization focused on global long term priorities, and local chapter organizations tailoring their work based on the needs of the local public code ecosystem and participating public organizations. | ||
* Continue to secure the organization's sustainability by ensuring additional philanthropic support, financial and in-kind contributions from public organisations, and improving the transparency and openness of our internal processes. | ||
|
||
### Phase 2: Mid term (2023 - 2024) | ||
### Phase 2: Mid term (2025 - 2027) | ||
|
||
* Support others in applying public code knowledge assets in their organizations and communities, through the further diversification and professionalization of knowledge and media assets, online learning materials, and in-person events. | ||
* Support others in applying public code knowledge assets in their organizations and communities, through the further diversification and professionalization of process codes, knowledge and media assets, online learning materials, and in-person events. | ||
* Grow and internationalize communities around stewarded codebases by training others to independently apply stewardship practices to codebases. | ||
* Support public organizations to implement public code as a strategic priority for their organization, mainstreaming public code into their operations, with the Foundation for Public Code as a cornerstone of their strategy. | ||
* Transition towards a predominantly publicly funded organization and consolidating our international reach. | ||
* Have a strong network of supportive, international partnerships with diverse organizations. | ||
* Have chapters in 3 to 5 geographical regions, each enjoying broad political and financial support in their respective region. | ||
|
||
### Phase 3: Long terms (2025 - 2027) | ||
### Phase 3: Long terms (2027 - 2030) | ||
|
||
* Mainstream capacity building around public code as professional development, including the spin off of training provided by other organizations based on our materials and certification process, as well as the establishment of a community of practice. | ||
* Mainstream capacity building around public code as professional development, including the spin off of training provided by other organizations based on our process codes, materials, and certification process, as well as the establishment of a community of practice. | ||
* Enable global scale of stewardship by stewarding the top-of-class codebases in strategic public functions, and supporting other organizations to execute codebase stewardship. | ||
* Widespread adoption of public code as a strategic priority for public organizations, enabled by a diverse set of publicly owned organizations that steward codebases. | ||
* Fully publicly funded organizations able to operate in all time zones, and with regional experts. | ||
* Fully publicly funded chapter organizations in most geographical regions, able to operate in all time zones, and with regional experts. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fully publicly funded seems ambitious! |
||
|
||
## 4. The assets and fundraising | ||
|
||
### 4.1 Fundraising | ||
|
||
The Foundation for Public Code’s income and assets come primarily from: | ||
|
||
* membership dues | ||
* donations and gifts | ||
* philanthropic donations and gifts | ||
|
||
The association’s income and assets enable it to achieve its mission. | ||
In line with its mission, the Foundation for Public Code spends its income on codebase stewardship and to support the public code ecosystem. | ||
|
||
Our current budgetary goals are to raise €3 million for phase 1 and 2, so that we can meet our expected level of expenditure. | ||
Please note that the Foundation for Public Code will not actively pursue donations and gifts and will spend no or very limited time on fundraising (not more than 5% of its budget). | ||
|
||
### 4.2 Asset management | ||
|
||
We expect membership dues will be paid at the end of each calendar year. | ||
In order to ensure the continuity of the association and its work (especially since we specifically focus on putting codebases on sustainable footing), we have a financial objective to keep enough financial reserves to find viable alternative stewardship for public code that organizations rely on. | ||
In practice we expect to not keep more than the cash equivalent of 36 months’ of projected costs in the association’s bank account. | ||
|
||
|
@@ -168,9 +162,8 @@ The annual accounts will be drawn up and signed by the board of directors (bestu | |
|
||
The members of the board of directors for the Foundation for Public Code are: | ||
|
||
* B. Cerveny: Chair | ||
* B.H. van Hoytema: Secretary | ||
* E. Herman: Treasurer | ||
* B. Cerveny: Chair & Secretary | ||
* Richard Pope: Treasurer | ||
|
||
## 7. Publication | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.