├── .github └── workflows │ └── main.yml ├── archiving.md ├── docs ├── pull_request_template.md └── standard-badge.svg ├── openstand.md ├── endorsement.md ├── standard.md ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md ├── README.md ├── governance.md ├── standard-questions.md └── LICENSE /.github/workflows/main.yml: -------------------------------------------------------------------------------- 1 | # The only reason this CI exists is that we can require branches to be up 2 | # to date before merging, which can only be enforced if there is at least 3 | # one status check enabled. 4 | 5 | name: Dummy CI 6 | 7 | on: 8 | push: 9 | pull_request: 10 | 11 | jobs: 12 | dummy: 13 | runs-on: ubuntu-latest 14 | 15 | steps: 16 | - uses: actions/checkout@v2 17 | - name: Dummy action 18 | run: echo dummy -------------------------------------------------------------------------------- /archiving.md: -------------------------------------------------------------------------------- 1 | # Archiving Policy 2 | 3 | In June 2022, the DPGA introduced the concept of "archiving" to the DPG Registry. 4 | 5 | As of this date, nominated solutions that are inactive or do not provide the required documentation needed for review within 90 days of outreach will be moved into an "archived" state. Archived solutions can still be queried, and solutions can move from the archive to an active state by providing the information demonstrating that all requirements of the DPG Standard must be met. 6 | 7 | Once a year, all digital public goods will have their documentation re-reviewed by the DPGA to ensure requirements are still met. Nominees have not yet been reviewed against the DPG Standard, or may currently be undergoing review. Digital solutions that are no longer active, or do not provide the required documentation needed for review, will be moved into the archive. 8 | -------------------------------------------------------------------------------- /docs/pull_request_template.md: -------------------------------------------------------------------------------- 1 | 2 | Fixes # . 3 | 4 | ## Changes proposed in this pull request: 5 | - 6 | - 7 | - 8 | 9 | ## Propagation of Changes 10 | 11 | Identify where of the following the proposed changes need to be propagated, and include the relevant pull request where appropriate: 12 | 13 | - [ ] The DPGA website contains https://digitalpublicgoods.net/standard/ which needs to be updated manually matching the contents of [standard.md](https://github.com/DPGAlliance/DPG-Standard/blob/master/standard.md). 14 | - [ ] The DPGA website also contains the [submission guide](https://digitalpublicgoods.net/submission-guide/) which needs to be updated manually. 15 | - [ ] The DPG application [webapp admin panel](https://app.digitalpublicgoods.net/login) which will be updated manually. 16 | - [ ] The [Eligibility Form](https://digitalpublicgoods.net/eligibility/) through the [unicef/publicgoods-scripts](https://github.com/unicef/publicgoods-submission) repository, by editing [quizQuestions.js](https://github.com/unicef/publicgoods-scripts/blob/master/packages/eligibility/src/api/quizQuestions.js) 17 | 18 | -------------------------------------------------------------------------------- /openstand.md: -------------------------------------------------------------------------------- 1 | ### **Joint IEEE, ISOC, W3C, IETF and IAB Definition** 2 | 3 | On August 12, 2012, the [Institute of Electrical and Electronics Engineers](https://en.wikipedia.org/wiki/Institute_of_Electrical_and_Electronics_Engineers) (IEEE), [Internet Society](https://en.wikipedia.org/wiki/Internet_Society) (ISOC), [World Wide Web Consortium](https://en.wikipedia.org/wiki/World_Wide_Web_Consortium) (W3C), [Internet Engineering Task Force](https://en.wikipedia.org/wiki/Internet_Engineering_Task_Force) (IETF) and [Internet Architecture Board](https://en.wikipedia.org/wiki/Internet_Architecture_Board) (IAB), jointly affirmed a set of principles which have contributed to the [exponential growth](https://en.wikipedia.org/wiki/Exponential_growth) of the Internet and related technologies. The "OpenStand Principles" define open standards and establish the building blocks for innovation.[[5]](https://en.wikipedia.org/wiki/Open_standard#cite_note-5)[[6]](https://en.wikipedia.org/wiki/Open_standard#cite_note-6) Standards developed using the OpenStand principles are developed through an open, participatory process, support interoperability, foster global competition, are voluntarily adopted on a global level and serve as building blocks for products and services targeted to meet the needs of markets and consumers. This drives innovation which, in turn, contributes to the creation of new markets and the growth and expansion of existing markets. 4 | 5 | **There are five, key OpenStand Principles, as outlined below:** 6 | 7 | ### 1. Cooperation 8 | 9 | Respectful cooperation between standards organizations, whereby each respects the autonomy, integrity, processes, and intellectual property rules of the others. 10 | 11 | ### 2. Adherence to Principles 12 | 13 | Adherence to the five fundamental principles of standards development, namely 14 | 15 | - **Due process:** Decisions are made with equity and fairness among participants. No one party dominates or guides standards development. Standards processes are transparent and opportunities exist to appeal decisions. Processes for periodic standards review and updating are well defined. 16 | - **Broad consensus:** Processes allow for all views to be considered and addressed, such that agreement can be found across a range of interests. 17 | - **Transparency:** Standards organizations provide advance public notice of proposed standards development activities, the scope of work to be undertaken, and conditions for participation. Easily accessible records of decisions and the materials used in reaching those decisions are provided. Public comment periods are provided before final standards approval and adoption. 18 | - **Balance:** Standards activities are not exclusively dominated by any particular person, company or interest group. 19 | - **Openness:** Standards processes are open to all interested and informed parties. 20 | 21 | ### 3. Collective Empowerment 22 | 23 | Commitment by affirming standards organizations and their participants to collective empowerment by striving for standards that: 24 | 25 | - are chosen and defined based on technical merit, as judged by the contributed expertise of each participant; 26 | - provide global interoperability, scalability, stability, and resiliency; 27 | - enable global competition; 28 | - serve as building blocks for further innovation; and 29 | - contribute to the creation of global communities, benefiting humanity. 30 | 31 | ### 4. Availability 32 | 33 | Standards specifications are made accessible to all for implementation and deployment. Affirming standards organizations have defined procedures to develop specifications that can be implemented under fair terms. Given market diversity, fair terms may vary from royalty-free to [fair, reasonable, and non-discriminatory](https://en.wikipedia.org/wiki/Fair,_reasonable,_and_non-discriminatory) terms (FRAND). 34 | 35 | ### 5. Voluntary Adoption 36 | 37 | Standards are voluntarily adopted and success is determined by the market. 38 | -------------------------------------------------------------------------------- /endorsement.md: -------------------------------------------------------------------------------- 1 | # Endorsement of the Digital Public Goods Alliance Standard 2 | 3 | This is a list of open source, open content and open data advocacy and advancement experts 4 | supporting the [Digital Public Goods Alliance Standard](standard.md). Endorsement means agreement 5 | with the standard for Digital Public Goods set out through the indicators, and a willingness to 6 | have your name and title publicly listed as having contributed to and endorsing the standard. 7 | 8 | *Note: attribution to this endorsement is explicitly made by the individual, not their organization.* 9 | 10 | ### Endorse the standard 11 | 12 | Two ways to endorse the standard: 13 | 14 | 1. Add your name to the list and endorse the standard by editing this file and submitting a Pull Request directly from your browser. 15 | 2. Complete [this form](https://forms.gle/knVvbv4mLfxkHtFS8) and we'll add you to the endorsement list. 16 | 17 | ## Endorsement List 18 | 19 | *Note: the list is sorted alphabetically by last name* 20 | 21 | Full Name | Title | Organization 22 | --- | --- | --- 23 | [Sean Blaschke](https://github.com/seanblaschke) | Technology for Development Business Analyst, UNICEF Eastern and Southern Africa Regional Office | [UNICEF](https://www.unicef.org/) 24 | [Fabien Benetou](https://fabien.benetou.fr) | UNICEF Innovation Fund WebXR technical advisor, European Parliament Innovation lab WebXR consultant | UNICEF, European Parliament 25 | [Edward Cable](https://www.linkedin.com/in/edcable/) | President/CEO, The Mifos Initiative | [The Mifos Initiative](https://mifos.org) 26 | [Michael Downey](https://floss.social/@downey) | Free & open source software advocate & consultant | 27 | [Justin W. Flory](https://jwf.io) | Open Source Technical Advisor, UNICEF Office of Innovation | [UNICEF Innovation Fund](https://unicefinnovationfund.org/) 28 | [Matt Germonrez](https://github.com/germonprez) | Professor, College of Information Science & Technology at University of Nebraska at Omaha | [CHAOSS](https://chaoss.community/) 29 | [Sean P. Goggins](https://github.com/sgoggins) | Professor, College of Engineering at University of Missouri | [CHAOSS](https://chaoss.community/) 30 | [Victor Grau Serrat](https://github.com/lacabra) | Technical Lead, UNICEF Office of Innovation | [UNICEF](https://www.unicef.org/innovation/) 31 | [Cable Green](https://github.com/cablegreen) | Director of Open Education, Creative Commons | [Creative Commons](https://creativecommons.org/) 32 | [Christer Gundersen](https://github.com/christer-io) | Technical Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) 33 | [Haiting Han](https://ifro.ku.dk/english/staff/staffproduction/?pure=en/persons/669864) | PhD fellow | University of Copenhagen 34 | [Lucy Harris](https://github.com/lucyeoh) | Secretariat Co-Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) 35 | [Georg J.P. Link](https://github.com/GeorgLink) | Open Source Strategist | [CHAOSS](https://chaoss.community/) 36 | Jon Lloyd | Director of Campaigns at Mozilla Foundation | [Mozilla Foundation](https://foundation.mozilla.org/en/) 37 | [Don Marti](https://github.com/dmarti) | VP, Ecosystem Innovation | [CafeMedia](https://cafemedia.com/) 38 | [Martin Mbaga](https://www.linkedin.com/in/martinmbaga)| Senior Digital For Development Expert | [Impalabridge](https://twitter.com/Impalabridge) 39 | [Liv Marte Nordhaug](https://github.com/livmarte) | Secretariat Co-Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) 40 | [Cliff Schmidt](https://www.linkedin.com/in/cliffschmidt/) | Executive Director, Amplio Network | [Amplio Network](https://www.amplio.org/) 41 | [Sudhanshu Shekhar](https://www.linkedin.com/in/sudshekhar02/) | Fellow, iSPIRT |[iSPIRT](https://ispirt.in/) 42 | [Surendrasingh Sucharia](https://github.com/surendrasinghs) | Product and Growth Lead, EkStep; Chief Evangelist for [Sunbird](https://sunbird.org) | [EkStep Foundation](https://ekstep.org) 43 | [Bodhish Thomas](https://www.linkedin.com/in/bodhish/) | Chief Network Architect, Coronasafe Network | [Coronasafe Network](http://coronasafe.network/) 44 | [Dau Thuy Ha](https://www.linkedin.com/in/dauthuyha/) | Co-founder, CEO, The Online Management Training Company (OMT), Vietnam | [The Online Management Training Company (OMT), Vietnam](http://omt.vn) 45 | 46 | 47 | 48 | 49 | -------------------------------------------------------------------------------- /standard.md: -------------------------------------------------------------------------------- 1 | # Digital Public Goods Standard 2 | 3 | - **Version**: 1.1.4 4 | - **Last Update**: 2021-01-04 5 | - [View Changelog](https://github.com/DPGAlliance/DPG-Standard/blob/master/CHANGELOG.md) 6 | 7 | Indicator | Requirement 8 | --- | --- 9 | **1. Relevance to Sustainable Development Goals** | Digital public goods must demonstrate relevance to advancing the [Sustainable Development Goals (SDGs)](https://sdgs.un.org/goals). 10 | **2. Use of Approved Open Licenses** | Digital public goods must demonstrate the use of an approved open license. For open-source software, only [OSI approved licenses](https://opensource.org/licenses) are accepted. For open content collections the use of a [Creative Commons license](https://creativecommons.org/licenses/) is required. DPGs are encouraged to use a license that allows for both derivatives and commercial reuse ([CC-BY](https://creativecommons.org/licenses/by/4.0/) and [CC-BY-SA](https://creativecommons.org/licenses/by-sa/4.0/)), or dedicate content to the public domain ([CC0](https://creativecommons.org/choose/zero/)); licenses that do not allow for commercial reuse ([CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/) and [CC-BY-NC-SA](https://creativecommons.org/licenses/by-nc-sa/4.0/)) are also accepted. For open data, an [Open Data Commons approved license](https://opendefinition.org/licenses/) is required. See [The full license list](https://github.com/DPGAlliance/publicgoods-candidates/blob/main/help-center/licenses.md) for reference. 11 | **3. Clear Ownership** | Ownership of assets that the digital public good produces must be clearly defined and documented. For example, through copyright, trademark or other publicly available information. 12 | **4. Platform Independence** | When the digital public good has mandatory dependencies that create more restrictions than the original license, proving independence from the closed component(s) and/or indicating the existence of functional, open alternatives that can be used without significant changes to the core product is required. 13 | **5. Documentation** | Digital public goods require documentation of the source code, use cases, and/or functional requirements. For content collections, this should include all relevant/compatible apps, software, or hardware required to access the content collection, and instructions regarding how to use it. For software solutions, this should be technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For data projects, this should be documentation that describes all the fields in the set, and provides context on how the dataset was collected, and how it should be interpreted. 14 | **6. Mechanism for Extracting Data and Content** | Digital public goods with non-personally identifiable information (PII) design for possibility of extracting or importing non-PII data and content from the system in a non-proprietary format. 15 | **7. Adherence to Privacy and Applicable Laws** | Digital public goods must be designed and developed to comply with privacy and other applicable laws 16 | **8. Adherence to Standards & Best Practices** | Digital public goods must be designed and developed to align with relevant standards, best practices, and/or principles. For example,[the Principles for Digital Development](https://digitalprinciples.org/principles/). 17 | **9. Do No Harm By Design** | Digital public goods must be designed to anticipate, prevent, and do no harm by design. 18 | **9a) Data Privacy & Security** | Digital public goods that collect, store and distribute [personally identifiable (PII) data](https://github.com/DPGAlliance/publicgoods-candidates/tree/main/docs/help-center/personal-data-definition), must demonstrate how they ensure the privacy, security and integrity of this data in addition to the steps taken to prevent adverse impacts resulting from its collection, storage and distribution. 19 | **9b) Inappropriate & Illegal Content** | Digital public goods that collect, store or distribute content must have policies identifying inappropriate and illegal content such as child sexual abuse materials in addition to processes for detecting, moderating, reporting and removing inappropriate/ illegal content. 20 | **9c) Protection from Harassment** | If the digital public good facilitates interactions with or between users or contributors there must be a process for users and contributors to protect themselves against grief, abuse, and harassment. The project must have system(s) to address the safety and security of underage users. 21 | 22 | _NOTE: Evidence for requirements 7-9 can only be given by someone authorized to speak on behalf of the project. We collect title, name and contact information to confirm this authority._ 23 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Changelog 2 | All notable changes to this project will be documented in this file. 3 | 4 | The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), 5 | and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). 6 | 7 | ## [1.1.5] 2023-03-17 8 | 9 | ### Added 10 | 11 | - Add support for OpenStand ([#38](https://github.com/DPGAlliance/DPG-Standard/pull/38)) 12 | - Add mention of 'content to Indicator 6 ([#50](https://github.com/DPGAlliance/DPG-Standard/pull/50), [#100](https://github.com/DPGAlliance/DPG-Standard/pull/100)) 13 | 14 | ### Changed 15 | 16 | - Clarified language on DPGA's relationship to other organizations in the space ([#40](https://github.com/DPGAlliance/DPG-Standard/pull/40)) 17 | - Grammatical edits to governance.md ([#46](https://github.com/DPGAlliance/DPG-Standard/pull/46)) 18 | - Grammatical edits to standards.md ([#45](https://github.com/DPGAlliance/DPG-Standard/pull/45)) 19 | - Grammatical edits to README.md ([#47](https://github.com/DPGAlliance/DPG-Standard/pull/47)) 20 | 21 | ## [1.1.4] 2021-01-29 22 | 23 | ### Added 24 | 25 | - Added informational questions to the DPG Standard Questionary ([#31](https://github.com/DPGAlliance/DPG-Standard/pull/31)) 26 | - Added three new endorsements ([39446fa](https://github.com/DPGAlliance/DPG-Standard/commit/39446fa415f0260c5bd92e40aa37b16b52398551)) 27 | - Added a new endorsement ([#43](https://github.com/DPGAlliance/DPG-Standard/pull/43)) 28 | 29 | ## Changed 30 | 31 | - Renamed two indicators for clarity ([#41](https://github.com/DPGAlliance/DPG-Standard/pull/41)) 32 | - Updating the questions for indicator 7 as per #35 ([1088ec6](https://github.com/DPGAlliance/DPG-Standard/commit/1088ec6a94e3070c8ed8ecbe5f33cb179766384a)) 33 | 34 | ## [1.1.3] 2020-12-03 35 | 36 | ## Changed 37 | 38 | - Removed the word "source" when referring to "open source licenses", as the licenses and dependencies that we refer to are not only for "open source", but should be simply referred to "open licenses" ([#30](https://github.com/DPGAlliance/DPG-Standard/pull/26)) 39 | 40 | ## [1.1.2] 2020-11-16 41 | 42 | ### Changed 43 | 44 | - Added link to https://sdgs.un.org/goals where the Sustainable Development Goals are mentioned ([#26](https://github.com/DPGAlliance/DPG-Standard/pull/26)) 45 | - Added mention of GDPR and other regional privacy laws in the corresponding question, without altering the standard ([#20](https://github.com/DPGAlliance/DPG-Standard/pull/20)) 46 | 47 | ## [1.1.1] 2020-11-12 48 | 49 | ### Changed 50 | 51 | - Rewording of [standard-questions.md](https://github.com/DPGAlliance/DPG-Standard/blob/master/standard-questions.md) to align with the current submission form, and bring consistency. All very minor changes ([#25](https://github.com/DPGAlliance/DPG-Standard/pull/25)) 52 | 53 | ## [1.1.0] 2020-11-09 54 | 55 | ## Removed 56 | 57 | - Removed 9a ([#1](https://github.com/DPGAlliance/DPG-Standard/pull/1)) 58 | 59 | ## [1.0.5] 2020-10-22 60 | 61 | ### Changed 62 | 63 | - Rather than having "response time" as a separate question, included it in the request for description of the mechanism for detecting, reporting and (added) removing, inappropriate/illegal content ([#21](https://github.com/DPGAlliance/DPG-Standard/pull/21)) 64 | 65 | ## [1.0.4] 2020-10-20 66 | 67 | ### Changed 68 | 69 | - Changed language on `7. Adherence to privacy and applicable laws` to include clarifying statement on **to the best of its knowledge** ([#2](https://github.com/DPGAlliance/DPG-Standard/pull/2)) 70 | 71 | ## [1.0.3] 2020-10-20 72 | 73 | ### Added 74 | - Added documentation on how to release a new version 75 | 76 | ### Changed 77 | - Changed language on `9c) Inappropriate & Illegal Content` to include the mention of **removal** of inappropriate/illegal content ([#3](https://github.com/DPGAlliance/DPG-Standard/pull/3)) 78 | 79 | ## [1.0.2] 2020-10-20 80 | 81 | ### Changed 82 | - Clarified wording around CC licenses ([#11](https://github.com/DPGAlliance/DPG-Standard/pull/11)) 83 | 84 | ## [1.0.1] 2020-10-20 85 | 86 | ### Added 87 | - Added `standard-questions.md` ([#10](https://github.com/DPGAlliance/DPG-Standard/pull/10)) 88 | - Created `governance.md` ([#13](https://github.com/DPGAlliance/DPG-Standard/pull/13)) 89 | - Added `CHANGELOG.md` ([#14](https://github.com/DPGAlliance/DPG-Standard/pull/14)) 90 | 91 | ### Removed 92 | - Moved questions from section around online child safety into "9.d Protection from Harassment" where they belong ([#16](https://github.com/DPGAlliance/DPG-Standard/pull/16)) 93 | - Removed transparency section from `standard-questions.md` since that section is not present in the standard ([#17](https://github.com/DPGAlliance/DPG-Standard/pull/17)) 94 | 95 | ## [1.0.0] 2020-09-15 96 | 97 | ### Added 98 | - Released first version of the Digital Public Good Standard in consultation with a number of key stakeholders at the intersection of open source and social good. 99 | 100 | [1.1.4]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.1.3...v1.1.4 101 | [1.1.3]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.1.2...v1.1.3 102 | [1.1.2]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.1.1...v1.1.2 103 | [1.1.1]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.1.0...v1.1.1 104 | [1.1.0]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.5...v1.1.0 105 | [1.0.5]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.4...v1.0.5 106 | [1.0.4]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.3...v1.0.4 107 | [1.0.3]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.2...v1.0.3 108 | [1.0.2]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.1...v1.0.2 109 | [1.0.1]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.0...v1.0.1 110 | [1.0.0]: https://github.com/DPGAlliance/DPG-Standard/releases/tag/v1.0.0 111 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | 2 | # Contributor Covenant Code of Conduct 3 | 4 | ## Our Pledge 5 | 6 | We as members, contributors, and leaders pledge to make participation in our 7 | community a harassment-free experience for everyone, regardless of age, body 8 | size, visible or invisible disability, ethnicity, sex characteristics, gender 9 | identity and expression, level of experience, education, socio-economic status, 10 | nationality, personal appearance, race, religion, or sexual identity 11 | and orientation. 12 | 13 | We pledge to act and interact in ways that contribute to an open, welcoming, 14 | diverse, inclusive, and healthy community. 15 | 16 | ## Our Standards 17 | 18 | Examples of behavior that contributes to a positive environment for our 19 | community include: 20 | 21 | * Demonstrating empathy and kindness toward other people 22 | * Being respectful of differing opinions, viewpoints, and experiences 23 | * Giving and gracefully accepting constructive feedback 24 | * Accepting responsibility and apologizing to those affected by our mistakes, 25 | and learning from the experience 26 | * Focusing on what is best not just for us as individuals, but for the 27 | overall community 28 | 29 | Examples of unacceptable behavior include: 30 | 31 | * The use of sexualized language or imagery, and sexual attention or 32 | advances of any kind 33 | * Trolling, insulting or derogatory comments, and personal or political attacks 34 | * Public or private harassment 35 | * Publishing others' private information, such as a physical or email 36 | address, without their explicit permission 37 | * Other conduct which could reasonably be considered inappropriate in a 38 | professional setting 39 | 40 | ## Enforcement Responsibilities 41 | 42 | Community leaders are responsible for clarifying and enforcing our standards of 43 | acceptable behavior and will take appropriate and fair corrective action in 44 | response to any behavior that they deem inappropriate, threatening, offensive, 45 | or harmful. 46 | 47 | Community leaders have the right and responsibility to remove, edit, or reject 48 | comments, commits, code, wiki edits, issues, and other contributions that are 49 | not aligned to this Code of Conduct, and will communicate reasons for moderation 50 | decisions when appropriate. 51 | 52 | ## Scope 53 | 54 | This Code of Conduct applies within all community spaces, and also applies when 55 | an individual is officially representing the community in public spaces. 56 | Examples of representing our community include using an official e-mail address, 57 | posting via an official social media account, or acting as an appointed 58 | representative at an online or offline event. 59 | 60 | ## Enforcement 61 | 62 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 63 | reported to the community leaders responsible for enforcement by emailing 64 | [hello@digitalpubligoods.net](mailto:hello@digitalpublicgoods.net) or contacting 65 | [Lucy Harris](https://github.com/Lucyeoh). 66 | All complaints will be reviewed and investigated promptly and fairly. 67 | 68 | All community leaders are obligated to respect the privacy and security of the 69 | reporter of any incident. 70 | 71 | ## Enforcement Guidelines 72 | 73 | Community leaders will follow these Community Impact Guidelines in determining 74 | the consequences for any action they deem in violation of this Code of Conduct: 75 | 76 | ### 1. Correction 77 | 78 | **Community Impact**: Use of inappropriate language or other behavior deemed 79 | unprofessional or unwelcome in the community. 80 | 81 | **Consequence**: A private, written warning from community leaders, providing 82 | clarity around the nature of the violation and an explanation of why the 83 | behavior was inappropriate. A public apology may be requested. 84 | 85 | ### 2. Warning 86 | 87 | **Community Impact**: A violation through a single incident or series 88 | of actions. 89 | 90 | **Consequence**: A warning with consequences for continued behavior. No 91 | interaction with the people involved, including unsolicited interaction with 92 | those enforcing the Code of Conduct, for a specified period of time. This 93 | includes avoiding interactions in community spaces as well as external channels 94 | like social media. Violating these terms may lead to a temporary or 95 | permanent ban. 96 | 97 | ### 3. Temporary Ban 98 | 99 | **Community Impact**: A serious violation of community standards, including 100 | sustained inappropriate behavior. 101 | 102 | **Consequence**: A temporary ban from any sort of interaction or public 103 | communication with the community for a specified period of time. No public or 104 | private interaction with the people involved, including unsolicited interaction 105 | with those enforcing the Code of Conduct, is allowed during this period. 106 | Violating these terms may lead to a permanent ban. 107 | 108 | ### 4. Permanent Ban 109 | 110 | **Community Impact**: Demonstrating a pattern of violation of community 111 | standards, including sustained inappropriate behavior, harassment of an 112 | individual, or aggression toward or disparagement of classes of individuals. 113 | 114 | **Consequence**: A permanent ban from any sort of public interaction within 115 | the community. 116 | 117 | ## Attribution 118 | 119 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 120 | version 2.0, available at 121 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 122 | 123 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 124 | enforcement ladder](https://github.com/mozilla/diversity). 125 | 126 | [homepage]: https://www.contributor-covenant.org 127 | 128 | For answers to common questions about this code of conduct, see the FAQ at 129 | https://www.contributor-covenant.org/faq. Translations are available at 130 | https://www.contributor-covenant.org/translations. 131 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | [![CC BY-SA 4.0][cc-by-sa-shield]](LICENSE) 2 | [![Contributor Covenant][code-of-conduct-shield]](CODE_OF_CONDUCT.md) 3 | 4 | OpenStand Group Logo
5 | 6 |

