Hello,
Last week we launched the implementation guide!
It's meant to be a community built resource for anyone trying to implement
the Standard for Public Code.
Read more in our announcement here:
https://blog.publiccode.net/news/2022/09/13/launching-community-built-imple…
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello,
Last week we launched the implementation guide!
It's meant to be a community built resource for anyone trying to implement
the Standard for Public Code.
Read more in our announcement here:
https://blog.publiccode.net/news/2022/09/13/launching-community-built-imple…
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello!
We are aiming to make the next release on 7 September.
This will have a bump to v.0.4.0, mainly since we're introducing a new
criterion about findability.
The changes that currently would be included can be seen in this comparison
of branches:
https://github.com/publiccodenet/standard/compare/main...develop
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello,
For a long time, we have been thinking that the Code of Conduct we chose
for the Standard for Public Code was not exactly what we wanted. So now we
are proposing a new Code of Conduct.
The main features are that it is tailored for our audience, it's licensed
CC 0 (like the standard) and it is very concise.
Check it out on https://github.com/publiccodenet/standard/pull/643
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello list!
Based on a community call that arose from issue #254 we have a pull request
with a proposal for an entirely new criterion in the Standard for Public
Code. We would appreciate comments or suggestions here or on the pull
request.
https://github.com/publiccodenet/standard/pull/630
Thanks,
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello!
The next Standard for Public Code community call will be held on Thursday,
7 July, 13.00 (UTC).
Video call-in link: https://meet.publiccode.net/StandardforPublicCode
<https://meet.publiccode.net/StandardforPublicCode>
More and more organizations are looking to use the Standard for Public
Code. Considering that it is still not released in a 1.0 version, to
radiate intent and give an insight of where it is going, we should create a
public roadmap for it. What are the next steps and when will we consider it
to be ready for a major version increase? (This is also discussed in issue
#292 <https://github.com/publiccodenet/standard/issues/292>.)
If you cannot participate in this specific call but have any questions or
opinions, feel free to reply to this email or comment on the issue above.
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!
I am happy to announce that we just released version 0.3.0.
The bump of minor version is due to a new requirement for localization and
strengthening of the requirements for documentation of governance.
Find complete release notes and downloadable PDF at
https://github.com/publiccodenet/standard/releases/tag/0.3.0
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
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/standard-…
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net