Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update standard.md #45

Merged
merged 5 commits into from
Feb 4, 2021
Merged

Update standard.md #45

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
32646b9
Update standard.md
Not-Whiskey Feb 4, 2021
dd08338
DOC: formatting edits
lacabra Feb 4, 2021
97d7c0c
Update standard.md
Not-Whiskey Feb 4, 2021
22101bd
Merge branch 'master' into Not-Whiskey-patch-1
lacabra Feb 4, 2021
b898137
DOC: updated CHANGELOG with #45
lacabra Feb 4, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,19 @@
- **Last Update**: 2021-01-04
- [View Changelog](https://github.com/DPGAlliance/DPG-Standard/blob/master/CHANGELOG.md)

| Indicator | Requirement |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1. Relevance to Sustainable Development Goals** | All projects must indicate the [Sustainable Development Goals](https://sdgs.un.org/goals) (SDGs) that they are relevant to and provide supporting links/documentation to support this relevance. |
| **2. Use of approved open licenses** | Projects must demonstrate the use of an approved open license. For Open Source Software, we only accept [OSI approved licenses](https://opensource.org/licenses). For Open Content we require the use of a [Creative Commons license](https://creativecommons.org/licenses/) while we encourage projects to use a license which 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/)); we also accept licenses which 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/)). For data we require an [Open Data Commons approved license](https://opendefinition.org/licenses/). _You can find [the full license list here](https://github.com/unicef/publicgoods-candidates/blob/master/docs/licenses.md)._ |
| **3. Clear Ownership** | Ownership of everything that the project produces must be clearly defined and documented i.e. 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 projects must be able to demonstrate independence from the closed component and/or indicate the existence of functional, open alternatives. |
| **5. Documentation** | The project must have some documentation of the source code, use cases, and/or functional requirements. For content, this should indicate any relevant compatible apps, software, hardware required to access the content and instructions about how to use it. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. |
| **6. Mechanism for Extracting Data** | If this project has non personally identifiable information there must be a mechanism for extracting or importing non personally identifiable information (PII) data from the system in a non-proprietary format. |
| **7. Adherence to privacy and applicable laws** | The project must state that to the best of its knowledge it complies with relevant privacy laws, and all applicable international and domestic laws. |
| **8. Adherence to standards & best practices** | Projects must demonstrate some adherence to standards, best practices and/or principles. i.e. the principles for digital development |
| **9. Do No Harm** | All projects must demonstrate that they have taken steps to ensure that the project anticipates, prevents and does no harm. |
| **9a) Data Privacy & Security** | Projects that collect data must identify the types of data collected and stored and demonstrate that the project ensures the privacy and security of this data and has taken steps 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 and 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. |
Indicator | Requirement
--- | ---
**1. Relevance to Sustainable Development Goals** | All projects must indicate the [Sustainable Development Goals](https://sdgs.un.org/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](https://opensource.org/licenses) are accepted. For open content the use of a [Creative Commons license](https://creativecommons.org/licenses/) is required. While we encourage projects 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/unicef/publicgoods-candidates/blob/master/docs/licenses.md) 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](https://digitalprinciples.org/principles/).
**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: that 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._
_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._