7 | oss image 8 |

9 |

Digital Public Goods Standard

10 | 11 | The [Digital Public Goods Standard](standard.md) is a set of specifications and guidelines designed to maximize consensus about whether a project conforms to the definition of digital public goods set by the UN Secretary-General in the [2020 Roadmap for Digital Cooperation](https://www.un.org/en/content/digital-cooperation-roadmap/): *digital public goods must be open source software, open data, open AI models, open standards, and open content that adhere to privacy and other applicable laws and best practices, do no harm, and help attain the Sustainable Development Goals (SDGs).* 12 | 13 | The DPG Standard establishes a baseline that must be met in order to earn recognition as a digital public good by the [Digital Public Goods Alliance](https://digitalpublicgoods.net) (DPGA) and the broader community. The DPG Standard is an open project and therefore [open to contribution](standard.md). The DPGA supports the [5 Core Principles of OpenStand](openstand.md) in the development of the DPG Standard. We invite anyone who uses and benefits from the DPG Standard to [join our growing list of endorsers](endorsement.md). 14 | 15 | ## 🔎 Current Version 16 | 17 | [The DPG Standard](standard.md) is currently at version 1.1.4, published on Jan. 29, 2021; view the [changelog](https://github.com/DPGAlliance/DPG-Standard/blob/master/CHANGELOG.md). 18 | 19 | ## ✅ Application of the DPG Standard 20 | 21 | We encourage creators, maintainers, funders, implementers, and consumers to use this standard to recognize, assess, and support digital public goods. The standard is operationalized through a [questionary](https://app.digitalpublicgoods.net/form) that is required as part of the assessment process. We maintain a list of digital public goods that meet the DPG Standard described above on [our registry](https://digitalpublicgoods.net/registry). Projects are reviewed annually and archived if they do not continue to meet the Standard, as per our [archiving policy](archiving.md). 22 | 23 | ![Vetting Process](docs/process.svg) 24 | 25 | We apply the DPG Standard to projects that have either been [nominated directly](https://app.digitalpublicgoods.net/form) or have been pulled together from partnership databases. Projects that are submitted to our platform will undergo three stages of review to ensure they meet the requirements set in the DPG Standard. As a project undergoes various reviews it will move from **nominee** to a fully reviewed **digital public good**. 26 | 27 | Documentation submitted by candidates is transparently displayed on GitHub and can be [viewed here](https://github.com/unicef/publicgoods-candidates/pulls). If a project meets the DPG Standard it will be officially considered a digital public good and will appear as such in the DPG Registry, and may be eligible for additional recognition and support. 28 | 29 | ## 👍 Endorsements 30 | 31 | The DPG Standard is endorsed by [a growing list](endorsement.md) of open source, open content, and open data advocacy and advancement experts. Endorsement means agreement with the DPG Standard set through the indicators, and a willingness to have your name and title publicly listed as having contributed to and endorsing the DPG Standard. 32 | 33 | Add your endoresment by editing the [file](endorsement.md), and submitting a Pull Request or filling out [this form](https://forms.gle/knVvbv4mLfxkHtFS8). 34 | 35 | ## 🤗 Code of Conduct 36 | 37 | The DPGA is dedicated to building a welcoming, diverse, and safe community. We expect everyone participating in the DPGA community to abide by our [**Code of Conduct**](CODE_OF_CONDUCT.md). Please read it. Please follow it. In the DPGA, we work hard to build each other up and create amazing things together. 💪💜 38 | 39 | ## ⚖️ Governance 40 | 41 | At the DPGA, we envision a growing community of contributors and stakeholders around the DPG Standard in an open, transparent, and accessible manner. Our [governance](governance.md) documents the processes for welcoming, reviewing, and merging proposals for modifications to the DPG Standard and manages clear expectations around these processes. 42 | 43 | ## 🙏 Acknowledgements 44 | 45 | Thank you to all the individuals that contributed to and [endorsed](endorsement.md) the DPG Standard, as well as well as to the participants of the **Early Grade Reading Community of Practice**. We also thank the following organizations: UNICEF,iSPIRT, Government of Sierra Leone, Government of Norway, and the DPGA Secretariat. 46 | 47 | *Image Credit: [Badge](https://thenounproject.com/search/?q=seal+of+approval&i=32270) by André Luiz from [the Noun Project](http://thenounproject.com/), released under a CC license.* 48 | 49 | ## :memo: License 50 | 51 | This repository is primarily content, and it is licensed under a [Creative Commons Attribution ShareAlike 4.0 International License](LICENSE). 52 | 53 | [![CC BY-SA 4.0][cc-by-sa-image]](LICENSE) 54 | 55 | > This is a human-readable summary of (and not a substitute for) the license. 56 | > 57 | > You are free to: 58 | > * **Share** — copy and redistribute the material in any medium or format 59 | > * **Adapt** — remix, transform, and build upon the material for any purpose, even commercially. 60 | > 61 | > The licensor cannot revoke these freedoms as long as you follow the license terms. 62 | > 63 | > * **Attribution** — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. 64 | > * **ShareAlike** — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original. 65 | > 66 | > No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. 67 | 68 | [cc-by-sa-image]: https://licensebuttons.net/l/by-sa/4.0/88x31.png 69 | [cc-by-sa-shield]: https://img.shields.io/badge/License-CC%20BY--SA%204.0-lightgrey.svg 70 | [code-of-conduct-shield]: https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg 71 | -------------------------------------------------------------------------------- /governance.md: -------------------------------------------------------------------------------- 1 | # Digital Public Goods Standard Governance 2 | 3 | This is a work in progress. 4 | 5 | The purpose of this document is to share how the Digital Public Goods Alliance (DPGA) envisions engaging a growing community of contributors and stakeholders around the Digital Public Goods (DPG) Standard. Our goal is to balance responsiveness to feedback, with stability and predictabilty for the DPG Standard so it can be a framework that people can build for and to. 6 | 7 | The DPG Standard leverages frameworks, standards and definitions from specific organizations that have broad market consensus and are facilitating the discovery, development, use of, and investment in digital public goods. Specific organizations the DPG Standard aligns with include: Open Source Initiative (OSI) also member of the DPGA alliance, Creative Commons, and Open Data Commons. 8 | 9 | ## Principles 10 | 11 | The DPGA community adheres to the [OpenStand Principles](openstand.md) when developing the DPG standard. 12 | 13 | ## Code of Conduct 14 | 15 | We have adopted the [Contributor Covenant Code of Conduct v2](CODE_OF_CONDUCT.md), and expect all members of the 16 | community to embrace it. The following is an excerpt on our pledge: 17 | 18 | *We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.* 19 | 20 | *We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.* 21 | 22 | ## Revisions 23 | 24 | The following section showcases the processes for: 25 | * proposing modifications to the current version of the DPG Standard 26 | * reviewing proposed changes 27 | * incorporating proposed changes in forthcoming revisions 28 | 29 | The latest version of the [Digital Public Goods Standard](standard.md) is found in the root folder of this repository. 30 | The DPG Standard is operationalized through a [questionary](https://app.digitalpublicgoods.net/form). This set of questions is used to screen 31 | projects or products, and validate whether they conform to the DPG Standard, and can thus be classified as digital public goods. 32 | 33 | ### Priority 34 | 35 | Our priority for year 2023 is to establish a stable version of the DPG Standard that encompasses specific requirements for open standard, open data, open AI solutions. To do so, we ask for all comments and edits to be centered around the DPG Standard rather than the associated set of questions. The rationale being if the DPG Standard were to significantly change, so would the questionary, therefore any preliminary work on the questions may need to be discarded. 36 | 37 | ### Proposing Changes 38 | 39 | These are the suggested steps for proposing changes to the DPG Standard: 40 | - Start an issue: You can create [an issue](https://github.com/DPGAlliance/DPG-Standard/issues) to suggest changes and invite other community members to weigh in with their thoughts 41 | OR 42 | - Start a Pull Request 43 | - First, to avoid duplication, review the existing [Pull Requests](https://github.com/DPGAlliance/DPG-Standard/pulls) to see if your proposed change 44 | has already been proposed or not. If it has already been proposed, you are encouraged to add your perspective 45 | to the existing proposed change and argue for or against it with constructive and compelling arguments. 46 | - If none of the open pull requests address the issue you are proposing, 47 | [edit the standard](https://github.com/DPGAlliance/DPG-Standard/edit/master/standard.md) and open a new pull request with your edits, guided by the "**one issue, one pull request**" guideline. 48 | When opening a new pull request, be very explicit about the changes that you are proposing when making the case for your suggested changes. If your 49 | contribution is commentary or a general opinion, we will still review it, but we will deem it nonactionable and close it. 50 | - Once your pull request has been submitted, follow the discussion that ensues. 51 | 52 | ### Classification of Modifications 53 | 54 | In order to streamline the review of proposals, we will use the following classifications and labelling them accordingly: 55 | 56 | * [![](https://img.shields.io/badge/-minor_fix-c5def5)](https://github.com/DPGAlliance/DPG-Standard/pulls?q=is%3Apr+is%3Aopen+label%3A%22minor+fix%22) These 57 | are mostly stylistic edits that include, but are not limited to: correcting typographical errors, making gramatical edits, adding or removing clarifying 58 | statements with the aim of improving readibility, or facilitating understanding of the DPG Standard to the reader. These proposed changes do not alter the 59 | intended meaning of the existing indicators, nor introduce or remove key concepts. 60 | 61 | * [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change) These are modifications 62 | that alter the existing indicators in significant ways that have broader implications, but they do not challenge the purpose or scope of the DPG Standard. 63 | These may also include reorganization of the various sections of the DPG Standard, removing existing sections entirely, or adding new indicators to the DPG Standard. 64 | 65 | * [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) These involve 66 | fundamental or philosophical changes that challenge the purpose, scope, or very existence of the DPG Standard. 67 | 68 | ## Proposal Review 69 | 70 | The process for reviewing and accepting proposals varies depending on the classification of the proposal: 71 | 72 | * [![](https://img.shields.io/badge/-minor_fix-c5def5)](https://github.com/DPGAlliance/DPG-Standard/pulls?q=is%3Apr+is%3Aopen+label%3A%22minor+fix%22) After 73 | leaving a minimum of one week of accepting additional comments from other members of the community, the pull request requires 1 secretariat co-lead and 1 technical 74 | lead (see [Current Roles](#current-roles)) to review and approve the issue in order to accept and merge it. This review will happen on a rolling basis, there 75 | are monthly meetings to catch and address any outstanding issues. 76 | 77 | * [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change). The moderator will first assign it 78 | to a member of the DPGA for further investigation over a period of up to two weeks. That person will report and comment on the issue, documenting and exploring 79 | the implications of accepting or rejecting that change, and will open another period of up to two weeks for additional input from the community. We will inform 80 | the members of the [DPGA's Governance Board](https://digitalpublicgoods.net/governance/) (the Board) giving them an equal opportunity to comment. Reviewing these changes will happen quarterly. Consensus from the 2 co-leads and 2 technical leads 81 | (see [Current Roles](#current-roles)) will be required to accept or reject these proposals. 82 | 83 | * [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental). After validating the legitimacy of the 84 | proposal, we will open a consultation process with significant communities and stakeholders throughout the ecosystem, including all [endorsers](endorsement.md). 85 | The findings from this consultation process will be presented to the[DPGA's Governance Board](https://digitalpublicgoods.net/governance/) (the Board) , who will have a week to veto or ask for more time 86 | (where silence is implied consent). Consensus from the 2 co-leads and 2 technical leads (see [Current Roles](#current-roles)) will be required to 87 | either accept or reject the proposal. Reviewing these changes will occur twice per year during the first year, and yearly thereafter. 88 | 89 | ## Versioning 90 | 91 | All notable changes to this project will be documented in the [CHANGELOG](CHANGELOG.md) 92 | and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html) using a variation of the `MAJOR.MINOR.PATCH` format (accounting for the fact that this applies to content, not code): 93 | 94 | * *MAJOR version when you make incompatible API changes*: [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) 95 | * *MINOR version when you add functionality in a backwards compatible manner*: [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change) 96 | * *PATCH version when you make backwards compatible bug fixes*: [![](https://img.shields.io/badge/-minor_fix-c5def5)](https://github.com/DPGAlliance/DPG-Standard/pulls?q=is%3Apr+is%3Aopen+label%3A%22minor+fix%22) 97 | 98 | ### Releasing a New Version 99 | 100 | Follow these steps to release a new version: 101 | 102 | 1. Document your upcoming changes in `CHANGELOG.md`. Follow the existing structure and be consistent with the order of subsections: `Added`, `Changed`, `Deleted`. Also be sure to link the version in the diff list at the very bottom of the CHANGELOG. 103 | 2. Update the version number in both `standard.md` and `README.md`. 104 | 3. Commit all the changes that will be included in the new version. 105 | 4. Tag the last commit, for example, for version 1.0.1: 106 | ```bash 107 | git tag -a v1.0.1 -m "Version 1.0.1" 108 | ``` 109 | 5. Push the tag to the origin: 110 | ```bash 111 | git push origin --tags 112 | ``` 113 | 6. Visit https://github.com/DPGAlliance/DPG-Standard/releases and click on `Draft a New Release`: 114 | - Select the version you just tagged above in step 3 115 | - Enter the `Release title`, for example `v1.0.1` consistent with the preceeding steps. 116 | - In the `Describe this release`, copy and paste the text from the CHANGELOG for this version in *raw form* (it's markdown after all). Preview and verify that it looks good (you can edit this information again later, no big deal if something is wrong in the description). 117 | 118 | ## Propagating Changes 119 | 120 | This repository [DPGAlliance/DPG-Standard](https://github.com/DPGAlliance/DPG-Standard) is the source of truth for any information pertaining to the **Digital Public Goods Standard**, and any changes to the information contained herein need to be propagated and synced with the following list of resources, where applicable: 121 | 122 | 1. The DPGA website contains https://digitalpublicgoods.net/standard/ which needs to be updated manually matching the contents of [standard.md](https://github.com/DPGAlliance/DPG-Standard/blob/master/standard.md). 123 | 2. The DPGA website also contains the [submission guide](https://digitalpublicgoods.net/submission-guide/) which needs to be updated manually. 124 | 3. The DPG application [webapp admin panel](https://app.digitalpublicgoods.net/login) which will be updated manually. 125 | 5. The [Eligibility Form](https://digitalpublicgoods.net/eligibility/) through the [unicef/publicgoods-scripts](https://github.com/unicef/publicgoods-submission) repository, by editing [quizQuestions.js](https://github.com/unicef/publicgoods-scripts/blob/master/packages/eligibility/src/api/quizQuestions.js) 126 | 127 | 128 | # Current Roles 129 | 130 | * [Liv Marte Nordhaug](https://github.com/livmarte) Secretariat Co-Lead /OOO[Lucy Harris](https://github.com/lucyeoh) 131 | * [Christer Gunderson](https://github.com/christer-io), Technical Advisor 132 | * [Prajakta Kuwalekar](https://github.com/prajectory), Product Manager, current Moderator 133 | 134 | -------------------------------------------------------------------------------- /standard-questions.md: -------------------------------------------------------------------------------- 1 | # DPG Standard Questionary 2 | This document contains the set of questions that are collected in the application form at [app.digitalpublicgoods.net](https://app.digitalpublicgoods.net/form) and used to assess each of the indicators set forth in the DPG Standard. 3 | 4 | ## GENERAL INFORMATION 5 | About your digital solution. Please ensure that your details and code are available in English so that our reviewer team can assess the application properly. 6 | 7 | __Solution name__ 8 |
Please enter the full name of your digital solution. This will be listed on the registry if your application is accepted. 9 | 10 | __Aliases (if any)__ 11 |
Please mention any acronyms or aliases used to refer to your digital solution. Use commas to enter multiple names. 12 | 13 | __Solution category__ 14 |
Please select one or more of the four categories that your digital solutions belong to (Most solutions belong to only one category) 15 | * Open Software 16 | * Open Content 17 | * Open Data 18 | * Open AI Model 19 | 20 | __Short description__ 21 |
Please write a tweet-length description of the solution. If your application is approved, this will be reflected on the public DPG registry. 22 | 23 | __Website__ 24 |
Please provide link(s) to the website or webpage of your digital solution. 25 | 26 | __Alternate email address__ 27 |
Please provide us with an alternate email address (separate from the one used to register on this app). This will give us an additional way to contact you in case emails to the registered email address bounce back. 28 | 29 | __Where is your solution's source hosted?__ 30 |
Please provide link(s) to access the source for your code, data, content or AI model. This could be an open repository, API, library etc. 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 45 | 52 | 53 | 54 | 55 | 57 | 65 | 66 | 67 | 68 | 69 | 77 | 78 | 79 | 80 | 81 | 89 | 90 | 91 | 92 | 93 | 102 | 103 | 104 | 105 | 106 | 114 | 115 | 116 | 119 | 120 | 121 | 122 | 123 | 129 | 130 | 131 | 132 | 133 | 141 | 142 | 143 | 144 | 146 | 155 | 156 | 157 | 158 | 160 | 170 | 171 | 172 | 173 | 175 | 183 | 184 | 185 |
Indicator: Description:DPG Standard Assessment Questions:
1. SDG RelevanceYour digital solution must demonstrate relevance to one or more Sustainable Development Goals 44 | 46 |
    47 |
  • Which SDGs is your solution relevant to?*
    Select SDG/s that are MOST relevant to your solution from the list below.
    • 48 |
  • How is your solution relevant to each SDG you’ve selected above?*
    Each SDG has detailed targets that you can learn more about at the SDG tracker . State in a couple of sentences the relationship between your solution and selected SDG(s)’s targets. If you have selected more than one, you will have to establish the relationship for each of them. 49 |
    • 50 |
51 |
2. Open LicensingYour digital solution must use an approved open license. 56 | 58 |
    59 |
  • Which open license(s) is/are used by your solution?
    Please refer here for the list of approved open licenses accepted. (If you do not currently use one of the approved licenses, your solution cannot be approved as a DPG) 60 |
    • 61 |
  • Provide evidence of use of the selected open license(s).*
    Please provide link(s) to public pages where the license(s) selected above are hosted for this project. This could be a license file in GitHub repository or a public URL on the project website. 62 |
    • 63 |
64 |
3. Clear OwnershipThe organisation that owns this digital solution must be clearly defined. 70 |
    71 |
  • Who owns this digital solution?*
    If there is no formal organization associated with the solution, please enter names of the people who own this solution. 72 |
    • 73 |
  • Provide evidence(s) of ownership.*
    Please provide link(s) to the copyright, trademarks, or publicly available ownership documentation for the digital solutions. It could be a webpage that clearly defines who owns the digital solution. Terms of Service may also indicate the ownership of the digital solutions. Additional legal documentation that provides supporting information will strengthen your application. Digital solutions owned by a parent organisation, could highlight the digital solutions on their website to strengthen the application. 74 |
    • 75 |
76 |
4. Platform IndependenceIf your digital solution has any mandatory dependencies that create more restrictions than the original license, then there should be open alternatives so that such dependencies can be replaced with the alternatives without making significant changes to the core digital solution. 82 |
    83 |
  • Does this solution use any closed components that create proprietary dependency?*
    Yes or No. You will be required to answer the next question if you select Yes. 84 |
    • 85 |
  • How can these closed component(s) be replaced with open alternative(s)?
    Please provide a list of the active open alternatives for the closed component(s) and demonstrate that these close component(s) can be replaced with those open alternatives with minimal configuration changes, without requiring a major overhaul of the entire system. This requirement can be best answered by a technical member of your team. Leave this blank if the above answer is No. 86 |
    • 87 |
88 |
5. DocumentationYour digital solution must have strong documentation. The documentation should allow a technical person unfamiliar with the solution to launch and run the digital solution themselves. 94 |
    95 |
  • Where is your solution’s documentation?*
    Please summarize how and where the solution is documented along with link(s) to all relevant documents. 96 | For software solutions, documentation could include an open repo, technical specifications, functional requirements, etc. 97 | For data sets or solutions, documentation could describe all the fields in the set, and provide context on how the data was collected and how it should be interpreted. 98 | For content, documentation could include relevant compatible apps, software, hardware required to access the content and any instructions on how to use it. For more details on documentation best practices, please visit this link 99 |
    • 100 |
101 |
6. Non-PII Data ExtractionIf your solution collects or uses non-PII data and/or content, then there must be mechanisms for extracting or importing non-PII data from or into the system in a non-proprietary format. 107 |
    108 |
  • Does your solution collects or uses non-PII data and/or content?*
    Yes or No. You will be required to answer the next question only if you collect or use non-PII data and/or content. 109 |
    • 110 |
  • Describe the mechanism for extracting or importing non-PII data from or into the system in a non-proprietary format.
    Please provide a detailed description of how the non-PII data can be imported or exported into non-proprietary formats such as CSV/XML/JSON etc or via exposing the non-PII data through APIs. 111 |
    • 112 |
113 |
117 | Note that requirements related to indicators 7-9 can only be answered by someone authorized to speak on behalf of the project. 118 |
7. Privacy & Applicable LawsYour digital solution must comply with relevant privacy, domestic and other applicable international laws. 124 |
    125 |
  • Provide a list of relevant privacy, domestic and other applicable international laws your solution complies with.*
    Please enter a list of the relevant laws that your digital solutions complies with such as General Data Protection Regulation (GDPR), Indian IT Act, Persons with Disabilities Act 2020, Canadian Disabilities Act, Americans with Disabilities Act of 1990, etc.
    • 126 |
  • Provide evidence(s) of adherence with the laws mentioned above.*
    Please provide link(s) to the privacy policy, terms of service or other relevant legal documentation as demonstrate adherence
    • 127 |
128 |
8. Open Standards & Best PracticesYour digital solution must comply with relevant standards, best practices and/or principles. 134 |
    135 |
  • Provide a list of the open standards your solution adheres to and demonstrate adherence.*
    You may provide link(s) to a validator, open test suite, etc to demonstrate adherence. Here is a list of open standards that you may find helpful. 136 |
    • 137 |
  • Provide a list of best practices & principles your solution adheres to and demonstrate adherence.*
    You may provide link(s) to a validator, open test suite, etc to demonstrate adherence. Here is a list of best practices that you may find helpful. 138 |
    • 139 |
140 |
9 A. Data Privacy & SecurityIf your digital solution collects, stores and distributes PII data (personally identifiable information) data, then you must demonstrate how is the privacy, security and integrity of this data is ensured 145 | 147 |
    148 |
  • Does your solution collect / store / distribute PII data?*
    Please select the option that is applicable for your solution.
    PII data is NOT collected NOT stored and NOT distributed.
    PII data is collected but NOT stored and NOT distributed.
    PII data is collected and stored but NOT distributed.
    PII data is collected and stored and distributed. 149 |
    • 150 |
  • What are types of data that is collected / stored / distributed?
    Please list the types of PII data. Example: Name, Email, etc.
    • 151 |
  • How does your solution ensures data privacy & security?
    Please demonstrate how the project ensures the privacy, security and integrity of this data and the steps taken to prevent adverse impacts resulting from its collection, storage and distribution. 152 |
    • 153 |
154 |
9 B. Inappropriate & Illegal ContentIf your digital solution collects, stores and distributes content, then you must have policies identifying inappropriate and illegal content such as child sexual abuse materials in addition to processes for detecting, moderating, reporting and removing inappropriate/ illegal content. 159 | 161 |
    162 |
  • Does your solution collect / store / distribute content?*
    Please select the option that is applicable for your solution.
    Content is NOT collected NOT stored and NOT distributed.
    Content is collected but NOT stored and NOT distributed.
    Content is collected and stored but NOT distributed.
    Content is collected and stored and distributed. 163 |
    • 164 |
  • What are the types of content that is collected / stored / distributed?
    Please list the types of content. 165 |
    • 166 |
  • How does your solution handles inappropriate and illegal content?
    Please describe (1) the policies for identifying inappropriate and illegal content and (2) the processes for detecting, moderating, reporting and removing inappropriate / illegal content. Please include the average response time for assessment and/or action. 167 |
    • 168 |
169 |
9 C. Protection from HarassmentIf your digital solution facilitates interactions with or between users or contributors there must be a process for users and contributors to protect themselves against grief, abuse, and harassment. The project must have system(s) to address the safety and security of underage users 174 | 176 |
    177 |
  • Does your solution facilitate interactions with or between users and/or contributors?*
    Yes or No. Please select the option that is applicable for your solution. You will be required to answer the next question if you select Yes. 178 |
    • 179 |
  • How does your solution enables users and contributors to protect themselves from harassment?
    Please describe (1) policies such as a code of conduct and processes users and contributors can use to protect themselves and (2) processes that addresses the safety and security of underage users. 180 |
    • 181 |
182 |
186 | 187 | **Scale of Solution:** 188 |
Additional information highlighting the extent and scale of your solution's implementation and success. 189 | * Where was this solution developed?*: _Please select one or more countries._ 190 | * Where is this solution actively deployed?*: _Please select one or more countries._ 191 | * Are there any multi-lateral organisations using your solution?: _Please select from the options below._ 192 | * Are there any governments departments and/or ministries using your solution?: _Please enter a list country governments, ministries, public bodies that have adopted your solution._ 193 | * Who else is using your solution?: _Please enter any other organization or body not covered in above questions that have adopted your solution_ 194 | * Has your solution received any awards and/or recognition in the last one year?: _Please enter a list of awards and/or recognition recieved along with the awarding organisation, award title and a link to a certificate or document or image that verifies your claim for each._ 195 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Attribution-ShareAlike 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution-ShareAlike 4.0 International Public 58 | License 59 | 60 | By exercising the Licensed Rights (defined below), You accept and agree 61 | to be bound by the terms and conditions of this Creative Commons 62 | Attribution-ShareAlike 4.0 International Public License ("Public 63 | License"). To the extent this Public License may be interpreted as a 64 | contract, You are granted the Licensed Rights in consideration of Your 65 | acceptance of these terms and conditions, and the Licensor grants You 66 | such rights in consideration of benefits the Licensor receives from 67 | making the Licensed Material available under these terms and 68 | conditions. 69 | 70 | 71 | Section 1 -- Definitions. 72 | 73 | a. Adapted Material means material subject to Copyright and Similar 74 | Rights that is derived from or based upon the Licensed Material 75 | and in which the Licensed Material is translated, altered, 76 | arranged, transformed, or otherwise modified in a manner requiring 77 | permission under the Copyright and Similar Rights held by the 78 | Licensor. For purposes of this Public License, where the Licensed 79 | Material is a musical work, performance, or sound recording, 80 | Adapted Material is always produced where the Licensed Material is 81 | synched in timed relation with a moving image. 82 | 83 | b. Adapter's License means the license You apply to Your Copyright 84 | and Similar Rights in Your contributions to Adapted Material in 85 | accordance with the terms and conditions of this Public License. 86 | 87 | c. BY-SA Compatible License means a license listed at 88 | creativecommons.org/compatiblelicenses, approved by Creative 89 | Commons as essentially the equivalent of this Public License. 90 | 91 | d. Copyright and Similar Rights means copyright and/or similar rights 92 | closely related to copyright including, without limitation, 93 | performance, broadcast, sound recording, and Sui Generis Database 94 | Rights, without regard to how the rights are labeled or 95 | categorized. For purposes of this Public License, the rights 96 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 97 | Rights. 98 | 99 | e. Effective Technological Measures means those measures that, in the 100 | absence of proper authority, may not be circumvented under laws 101 | fulfilling obligations under Article 11 of the WIPO Copyright 102 | Treaty adopted on December 20, 1996, and/or similar international 103 | agreements. 104 | 105 | f. Exceptions and Limitations means fair use, fair dealing, and/or 106 | any other exception or limitation to Copyright and Similar Rights 107 | that applies to Your use of the Licensed Material. 108 | 109 | g. License Elements means the license attributes listed in the name 110 | of a Creative Commons Public License. The License Elements of this 111 | Public License are Attribution and ShareAlike. 112 | 113 | h. Licensed Material means the artistic or literary work, database, 114 | or other material to which the Licensor applied this Public 115 | License. 116 | 117 | i. Licensed Rights means the rights granted to You subject to the 118 | terms and conditions of this Public License, which are limited to 119 | all Copyright and Similar Rights that apply to Your use of the 120 | Licensed Material and that the Licensor has authority to license. 121 | 122 | j. Licensor means the individual(s) or entity(ies) granting rights 123 | under this Public License. 124 | 125 | k. Share means to provide material to the public by any means or 126 | process that requires permission under the Licensed Rights, such 127 | as reproduction, public display, public performance, distribution, 128 | dissemination, communication, or importation, and to make material 129 | available to the public including in ways that members of the 130 | public may access the material from a place and at a time 131 | individually chosen by them. 132 | 133 | l. Sui Generis Database Rights means rights other than copyright 134 | resulting from Directive 96/9/EC of the European Parliament and of 135 | the Council of 11 March 1996 on the legal protection of databases, 136 | as amended and/or succeeded, as well as other essentially 137 | equivalent rights anywhere in the world. 138 | 139 | m. You means the individual or entity exercising the Licensed Rights 140 | under this Public License. Your has a corresponding meaning. 141 | 142 | 143 | Section 2 -- Scope. 144 | 145 | a. License grant. 146 | 147 | 1. Subject to the terms and conditions of this Public License, 148 | the Licensor hereby grants You a worldwide, royalty-free, 149 | non-sublicensable, non-exclusive, irrevocable license to 150 | exercise the Licensed Rights in the Licensed Material to: 151 | 152 | a. reproduce and Share the Licensed Material, in whole or 153 | in part; and 154 | 155 | b. produce, reproduce, and Share Adapted Material. 156 | 157 | 2. Exceptions and Limitations. For the avoidance of doubt, where 158 | Exceptions and Limitations apply to Your use, this Public 159 | License does not apply, and You do not need to comply with 160 | its terms and conditions. 161 | 162 | 3. Term. The term of this Public License is specified in Section 163 | 6(a). 164 | 165 | 4. Media and formats; technical modifications allowed. The 166 | Licensor authorizes You to exercise the Licensed Rights in 167 | all media and formats whether now known or hereafter created, 168 | and to make technical modifications necessary to do so. The 169 | Licensor waives and/or agrees not to assert any right or 170 | authority to forbid You from making technical modifications 171 | necessary to exercise the Licensed Rights, including 172 | technical modifications necessary to circumvent Effective 173 | Technological Measures. For purposes of this Public License, 174 | simply making modifications authorized by this Section 2(a) 175 | (4) never produces Adapted Material. 176 | 177 | 5. Downstream recipients. 178 | 179 | a. Offer from the Licensor -- Licensed Material. Every 180 | recipient of the Licensed Material automatically 181 | receives an offer from the Licensor to exercise the 182 | Licensed Rights under the terms and conditions of this 183 | Public License. 184 | 185 | b. Additional offer from the Licensor -- Adapted Material. 186 | Every recipient of Adapted Material from You 187 | automatically receives an offer from the Licensor to 188 | exercise the Licensed Rights in the Adapted Material 189 | under the conditions of the Adapter's License You apply. 190 | 191 | c. No downstream restrictions. You may not offer or impose 192 | any additional or different terms or conditions on, or 193 | apply any Effective Technological Measures to, the 194 | Licensed Material if doing so restricts exercise of the 195 | Licensed Rights by any recipient of the Licensed 196 | Material. 197 | 198 | 6. No endorsement. Nothing in this Public License constitutes or 199 | may be construed as permission to assert or imply that You 200 | are, or that Your use of the Licensed Material is, connected 201 | with, or sponsored, endorsed, or granted official status by, 202 | the Licensor or others designated to receive attribution as 203 | provided in Section 3(a)(1)(A)(i). 204 | 205 | b. Other rights. 206 | 207 | 1. Moral rights, such as the right of integrity, are not 208 | licensed under this Public License, nor are publicity, 209 | privacy, and/or other similar personality rights; however, to 210 | the extent possible, the Licensor waives and/or agrees not to 211 | assert any such rights held by the Licensor to the limited 212 | extent necessary to allow You to exercise the Licensed 213 | Rights, but not otherwise. 214 | 215 | 2. Patent and trademark rights are not licensed under this 216 | Public License. 217 | 218 | 3. To the extent possible, the Licensor waives any right to 219 | collect royalties from You for the exercise of the Licensed 220 | Rights, whether directly or through a collecting society 221 | under any voluntary or waivable statutory or compulsory 222 | licensing scheme. In all other cases the Licensor expressly 223 | reserves any right to collect such royalties. 224 | 225 | 226 | Section 3 -- License Conditions. 227 | 228 | Your exercise of the Licensed Rights is expressly made subject to the 229 | following conditions. 230 | 231 | a. Attribution. 232 | 233 | 1. If You Share the Licensed Material (including in modified 234 | form), You must: 235 | 236 | a. retain the following if it is supplied by the Licensor 237 | with the Licensed Material: 238 | 239 | i. identification of the creator(s) of the Licensed 240 | Material and any others designated to receive 241 | attribution, in any reasonable manner requested by 242 | the Licensor (including by pseudonym if 243 | designated); 244 | 245 | ii. a copyright notice; 246 | 247 | iii. a notice that refers to this Public License; 248 | 249 | iv. a notice that refers to the disclaimer of 250 | warranties; 251 | 252 | v. a URI or hyperlink to the Licensed Material to the 253 | extent reasonably practicable; 254 | 255 | b. indicate if You modified the Licensed Material and 256 | retain an indication of any previous modifications; and 257 | 258 | c. indicate the Licensed Material is licensed under this 259 | Public License, and include the text of, or the URI or 260 | hyperlink to, this Public License. 261 | 262 | 2. You may satisfy the conditions in Section 3(a)(1) in any 263 | reasonable manner based on the medium, means, and context in 264 | which You Share the Licensed Material. For example, it may be 265 | reasonable to satisfy the conditions by providing a URI or 266 | hyperlink to a resource that includes the required 267 | information. 268 | 269 | 3. If requested by the Licensor, You must remove any of the 270 | information required by Section 3(a)(1)(A) to the extent 271 | reasonably practicable. 272 | 273 | b. ShareAlike. 274 | 275 | In addition to the conditions in Section 3(a), if You Share 276 | Adapted Material You produce, the following conditions also apply. 277 | 278 | 1. The Adapter's License You apply must be a Creative Commons 279 | license with the same License Elements, this version or 280 | later, or a BY-SA Compatible License. 281 | 282 | 2. You must include the text of, or the URI or hyperlink to, the 283 | Adapter's License You apply. You may satisfy this condition 284 | in any reasonable manner based on the medium, means, and 285 | context in which You Share Adapted Material. 286 | 287 | 3. You may not offer or impose any additional or different terms 288 | or conditions on, or apply any Effective Technological 289 | Measures to, Adapted Material that restrict exercise of the 290 | rights granted under the Adapter's License You apply. 291 | 292 | 293 | Section 4 -- Sui Generis Database Rights. 294 | 295 | Where the Licensed Rights include Sui Generis Database Rights that 296 | apply to Your use of the Licensed Material: 297 | 298 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 299 | to extract, reuse, reproduce, and Share all or a substantial 300 | portion of the contents of the database; 301 | 302 | b. if You include all or a substantial portion of the database 303 | contents in a database in which You have Sui Generis Database 304 | Rights, then the database in which You have Sui Generis Database 305 | Rights (but not its individual contents) is Adapted Material, 306 | 307 | including for purposes of Section 3(b); and 308 | c. You must comply with the conditions in Section 3(a) if You Share 309 | all or a substantial portion of the contents of the database. 310 | 311 | For the avoidance of doubt, this Section 4 supplements and does not 312 | replace Your obligations under this Public License where the Licensed 313 | Rights include other Copyright and Similar Rights. 314 | 315 | 316 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 317 | 318 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 319 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 320 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 321 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 322 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 323 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 324 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 325 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 326 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 327 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 328 | 329 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 330 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 331 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 332 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 333 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 334 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 335 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 336 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 337 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 338 | 339 | c. The disclaimer of warranties and limitation of liability provided 340 | above shall be interpreted in a manner that, to the extent 341 | possible, most closely approximates an absolute disclaimer and 342 | waiver of all liability. 343 | 344 | 345 | Section 6 -- Term and Termination. 346 | 347 | a. This Public License applies for the term of the Copyright and 348 | Similar Rights licensed here. However, if You fail to comply with 349 | this Public License, then Your rights under this Public License 350 | terminate automatically. 351 | 352 | b. Where Your right to use the Licensed Material has terminated under 353 | Section 6(a), it reinstates: 354 | 355 | 1. automatically as of the date the violation is cured, provided 356 | it is cured within 30 days of Your discovery of the 357 | violation; or 358 | 359 | 2. upon express reinstatement by the Licensor. 360 | 361 | For the avoidance of doubt, this Section 6(b) does not affect any 362 | right the Licensor may have to seek remedies for Your violations 363 | of this Public License. 364 | 365 | c. For the avoidance of doubt, the Licensor may also offer the 366 | Licensed Material under separate terms or conditions or stop 367 | distributing the Licensed Material at any time; however, doing so 368 | will not terminate this Public License. 369 | 370 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 371 | License. 372 | 373 | 374 | Section 7 -- Other Terms and Conditions. 375 | 376 | a. The Licensor shall not be bound by any additional or different 377 | terms or conditions communicated by You unless expressly agreed. 378 | 379 | b. Any arrangements, understandings, or agreements regarding the 380 | Licensed Material not stated herein are separate from and 381 | independent of the terms and conditions of this Public License. 382 | 383 | 384 | Section 8 -- Interpretation. 385 | 386 | a. For the avoidance of doubt, this Public License does not, and 387 | shall not be interpreted to, reduce, limit, restrict, or impose 388 | conditions on any use of the Licensed Material that could lawfully 389 | be made without permission under this Public License. 390 | 391 | b. To the extent possible, if any provision of this Public License is 392 | deemed unenforceable, it shall be automatically reformed to the 393 | minimum extent necessary to make it enforceable. If the provision 394 | cannot be reformed, it shall be severed from this Public License 395 | without affecting the enforceability of the remaining terms and 396 | conditions. 397 | 398 | c. No term or condition of this Public License will be waived and no 399 | failure to comply consented to unless expressly agreed to by the 400 | Licensor. 401 | 402 | d. Nothing in this Public License constitutes or may be interpreted 403 | as a limitation upon, or waiver of, any privileges and immunities 404 | that apply to the Licensor or You, including from the legal 405 | processes of any jurisdiction or authority. 406 | 407 | 408 | ======================================================================= 409 | 410 | Creative Commons is not a party to its public 411 | licenses. Notwithstanding, Creative Commons may elect to apply one of 412 | its public licenses to material it publishes and in those instances 413 | will be considered the “Licensor.” The text of the Creative Commons 414 | public licenses is dedicated to the public domain under the CC0 Public 415 | Domain Dedication. Except for the limited purpose of indicating that 416 | material is shared under a Creative Commons public license or as 417 | otherwise permitted by the Creative Commons policies published at 418 | creativecommons.org/policies, Creative Commons does not authorize the 419 | use of the trademark "Creative Commons" or any other trademark or logo 420 | of Creative Commons without its prior written consent including, 421 | without limitation, in connection with any unauthorized modifications 422 | to any of its public licenses or any other arrangements, 423 | understandings, or agreements concerning use of licensed material. For 424 | the avoidance of doubt, this paragraph does not form part of the 425 | public licenses. 426 | 427 | Creative Commons may be contacted at creativecommons.org. 428 | -------------------------------------------------------------------------------- /docs/standard-badge.svg: -------------------------------------------------------------------------------- 1 | 2 | Created by André Luizfrom the Noun Project 3 | --------------------------------------------------------------------------------