Hello!
The next Standard for Public Code community call will be held on Thursday,
7 April, 13.00 (UTC).
Video call-in link: https://meet.publiccode.net/StandardforPublicCode
First, we want to discuss if the Standard for Public Code should have
requirements or guidelines about software architecture and modularity of
the codebase. And if we incorporate that, how could it be phrased and where
in the standard would it fit? Could we perhaps be inspired by the ISO 25010
standard?
As our second point, we have a suggestion
<https://github.com/publiccodenet/standard/pull/602> to change the
subjective and hard to test requirement “Contributions MUST be small.” to
instead require guidelines about contributions.
If you cannot participate in this specific call but have any questions,
feel free to reply to this email.
Preliminary agenda. <https://hackmd.io/-OegeqvoThCbAsw3c3gIjw>
We look forward to seeing you on the call!
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello!
We just made a new release
<https://github.com/publiccodenet/standard/releases/tag/0.2.3>, here is the
changelog:
March 15th 2022: [image: scroll] the ninth draft allows English summaries
of policy lacking an official translation.
- Relax the criterion Use plain English by adding a new requirement that
allows bundled policy not available in English to have an accompanying
summary in English instead of translating the full text.
- Similarly, allow for English summaries for policies not available in
English in Bundle policy and code.
- Clarify that term 'policy' includes processes which impact development
and deployment in Bundle policy and code.
- Emphasize reusability also on parts of the solutions in Create
reusable and portable code.
- Expand guidance to Developers and designers in Create reusable and
portable code about deploying to proprietary platforms.
- Add nuance to use of non-English terms in what management need to do
in Use plain English.
- Change the pull request process diagram to use Mermaid instead of BPMN
to make it community translations easier.
- Added Maurice Hendriks to AUTHORS.
- Add on OpenAPI Specification to further reading.
- Made the attributions in further reading sections clearer.
- Made additional minor changes to text for clarity.
You can find the printed version here:
https://github.com/publiccodenet/standard/releases/download/0.2.3/standar...
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net