- Standard - nextcloud-publiccode.maadix.org

The Standard is a finalist in the OSOR Community Awards
by Jan Ainali 04 Oct '23

04 Oct '23

Hurray! The European Commission's Open Source Observatory (OSOR) is giving out awards to public sector solutions and initiatives. The Standard for Public Code has been selected as one of the 22 finalists for the Community Awards. You can vote at https://joinup.ec.europa.eu/collection/open-source-observatory-osor/osor-co… Best, Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

1 0

Release 0.7.1
by Jan Ainali 31 Jul '23

31 Jul '23

Hello, Today we released 0.7.1 of the Standard for Public Code. The sixteenth draft changes the name of a criterion and clarifies references to code. - The criterion "Make the codebase reusable and portable" was renamed from "Create reusable and portable code". - Added a glossary entry for "Source Code". - References to "code" which only applied to "source code" now reference "source code" explicitly. - Clarification of "running code" as "software". - Minor changes to clarify "code" vs "codebase". - Simplify guidance to policy makers in Bundle policy and source code. - Clarify How to test sections of Make the codebase findable and Make the codebase reusable and portable. - Add a criteria and requirements checklist to the release artifacts. - Increase automation of the release process. Best regards, Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

1 0

New badge to advertise commitment
by Jan Ainali 19 Jul '23

19 Jul '23

Hello, Yesterday we made a badge that can be used in your repository (or anywher really) to advertise that it has made a commitment to adhere to the Standard for Public Code. You can see it in use in the repository of the Standard itself, along with a brief usage guide. https://github.com/publiccodenet/standard -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

3 3

Codebases implementing public policy
by Jan Ainali 02 Jun '23

02 Jun '23

Hello, In our effort to find the best practices in bundling policy and code, we are looking for examples of codebases that are implementing policies and how this is referred to inside their repository. If you know of any, please reply with a link to the repository and a sentence or two on where to look for the policy connection. Thank you, Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

2 1

Release 0.7.0
by Jan Ainali 31 May '23

31 May '23

May 31st 2023: [image: bookmark_tabs] the fifteenth draft adds new requirements for documenting review funding and clarifies review process requirement. - Add requirement to document who is expected to cover the cost of reviewing contributions. - Add requirement to have a short description of the codebase. - Change the focus of contributions adhering to standards to focus on the review of contributions. - Relaxed MUST requirements to SHOULD in Make the codebase findable. - Review template now in HTML format. - Introduction converted to foreword. - Improved contributing guidelines. - Improved documentation of scripts. -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

1 0

Release 0.6.0
by Jan Ainali 01 May '23

01 May '23

April 20th 2023: [image: twisted_rightwards_arrows] the fourteenth draft adds new requirements for portability and tests and an introduction to each criterion. - New requirement in Create reusable and portable code about the development being a collaboration between multiple parties. - New requirement in Create reusable and portable code about being dependent on a single vendor. - New requirement in Use continuous integration about publishing results for automated tests. - Differentiating the two requirements about security to clearly be about providing a method and having documentation about it. - Rephrased requirements to focus on the codebase rather than contributor behavior. - Removed the sections Why this is important and What this does not do and replaced with an introduction in each criterion. - Added general What this does not do section in the introduction of the Standard. - Added guidance for public policy makers about related policies and license compatibility. - Added guidance for developers and designers about version controlling files. - Clarified guidance for developers and designers about prompt responses and search engine optimization. - Added Further reading about accessibility. - Aligned criteria URLs with criteria names. - Improved navigation in the web version. - Moved tools in Further reading sections to the community implementation guide. - Moved compliance or certification process to publiccode.net. - Change format of the review template to make it easier to update after a new release. - Improved the text on the landing page and added links to related resources. - Added spell checker automated test. - Made minor changes to text for clarity and consistency. - Moved SPDX headers to yaml header. Find related assets (pdf, epub, review template) at: https://github.com/publiccodenet/standard/releases/tag/0.6.0 -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

1 0

Release 0.5.0!
by Jan Ainali 26 Jan '23

26 Jan '23

January 25th 2023: 🎨 the thirteenth draft focuses on documenting style guidelines. Adjust the coding style requirement to focus on the codebase using a style guide rather than contributor behavior. Moved requirement for codebase names to Make the codebase findable from Use plain English. Moved requirement about testing the code by using examples to Use continuous integration from Document the code. Split requirement about machine testable standards to clarify that open is more important than testable. Adjust how to test findability requirements to be less reliant on search engine algorithms. Made minor changes to text for clarity and consistency. Find related assets (pdf, epub, review template) at: https://github.com/publiccodenet/standard/releases/tag/0.5.0 -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

1 0

Implementation guide - Standard for Public Code Community Call (6 October)
by Jan Ainali 29 Sep '22

29 Sep '22

Hello! The next Standard for Public Code community call will be held on Thursday, 6 October, 13.00 (UTC). Video call-in link: https://meet.publiccode.net/StandardforPublicCode <https://meet.publiccode.net/StandardforPublicCode> Recently, we released an implementation guide for the Standard for Public Code. The aim is for people to share their experiences and choices they made, demonstrating different possible ways to meet the criteria. In the call, we will present the guide, listen to questions, and collect your ideas on how it can be even more useful for you. 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

1 0

Fwd: New release: version 0.4.0
by Jan Ainali 21 Sep '22

21 Sep '22

(Resending announcement from September 8 that was lost to the list.) Hello, Yesterday we released a new version of the Standard for Public Code. There are many changes in this release, and the one we like to highlight is a new criterion for making the codebase findable. You'll find the full changelog, and the new pdf, on https://github.com/publiccodenet/standard/releases/tag/0.4.0 -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

Mailing list problems
by Jan Ainali 21 Sep '22

21 Sep '22

Hello! For some time, possibly a few weeks, our mailing list was not accepting emails properly. This unfortunately led to a swath of duplicates today. I am sorry for that. If you have sent any email to the mailing list recently and had it bounce, you should now be able to resend it again. Best, Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 0

2023

2022

2021

2020

Standard