2 March 2023 Standard for Public Code community call notes
- Jan Ainali
- Eric Herman
- Martin Dias d’Ullois
- Johan Groenen
News from the Foundation for Public Code
- New release for the Governance game, version 1.0.2
- We will have a session at MozFest: In 2030, governments only use open source: a thought experiment
When we recently changed the “Why this is important” section to instead become an introduction to each criterion, we also noted that many of the “What this does not do” sections did not add a lot of value to the reader, and so we created the issue Review “What does this not do” sections #813.
Our first review inspired us to make some additions to the introductions, since some sections had high level insights in them. With that done, we felt it would be best to remove the “What this does not do” section completely, as the little value that was once only there had been added to the wider context instead.
During the call, there were additional insights from Johan and Martin.
It was observed that since many of the “What this does not do” bullet points refer to other criteria, those that are not linked in such a way collectively sum up “What the Standard for Public Code does not do”. A unified section with that theme would fit well in the introduction.
It was also noted that unrelated to specific criteria, there are some misconceptions about the Standard for Public Code worth addressing there, for instance, that the Standard for Public Code should have any opinions about specific implementations of a codebase. This section could also be a place for us to differentiate the Standard for Public Code from other standards (we already have issues on this topic).
As we are planning to reframe some of the text in the introduction, which this suggestion aligns well with, we will bring this new idea into that work.