- Version: 1.1.4
- Last Update: 2021-01-04
- View Changelog
| Indicator | Requirement |
|---|---|
| 1. Relevance to Sustainable Development Goals | All projects must indicate the Sustainable Development Goals (SDGs) they are relevant to, and provide supporting links/documentation to support their relevance. |
| 2. Use of Approved Open Licenses | Projects must demonstrate the use of an approved open license. For open source software, only OSI approved licenses are accepted. For open content the use of a Creative Commons license is required. While we encourage projects to use a license that allows for both derivatives and commercial reuse (CC-BY and CC-BY-SA), or dedicate content to the public domain (CC0); licenses that do not allow for commercial reuse (CC-BY-NC and CC-BY-NC-SA) are also accepted. For open data, an Open Data Commons approved license is required. See The full license list for reference. |
| 3. Clear Ownership | Ownership of everything the project produces must be clearly defined and documented. For example, through copyright, trademark or other publicly available information. |
| 4. Platform Independence | If the project has mandatory dependencies that create more restrictions than the original license, the project(s) must be able to demonstrate independence from the closed component(s) and/or indicate the existence of functional, open alternatives. |
| 5. Documentation | The project must have documentation of the source code, use cases, and/or functional requirements. For content, this should include all relevant/compatible apps, software, or hardware required to access the content, and instructions regarding how to use it. For software projects, 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 data was collected, and how it should be interpreted. |
| 6. Mechanism for Extracting Data | If the project has non personally identifiable information (PII) there must be a mechanism for extracting or importing non-PII data from the system in a non-proprietary format. |
| 7. Adherence to Privacy and Applicable Laws | The project must state to the best of its knowledge that it complies with relevant privacy laws, and all applicable international and domestic laws. |
| 8. Adherence to Standards & Best Practices | Projects must demonstrate adherence to standards, best practices, and/or principles. For example, the Principles for Digital Development. |
| 9. Do No Harm | All projects must demonstrate that they have taken steps to ensure the project anticipates, prevents, and does no harm. |
| 9a) Data Privacy & Security | Projects collecting data must identify the types of data collected and stored. Projects must also demonstrate how they ensure the privacy and security of this data in addition to the steps taken to prevent adverse impacts resulting from it’s collection, storage and distribution. |
| 9b) Inappropriate & Illegal Content | Projects that collect, store or distribute content must have policies identifying inappropriate and illegal content such as child sexual abuse materials in addition to mechanisms for detecting, moderating and removing inappropriate/illegal content. |
| 9c) Protection from Harassment | If the project facilitates interactions with or between users or contributors there must be a mechanism for users and contributors to protect themselves against grief, abuse, and harassment. The project must have a mechanism to address the safety and security of underage users. |
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.