Skip to content

Commit

Permalink
Merge pull request #30 from christer-io/patch-2
Browse files Browse the repository at this point in the history
Minor correction of the text i point 2 and 4
  • Loading branch information
lacabra authored Dec 1, 2020
2 parents 494aeff + 116503b commit cd2a839
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions standard.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@
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 source license** | Projects must demonstrate the use of an approved open source 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).*
**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. Documentation of 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. Mandatory dependencies** | If the open source 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.
**4. Mandatory dependencies** | 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.
Expand Down

0 comments on commit cd2a839

Please sign in to comment.