Notes from the Standard for Public Code community call - 4 February 2021
Updates from the Foundation
- Signalen is incubation for the Standard for Pubic Code
- Signalen and OpenZaak’s assessments are both updated to the v.0.2.1 of the template
- Our podcast is back! Check out Let’s talk about public code #3 - Sergei Maertens and Tjerk Vaags, OpenZaak
- We’ll be at a lot of upcoming events:
- A panel discussion on OSPOs at Open Forum Europe’s Open Source Policy Summit
- A FOSDEM talk on Contributing (with) civil servants
- Lightning talks at FOSS Backstage:
Proposed for this call
This community call was full of sharing visions of the future with a lot of ideas, and bouncing them back and forth. Here’s a summary of what we currently believe certification will look like for codebases that meet the Standard for Public Code.
The Foundation for Public Code will store compliance information for every version of all codebases that are (or have ever been) compliant with the Standard. Technically, this will be done by saving the hashes of the relevant commits, proving that a specific state of the codebase is certified by the Foundation for Public Code. A service will be set up that can respond to a query with a commit hash by stating if it is compliant or not, making it possible to display a verifiable digital badge.
We also discussed if the required explanations for any SHOULD requirements that are not met should be discoverable through this verification, but didn’t come to a conclusion.
Another point of discussion was dashboards of various kinds. One would be for our organization, to display where we list the codebases we work with at publiccode.net. The other kind could be used by the community of the codebase. We didn’t get too deep in these discussions, but noted that there is potential value in these ideas.
As a sidenote we also discussed the process to become certified, and to stay compliant during continuous development. For both of these processes we came back to our expectation that for the time being, we are most likely to do this in close collaboration with known codebases during stewardship. Therefore, it is in the regular line of work of the codebase stewards to make sure it is all as smooth as possible for the community.
Finally we are all quite eager to see codebases move towards certification, but do believe we are still a bit away and that we still have time to discuss and iterate on this. If you have any opinions, please comment on this issue.