From fdd79b38bb4cc5ae819c135eeef5ae5266c3911b Mon Sep 17 00:00:00 2001 From: Lucyeoh <66376240+Lucyeoh@users.noreply.github.com> Date: Thu, 24 Sep 2020 16:09:29 -0400 Subject: [PATCH 01/18] Clarified wording around CC licenses Slight adjustment to make this paragraph more clear and readable based on suggestions by Cable Green, Creative Commons --- standard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard.md b/standard.md index 3ebeb40..3a7025e 100644 --- a/standard.md +++ b/standard.md @@ -7,7 +7,7 @@ Indicator | Requirement --- | --- **1. Relevance to Sustainable Development Goals** | All projects must indicate the SDG(s) 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 or dedicate content to the public domain ([CC0](https://creativecommons.org/choose/zero/)) we also accept the following 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 a [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 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 and CC-BY-SA), 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 a [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. **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. From c84250aa554192bc1b57fdbf1ee58327dba5eb75 Mon Sep 17 00:00:00 2001 From: downeymj <56423146+downeymj@users.noreply.github.com> Date: Tue, 6 Oct 2020 18:33:34 +0000 Subject: [PATCH 02/18] Add Michael Downey --- endorsement.md | 1 + 1 file changed, 1 insertion(+) diff --git a/endorsement.md b/endorsement.md index 4142bd0..ac3c899 100644 --- a/endorsement.md +++ b/endorsement.md @@ -21,6 +21,7 @@ Two ways to endorse the standard: Full Name | Title | Organization --- | --- | --- [Sean Blaschke](https://github.com/seanblaschke) | Technology for Development Business Analyst, UNICEF Eastern and Southern Africa Regional Office | [UNICEF](https://www.unicef.org/) +[Michael Downey](https://floss.social/@downey) | Director of Community, Open Source Center, Digital Impact Alliance | [United Nations Foundation](https://digitalimpactalliance.org/) [Justin W. Flory](https://jwf.io) | Open Source Technical Advisor, UNICEF Office of Innovation | [UNICEF Innovation Fund](https://unicefinnovationfund.org/) [Matt Germonrez](https://github.com/germonprez) | Professor, College of Information Science & Technology at University of Nebraska at Omaha | [CHAOSS](https://chaoss.community/) [Sean P. Goggins](https://github.com/sgoggins) | Professor, College of Engineering at University of Missouri | [CHAOSS](https://chaoss.community/) From f499b9dd57b9cf4560f5e2c468310b51fad4a1a2 Mon Sep 17 00:00:00 2001 From: downeymj <56423146+downeymj@users.noreply.github.com> Date: Tue, 6 Oct 2020 20:11:58 +0000 Subject: [PATCH 03/18] Update title/organization name --- endorsement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/endorsement.md b/endorsement.md index ac3c899..7cbede7 100644 --- a/endorsement.md +++ b/endorsement.md @@ -21,7 +21,7 @@ Two ways to endorse the standard: Full Name | Title | Organization --- | --- | --- [Sean Blaschke](https://github.com/seanblaschke) | Technology for Development Business Analyst, UNICEF Eastern and Southern Africa Regional Office | [UNICEF](https://www.unicef.org/) -[Michael Downey](https://floss.social/@downey) | Director of Community, Open Source Center, Digital Impact Alliance | [United Nations Foundation](https://digitalimpactalliance.org/) +[Michael Downey](https://floss.social/@downey) | Director of Community, Open Source Center | [Digital Impact Alliance @ United Nations Foundation](https://digitalimpactalliance.org/) [Justin W. Flory](https://jwf.io) | Open Source Technical Advisor, UNICEF Office of Innovation | [UNICEF Innovation Fund](https://unicefinnovationfund.org/) [Matt Germonrez](https://github.com/germonprez) | Professor, College of Information Science & Technology at University of Nebraska at Omaha | [CHAOSS](https://chaoss.community/) [Sean P. Goggins](https://github.com/sgoggins) | Professor, College of Engineering at University of Missouri | [CHAOSS](https://chaoss.community/) From 1442cf55dc182fecae4af9d3740f48ffd4898858 Mon Sep 17 00:00:00 2001 From: Lucyeoh <66376240+Lucyeoh@users.noreply.github.com> Date: Wed, 7 Oct 2020 14:44:49 -0400 Subject: [PATCH 04/18] Adding Sudhanshu Shekhar - from the form --- endorsement.md | 1 + 1 file changed, 1 insertion(+) diff --git a/endorsement.md b/endorsement.md index 7cbede7..96b0172 100644 --- a/endorsement.md +++ b/endorsement.md @@ -26,6 +26,7 @@ Full Name | Title | Organization [Matt Germonrez](https://github.com/germonprez) | Professor, College of Information Science & Technology at University of Nebraska at Omaha | [CHAOSS](https://chaoss.community/) [Sean P. Goggins](https://github.com/sgoggins) | Professor, College of Engineering at University of Missouri | [CHAOSS](https://chaoss.community/) [Victor Grau Serrat](https://github.com/lacabra) | Technical Lead, UNICEF Office of Innovation | [UNICEF](https://www.unicef.org/innovation/) +[Sudhanshu Shekhar (https://www.linkedin.com/in/sudshekhar02/) | Fellow, iSPIRT | [iSPIRT](https://ispirt.in/) [Lucy Harris](https://github.com/lucyeoh) | Secretariat Co-Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) [Georg J.P. Link](https://github.com/GeorgLink) | Open Source Strategist | [CHAOSS](https://chaoss.community/) Jon Lloyd | Director of Campaigns at Mozilla Foundation | [Mozilla Foundation](https://foundation.mozilla.org/en/) From 2131987338d2b87799628ee007262ce9a1461c92 Mon Sep 17 00:00:00 2001 From: Lucyeoh <66376240+Lucyeoh@users.noreply.github.com> Date: Wed, 7 Oct 2020 14:45:50 -0400 Subject: [PATCH 05/18] Fixed broken formatting (that I broke) --- endorsement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/endorsement.md b/endorsement.md index 96b0172..0586f2b 100644 --- a/endorsement.md +++ b/endorsement.md @@ -26,7 +26,7 @@ Full Name | Title | Organization [Matt Germonrez](https://github.com/germonprez) | Professor, College of Information Science & Technology at University of Nebraska at Omaha | [CHAOSS](https://chaoss.community/) [Sean P. Goggins](https://github.com/sgoggins) | Professor, College of Engineering at University of Missouri | [CHAOSS](https://chaoss.community/) [Victor Grau Serrat](https://github.com/lacabra) | Technical Lead, UNICEF Office of Innovation | [UNICEF](https://www.unicef.org/innovation/) -[Sudhanshu Shekhar (https://www.linkedin.com/in/sudshekhar02/) | Fellow, iSPIRT | [iSPIRT](https://ispirt.in/) +[Sudhanshu Shekhar](https://www.linkedin.com/in/sudshekhar02/) | Fellow, iSPIRT | [iSPIRT](https://ispirt.in/) [Lucy Harris](https://github.com/lucyeoh) | Secretariat Co-Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) [Georg J.P. Link](https://github.com/GeorgLink) | Open Source Strategist | [CHAOSS](https://chaoss.community/) Jon Lloyd | Director of Campaigns at Mozilla Foundation | [Mozilla Foundation](https://foundation.mozilla.org/en/) From d6531e0ebaa471cb9efa6526392efe51ce7303c7 Mon Sep 17 00:00:00 2001 From: Victor Date: Wed, 14 Oct 2020 16:47:13 -0600 Subject: [PATCH 06/18] DOC: created governance.md --- governance.md | 106 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 governance.md diff --git a/governance.md b/governance.md new file mode 100644 index 0000000..aaa5be8 --- /dev/null +++ b/governance.md @@ -0,0 +1,106 @@ +# Digital Public Goods Standard Governance + +This is work in progress. + +The purpose of this document is to present how the Digital Public Goods Alliance envisions governing a growing community of +contributors and stakeholders around the Digital Public Goods Standard. + +## Principles + +The Digital Public Goods community adheres to the following principles: + +* **Open**: The Digital Public Goods Standard is open content, refer to the [license terms](README#memo-license). +* **Welcoming and Respectful**: See the [Code of Conduct](#code-of-conduct) below. +* **Transparent and Accessible**: Work and collaboration on the Standard should be done in public, hence the creation and management of this repository. See [Revisions](#revisions) below. + +## Code of Conduct + +We have adopted the [Contributor Covenant Code of Conduct v2](CODE_OF_CONDUCT.md), and we expect all members of the +community to embrace it. Here's an excerpt on our pledge: + +*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.* + +*We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.* + +## Revisions + +This section documents the processes for: +* proposing modifications to the current version of the standard, +* reviewing proposed changes +* and incorporating them in forthcoming revisions + +The latest version of the [Digital Public Goods Standard](standard.md) is found at the root folder of this repository. +The standard is operationalized through a [questionary](standard-questions.md). This set of questions is used to screen +projects or products, and validate whether they conform to the standard, and can thus be +legitimately classified as Digital Public Goods. + +### Priority + +Our priority for Q4 2020 is to consolidate the standard. Thus, we ask all comments and edits to be centered around the standard +rather than the associated set of questions. The rationale is that if the standard were to change in a significant way over the +initial months, so would the questionary; and any preliminary work on the questions may need to be discarded. + +### Proposing Changes + +These are the suggested steps for proposing changes to the standard: +- First, review the existing [Pull Requests](https://github.com/DPGAlliance/DPG-Standard/pulls) and check if your proposed change +has not already been proposed to avoid duplication. If it has already been proposed, you are encouraged to add your perspective +to the existing proposed change and argue for or against it, making constructive and compelling arguments. +- If none of the open pull requests address the issue you are proposing, +[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. +When opening a new pull request, be very explicit about the changes that you are proposing, and making the case for these changes. Otherwise, if your +contribution is a commentary or a general opinion, we will review it, but will not deem it actionable and close it. +- Once your pull request has been submitted, follow the discussion that will ensue. + +### Classification of modifications + +In order to streamline the review of proposals, we will use the following classification, labeling them accordingly: + +* [![](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 +include mostly stylistic edits including, but not limited to: correcting typographical errors, making gramatical edits and adding or removing clarifying +statements with the aim of improving readibility of the standard or facilitating its understanding to the reader. These proposed changes do not alter the +intended meaning of the existing indicators, nor introduce or remove key concepts. + +* [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change) These include modifications +that alter the existing indicators in significant ways, have implications across the board, but they do not challenge the purpose or scope of the standard. +These may also include reorganization of the various sections of the standard, removing existing sections altogether, or adding new indicators to the standard. + +* [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) These involve +fundamental or philosophical changes taht challenge the purpose, the scope or the very existence of the standard. + +## Proposal review + +The process for reviewing and accepting proposals varies depending on the classification of the proposal: + +* [![](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 +leaving a minimum of one week to accept additional commentary from other members of the community, the pull request requires 1 Secretariat co-lead and 1 technical +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, and there +will be a monthly meeting to catch and address any outstanding such issues. + +* [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change). The moderator will first assign it +to a member of the Alliance for further investigation over a period of up to two weeks. That person will report back and comment on the issue documenting and exploring +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 +the members of the Alliance's Internal Strategy Group (ISG) giving them an equal chance to comment. Review for these changes will happen quarterly, and consensus from the 2 co-leads and 2 technical leads +(see [Current Roles](#current-roles)) will be required to take action (either accept or reject). + +* [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental). After validating the legitimacy of the +proposal, we will open a consultation process with the major communities and stakeholders in the ecosystem, including the all of the [endorsers](endorsement.md). +The findings from this consultation process will be presented to the Alliance's Internal Strategy Group (ISG), who will have a week to veto or ask for more time +(where silence is implied consent). Consensus from the 2 co-leads and 2 technical leads (see [Current Roles](#current-roles)) will be required to take action +(either accept or reject). Review for these changes will happen twice per year during the first year, and yearly thereafter. + +## Versioning + +All notable changes to this project will be documented in the [CHANGELOG](CHANGELOG.md) +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): + +* *MAJOR version when you make incompatible API changes*: [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) +* *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) +* *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) + +# Current Roles + +* [Liv Marte Nordhaug](https://github.com/livmarte), Secretariat Co-Lead +* [Lucy Harris](https://github.com/lucyeoh), Secretariat Co-Lead +* [Christer Gundersen](https://github.com/christer-io), Technical Lead +* [Victor Grau Serrat](https://github.com/lacabra), Technical Lead, current moderator. From 60aeaf9489a5c49a4b80904c6230fe56abcbde1e Mon Sep 17 00:00:00 2001 From: Victor Date: Wed, 14 Oct 2020 16:56:47 -0600 Subject: [PATCH 07/18] DOC: added CHANGELOG.md --- CHANGELOG.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 CHANGELOG.md diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..d6637e0 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,5 @@ +# Changelog +All notable changes to this project will be documented in this file. + +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), +and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). From 3e2e79be62f24970a004f7cc397e84ff9dde3f17 Mon Sep 17 00:00:00 2001 From: Victor Date: Wed, 14 Oct 2020 17:08:18 -0600 Subject: [PATCH 08/18] DOC: added governance mention in README --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index f1e5515..45ad8fd 100644 --- a/README.md +++ b/README.md @@ -34,6 +34,10 @@ Add yours by editing the [file](endorsement.md), and submitting a Pull Request o The Digital Public Goods Alliance is dedicated to building a welcoming, diverse and safe community. We expect everyone participating in the Digital Public Goods Alliance community to abide by our [**Code of Conduct**](CODE_OF_CONDUCT.md). Please read it. Please follow it. In the Digital Public Goods Alliance, we work hard to build each other up and create amazing things together. 💪💜 +## ⚖️ Governance + +At the Digital Public Goods Alliance, we envision a growing community of contributors and stakeholders around the Digital Public Goods 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 standard, and managing clear expectations around these processes. + ## 🙏 Acknowledgements Thank you to all the individuals that contributed to and [endorsed](endorsement.md) the standard, as well as well as to the participants of the **Early Grade Reading Community of Practice**. We also thank the following organizations: UNICEF, Norway, iSPIRT, Sierra Leone and the DPG Alliance Secretariat. From 139844eeb8208354cab0c9ae051f454e0d8d996d Mon Sep 17 00:00:00 2001 From: Lucyeoh <66376240+Lucyeoh@users.noreply.github.com> Date: Thu, 15 Oct 2020 08:55:52 -0400 Subject: [PATCH 09/18] Minor wording changes --- governance.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/governance.md b/governance.md index aaa5be8..26fc98a 100644 --- a/governance.md +++ b/governance.md @@ -2,8 +2,9 @@ This is work in progress. -The purpose of this document is to present how the Digital Public Goods Alliance envisions governing a growing community of -contributors and stakeholders around the Digital Public Goods Standard. +The purpose of this document is to present how the Digital Public Goods Alliance envisions engaging a growing community of +contributors and stakeholders around the Digital Public Goods Standard. Our ambition is to balance responsiveness to feedback, +with stability and predictabilty for the standard so that it can be a framework that people can build for and to. ## Principles @@ -25,18 +26,17 @@ community to embrace it. Here's an excerpt on our pledge: ## Revisions This section documents the processes for: -* proposing modifications to the current version of the standard, +* proposing modifications to the current version of the standard * reviewing proposed changes * and incorporating them in forthcoming revisions The latest version of the [Digital Public Goods Standard](standard.md) is found at the root folder of this repository. The standard is operationalized through a [questionary](standard-questions.md). This set of questions is used to screen -projects or products, and validate whether they conform to the standard, and can thus be -legitimately classified as Digital Public Goods. +projects or products, and validate whether they conform to the standard, and can thus be classified as Digital Public Goods. ### Priority -Our priority for Q4 2020 is to consolidate the standard. Thus, we ask all comments and edits to be centered around the standard +Our priority for Q4 2020 is to arrive at a stable version of the standard. Thus, we ask all comments and edits to be centered around the standard rather than the associated set of questions. The rationale is that if the standard were to change in a significant way over the initial months, so would the questionary; and any preliminary work on the questions may need to be discarded. @@ -66,7 +66,7 @@ that alter the existing indicators in significant ways, have implications across These may also include reorganization of the various sections of the standard, removing existing sections altogether, or adding new indicators to the standard. * [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) These involve -fundamental or philosophical changes taht challenge the purpose, the scope or the very existence of the standard. +fundamental or philosophical changes that challenge the purpose, the scope or the very existence of the standard. ## Proposal review From caba01f725b8bfe84fa8568a7f5ad4c380cd0c88 Mon Sep 17 00:00:00 2001 From: Don Marti Date: Tue, 20 Oct 2020 09:57:13 -0700 Subject: [PATCH 10/18] Add link and affiliation for Don Marti --- endorsement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/endorsement.md b/endorsement.md index 0586f2b..f36b494 100644 --- a/endorsement.md +++ b/endorsement.md @@ -30,5 +30,5 @@ Full Name | Title | Organization [Lucy Harris](https://github.com/lucyeoh) | Secretariat Co-Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) [Georg J.P. Link](https://github.com/GeorgLink) | Open Source Strategist | [CHAOSS](https://chaoss.community/) Jon Lloyd | Director of Campaigns at Mozilla Foundation | [Mozilla Foundation](https://foundation.mozilla.org/en/) -Don Marti | | +[Don Marti](https://github.com/dmarti) | VP, Ecosystem Innovation | [CafeMedia](https://cafemedia.com/) [Liv Marte Nordhaug](https://github.com/livmarte) | Secretariat Co-Lead, Digital Public Goods Alliance | [Digital Public Goods Alliance](https://digitalpublicgoods.net) From 62e73c5c94ae00e7f633cc438fe602a784314e4f Mon Sep 17 00:00:00 2001 From: Victor Date: Tue, 20 Oct 2020 13:25:47 -0600 Subject: [PATCH 11/18] BLD: removed transparency section --- standard-questions.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/standard-questions.md b/standard-questions.md index 8561027..444c39d 100644 --- a/standard-questions.md +++ b/standard-questions.md @@ -158,7 +158,7 @@ This document contains the set of questions that are being asked to assess each
  • If yes - Does this project share this data with third parties?
  • Please describe the circumstances with which this project shares data with third parties. Please add links as relevant
  • If yes - Does the project ensure the privacy and security of this data and has it taken steps to prevent adverse impacts resulting from it's collection, storage and distribution
    • -
  • Please describe
    • +
  • If yes - please describe, and include a link to the privacy policy and/or terms of service
    • @@ -185,15 +185,6 @@ This document contains the set of questions that are being asked to assess each - - Transparency - -
      -
    • Does this project have a clearly discoverable privacy policy and/or terms of service?
      • -
    • Please provide a link
      • -
    - - Child Online Safety From 83de24acfadd25361b263ce9680606b92db82db1 Mon Sep 17 00:00:00 2001 From: Victor Grau Serrat Date: Tue, 20 Oct 2020 15:59:23 -0600 Subject: [PATCH 12/18] merge master --- standard-questions.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/standard-questions.md b/standard-questions.md index 444c39d..8ab828d 100644 --- a/standard-questions.md +++ b/standard-questions.md @@ -131,7 +131,7 @@ This document contains the set of questions that are being asked to assess each - 9. Does the project do no harm? + 9. Does the project do no harm? Has this project taken steps to anticipate, prevent and do no harm?
      @@ -185,14 +185,5 @@ This document contains the set of questions that are being asked to assess each
    - - Child Online Safety - -
      -
    • Does the project address the safety and security of underage users?
      • -
    • Please describe
      • -
    - - From 644568d30a5def0b1f33078f0cbe1dfe5b78f349 Mon Sep 17 00:00:00 2001 From: Victor Date: Tue, 20 Oct 2020 13:17:28 -0600 Subject: [PATCH 13/18] BLD: updated questions around harassment --- standard-questions.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/standard-questions.md b/standard-questions.md index 8ab828d..77f7a2d 100644 --- a/standard-questions.md +++ b/standard-questions.md @@ -141,7 +141,7 @@ This document contains the set of questions that are being asked to assess each - Privacy and freedom + Privacy and Freedom of Expression
    • Does this project have strategies in place to anticipate, respond to and minimize adverse impacts on privacy and freedom of expression where governments or bad actors are believed to be using this projects’s products or services for illegitimate or political purposes
      • @@ -163,7 +163,7 @@ This document contains the set of questions that are being asked to assess each - Inappropriate/Illegal Content + Inappropriate & Illegal Content
      • Does this project collect, store or distribute content?
        • @@ -176,12 +176,14 @@ This document contains the set of questions that are being asked to assess each - Protection from Harassement + Protection from harassment
        • Does this project facilitate interactions with or between users or contributors?
          • -
        • Does the project help users and contributors protect themselves against grief, abuse, and harassment.
          • -
        • Please describe
          • +
        • If yes - does the project take steps to address the safety and security of underage users?
          • +
        • If yes - please describe the steps this project takes to address risk or prevent access by underage users.
          • +
        • If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment.
          • +
        • If yes - please describe the steps taken to help users protect users and contributors.
        From f5ef592ef2c694ca22a71b9af0aa1232a3691b25 Mon Sep 17 00:00:00 2001 From: Victor Date: Tue, 20 Oct 2020 13:29:51 -0600 Subject: [PATCH 14/18] MAINT: added numbers to 9.x sections --- standard-questions.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/standard-questions.md b/standard-questions.md index 77f7a2d..6f6bc2b 100644 --- a/standard-questions.md +++ b/standard-questions.md @@ -141,7 +141,7 @@ This document contains the set of questions that are being asked to assess each - Privacy and Freedom of Expression + 9.a. Privacy and Freedom of Expression
        • Does this project have strategies in place to anticipate, respond to and minimize adverse impacts on privacy and freedom of expression where governments or bad actors are believed to be using this projects’s products or services for illegitimate or political purposes
          • @@ -150,7 +150,7 @@ This document contains the set of questions that are being asked to assess each - Data Privacy & Security + 9.b. Data Privacy & Security
          • Does this project collect or store personally identifiable data?
            • @@ -163,7 +163,7 @@ This document contains the set of questions that are being asked to assess each - Inappropriate & Illegal Content + 9.c. Inappropriate & Illegal Content
            • Does this project collect, store or distribute content?
              • @@ -176,7 +176,7 @@ This document contains the set of questions that are being asked to assess each - Protection from harassment + 9.d. Protection from harassment
              • Does this project facilitate interactions with or between users or contributors?
                • From af6fc80fd84598e259379b000e7eec8cf0605f53 Mon Sep 17 00:00:00 2001 From: Victor Date: Tue, 20 Oct 2020 15:32:27 -0600 Subject: [PATCH 15/18] MAINT: minor HTML tweak in colspan --- standard-questions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard-questions.md b/standard-questions.md index 6f6bc2b..91e5f8e 100644 --- a/standard-questions.md +++ b/standard-questions.md @@ -131,7 +131,7 @@ This document contains the set of questions that are being asked to assess each - 9. Does the project do no harm? + 9. Does the project do no harm? Has this project taken steps to anticipate, prevent and do no harm?
                  From 6b52b45f6c62293b8ff9d1d877552b7412b76cc6 Mon Sep 17 00:00:00 2001 From: Victor Grau Serrat Date: Tue, 20 Oct 2020 15:50:31 -0600 Subject: [PATCH 16/18] DOC: release v1.0.1 --- CHANGELOG.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index d6637e0..3146687 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,3 +3,22 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). + +## [1.0.1] 2020-10-20 + +### Added +- Added `standard-questions.md` (#10) +- Created `governance.md` (#13) +- Added `CHANGELOG.md` (#14) + +### Removed +- Moved questions from section around online child safety into "9.d Protection from Harassment" where they belong (#16) +- Removed transparency section from `standard-questions.md` since that section is not present in the standard (#17) + +## [1.0.0] 2020-09-15 + +### Added +- 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. + +[1.0.1]: https://github.com/unicef/publicgoods-candidates/compare/v1.0.0...v1.0.1 +[1.0.0]: https://github.com/unicef/publicgoods-candidates/releases/tag/v1.0.0 From 4bdea8ed35220f8b131715eb4cf6c933ce66832e Mon Sep 17 00:00:00 2001 From: Victor Grau Serrat Date: Tue, 20 Oct 2020 16:03:06 -0600 Subject: [PATCH 17/18] MAINT: added links for CC-BY and CC-BY-SA --- standard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard.md b/standard.md index 3a7025e..d46e415 100644 --- a/standard.md +++ b/standard.md @@ -7,7 +7,7 @@ Indicator | Requirement --- | --- **1. Relevance to Sustainable Development Goals** | All projects must indicate the SDG(s) 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 and CC-BY-SA), 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 a [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 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).* **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. **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. From 03dd6a3b58c759febdfd67be4f735dc756a89e2f Mon Sep 17 00:00:00 2001 From: Victor Grau Serrat Date: Tue, 20 Oct 2020 16:07:43 -0600 Subject: [PATCH 18/18] DOC: updated CHANGELOG to v1.0.2 --- CHANGELOG.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3146687..02b3509 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [1.0.2] 2020-10-20 + +### Changed +- Clarified wording around CC licenses (#11) + ## [1.0.1] 2020-10-20 ### Added @@ -20,5 +25,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Added - 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. +[1.0.2]: https://github.com/unicef/publicgoods-candidates/compare/v1.0.1...v1.0.2 [1.0.1]: https://github.com/unicef/publicgoods-candidates/compare/v1.0.0...v1.0.1 [1.0.0]: https://github.com/unicef/publicgoods-candidates/releases/tag/v1.0.0