Notes from the Standard for Public Code community call - 1 April 2021
Attendees
Updates from the Foundation
- Version 0.2.1 of the Standard for Public Code has been released
- Signalen has been replicated by ‘s-Hertogenbosch (live site)
- Signalen had a community day
Notes
In this call we gave a thorough introduction to the Foundation of Public Code and how we work. Then we moved on to the long backlog of open issues in the Standard for Public Code repository and worked through them from oldest to newest. This is the result of our pruning, which is also reflected in the GitHub repository:
- #38: Standardise terms for policy, civic code etc - closed
- #47: Add vendor and platform independence as a criterion - remains open, good topic for a community call
- #62: Bundle policy and code: invite policy makers to contribute their own work in their own formats - remains open
- #135: Template: reorder the headers - added comment, may close if no additional response is given
- #140: Intro: incubation/attic introduced without context - closed
- #146: Requirement for version control, commit with an email adress - remains open, good first issue
- #148: Requirement for CD testing: have open results - remains open, good first issue
- #153: URL and Title mismatches - remains open
- #155: We now lay out tests for ‘SHOULD’ requirements - added comment, may close if no additional response is given
- #157: Style: align verbs in does/doesn’t ? - remains open, plan follow-up
- #162: Including examples in the standard - remains open, good topic for a community call