Eric Herman
Eric Herman
Digital Public Goods is defined by [unicef/publicgoods-candidates](https://github.com/unicef/publicgoods-candidates/blob/main/README.md) as *open source software, open data, open AI models, open standards and open content that adhere to privacy and other applicable best practices,...
fixes: #645 and fixes #669 We discussed splitting the requirement: > * All policy and source code that the codebase is based on MUST be > documented, reusable and portable....
Rather than state a requirement permissively when it is not desired, change the phrasing to constrain/limit undesirable actions. fixes: #681 ----- [View rendered criteria/open-standards.md](https://github.com/publiccodenet/standard/blob/open-standards-may-to-must-not/criteria/open-standards.md)
"All policy and source code that the codebase is based on MUST be documented, reusable and portable."
The criterion [Make contributing easy](https://github.com/publiccodenet/standard/blob/develop/criteria/make-contributing-easy.md) contains the requirements: * The codebase MUST have a public issue tracker that accepts suggestions from anyone. * The codebase MUST have communication channels for...
The "Bundle policy and source code" criterion include the requirement: * All policy and source code that the codebase is based on MUST be documented, reusable and portable. When thinking...
The criterion [Make contributing easy](https://github.com/publiccodenet/standard/blob/develop/criteria/make-contributing-easy.md) has two related requirements, however the nuance between them lacks clarity: * The codebase MUST include instructions for how to privately report security issues for...
What's the minimum the Standard for Public Code should require of a codebase with regards to marketing? Is it something like, "MUST have a unique enough name that it is...
The standard requires that the code be FOSS, but what about the test suites? The build scripts? Standard should at least include guidance to use FOSS tools and to prefer...
Standard does not seem to provide guidance/expectations on documentation at: * the function level * the architectural level * the API level There is no guidance around some notion of...