+373 79 760-762

opencode.md@gmail.com

Requirements to Open Source Solutions

Parameter	Requirements
1. Relevance to Sustainable Development Goals	Open Source Solution must demonstrate relevance to advancing the Sustainable Development Goals (SDGs)
2. Use of Approved Open Licenses	Digital Public Goods must demonstrate the use of an “Approved Open License”. For open-source software, the Open Source Initiative approved licenses are accepted. For open content collections the use of a Creative Commons license is required. For open data, an Open Data Commons approved license is required. For Digital Public Goods also are encourageed 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. The full list of licenses presented here.
3. Clear Ownership	Ownership of assets that the Open Source Solution be clearly defined and documented. For example, through copyright, trademark or other publicly available information.
4. Platform Independence	When the Open Source Solution 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.
5. Documentation	Open Source Solution 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.
6. Mechanism for Extracting Data	Open Source Solutions 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.
7. Adherence to Privacy and Applicable Laws	Open Source Solutions must be designed and developed to comply with privacy and other applicable laws.
8. Adherence to Standards & Best Practices	Open Source Solution must be designed and developed to align with relevant standards, best practices, and/or principles. For example, the Principles for Digital Development.
9. Do No Harm by Design	Open Source Solution must be designed to anticipate, prevent, and do no harm by design.
9.a) Data Privacy & Security	Open Source Solution that collect, store and distribute personally identifiable data, 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. Regarding the protection of personally identifiable data (or personal data), an open source solution must comply with: the requirements of Law No. 133 of 08-07-2011 on the protection of personal data. the requirements of the document UNDP Development Group “Guidance note on big data for achievement of the 2030 Sustainable Development Goals agenda” It reads: For the purposes of this document, personal data means data, in any form or medium, relating to an identified or identifiable individual who can be identified, directly or indirectly, by means reasonably likely to be used, including where an individual can be identified by linking the data to other information reasonably available. Personal data is defined by many regional and national instruments and can also be referenced as personal information or personally identifiable information.
9.b) Inappropriate & Illegal Content	Open Source Solution 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.
9.c) 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.