DPGAlliance · lacabra · Oct 20, 2020 · Sep 24, 2020 · Oct 6, 2020 · Oct 6, 2020
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -0,0 +1,30 @@
+# 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).
+
+## [1.0.2] 2020-10-20
+
+### Changed
+- Clarified wording around CC licenses (#11)
+
+## [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.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
diff --git 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.

diff --git a/endorsement.md b/endorsement.md
@@ -21,12 +21,14 @@ 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/)
 [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/)
-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)
diff --git a/governance.md 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 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
+
+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 classified as Digital Public Goods.
+
+### Priority
+
+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.
+
+### 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 that 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.
diff --git 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
             </td>
         </tr>
         <tr>
-            <td rowspan="7" valign="top">9. Does the project do no harm? </td>
+            <td rowspan="5" valign="top">9. Does the project do no harm? </td>
             <td valign="top">Has this project taken steps to anticipate, prevent and do no harm? </td>
             <td valign="top">
                 <ul>
@@ -141,7 +141,7 @@ This document contains the set of questions that are being asked to assess each
             </td>
         </tr>
         <tr>
-            <td valign="top">Privacy and freedom</td>
+            <td valign="top">9.a. Privacy and Freedom of Expression</td>
             <td valign="top">
                 <ul>
                     <li>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</li>
@@ -150,20 +150,20 @@ This document contains the set of questions that are being asked to assess each
             </td>
         </tr>
         <tr>
-            <td valign="top">Data Privacy &amp; Security</td>
+            <td valign="top">9.b. Data Privacy &amp; Security</td>
             <td valign="top">
                 <ul>
                     <li>Does this project collect or store personally identifiable data?</li>
                     <li>If yes - Please list the types of data collected and/or stored by the project</li>
                     <li>If yes - Does this project share this data with third parties?</li>
                     <li>Please describe the circumstances with which this project shares data with third parties. Please add links as relevant</li>
                     <li>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&#39;s collection, storage and distribution</li>
-                    <li>Please describe</li>
+                    <li>If yes - please describe, and include a link to the privacy policy and/or terms of service</li>
                 </ul>
             </td>
         </tr>
         <tr>
-            <td valign="top">Inappropriate/Illegal Content</td>
+            <td valign="top">9.c. Inappropriate &amp; Illegal Content</td>
             <td valign="top">
                 <ul>
                     <li>Does this project collect, store or distribute content?</li>
@@ -176,30 +176,14 @@ This document contains the set of questions that are being asked to assess each
             </td>
         </tr>
         <tr>
-            <td valign="top">Protection from Harassement</td>
+            <td valign="top">9.d. Protection from harassment</td>
             <td valign="top">
                 <ul>
                     <li>Does this project facilitate interactions with or between users or contributors?</li>
-                    <li>Does the project help users and contributors protect themselves against grief, abuse, and harassment.</li>
-                    <li>Please describe</li>
-                </ul>
-            </td>
-        </tr>
-        <tr>
-            <td valign="top">Transparency </td>
-            <td valign="top">
-                <ul>
-                    <li>Does this project have a clearly discoverable privacy policy and/or terms of service?</li>
-                    <li>Please provide a link</li>
-                </ul>
-            </td>
-        </tr>
-        <tr>
-            <td valign="top">Child Online Safety</td>
-            <td valign="top">
-                <ul>
-                    <li>Does the project address the safety and security of underage users?</li>
-                    <li>Please describe</li>
+                    <li>If yes - does the project take steps to address the safety and security of underage users?</li>
+                    <li>If yes - please describe the steps this project takes to address risk or prevent access by underage users.</li>
+                    <li>If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment.</li>
+                    <li>If yes - please describe the steps taken to help users protect users and contributors.</li>
                 </ul>
             </td>
         </tr>