diff --git a/governance.md b/governance.md index 1ff3fe1..fa4c5da 100644 --- a/governance.md +++ b/governance.md @@ -1,121 +1,126 @@ # Digital Public Goods Standard Governance -This is a work in progress. +This governance model aims to provide a comprehensive framework for developing and maintaining the Digital Public Goods (DPG) Standard in alignment with the [Digital Public Goods Alliance (DPGA)'s mission and values](https://digitalpublicgoods.net/digital-public-goods-alliance-strategy-2023-2028/). The DPGA envisions engaging with a growing community of contributors and stakeholders to ensure a balance between responsiveness to feedback, stability, and predictability for the DPG Standard, so it can be a framework that people can build for and to. -The purpose of this document is to share how the Digital Public Goods Alliance (DPGA) envisions engaging a growing community of contributors and stakeholders around the Digital Public Goods (DPG) Standard. Our goal is to balance responsiveness to feedback, with stability and predictabilty for the DPG Standard so it can be a framework that people can build for and to. +The DPG Standard leverages frameworks, standards, and definitions from specific organisations that have broad international consensus and are facilitating the discovery, development, use of, and investment in digital public goods. Specific organisations the DPG Standard aligns with include: Open Source Initiative (OSI), Creative Commons, and Open Data Commons (Open Knowledge Foundation). -The DPG Standard leverages frameworks, standards and definitions from specific organizations that have broad market consensus and are facilitating the discovery, development, use of, and investment in digital public goods. Specific organizations the DPG Standard aligns with include: Open Source Initiative (OSI) also member of the DPGA alliance, Creative Commons, and Open Data Commons. - -## Principles +## 1. Principles The DPGA community adheres to the [OpenStand Principles](openstand.md) when developing the DPG standard. -## Code of Conduct +Additionally, the DPGA Standard governance process through its Expert groups and community engagements also follows the following principles: +- **Inclusivity**: Ensuring participation and representation from a diverse range of contributors and stakeholders across geography and gender. +- **Transparency**: Conducting processes openly and sharing relevant information with the community on GitHub. +- **Accountability**: Assigning clear roles and responsibilities to individuals within the governance structure which will be delineated in the Terms of References for any organised community engagements like standard Expert Groups. +- **Collaboration**: Promoting active collaboration among contributors through constructive discussions on a regular basis on platforms such as GitHub. +- **Responsiveness**: Adapting to community feedback and stakeholder interaction, and evolving needs while maintaining stability. + -We have adopted the [Contributor Covenant Code of Conduct v2](CODE_OF_CONDUCT.md), and expect all members of the -community to embrace it. The following is an excerpt on our pledge: +## 2. Code of Conduct -*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 have adopted the [Contributor Covenant Code of Conduct](https://github.com/DPGAlliance/DPG-Standard/blob/main/CODE_OF_CONDUCT.md), and expect all members of the community to embrace it. The following is an excerpt on our pledge: -*We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.* +_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, caste, colour, religion, or sexual identity and orientation._ -## Revisions +_We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community._ + +## 3. Revisions The following section showcases the processes for: -* proposing modifications to the current version of the DPG Standard -* reviewing proposed changes -* incorporating proposed changes in forthcoming revisions +* Input mechanisms through public processes and expert inputs +* The change proposal process including classifications of modifications and community comments The latest version of the [Digital Public Goods Standard](standard.md) is found in the root folder of this repository. -The DPG Standard is operationalized through a [questionary](https://app.digitalpublicgoods.net/form). This set of questions is used to screen -projects or products, and validate whether they conform to the DPG Standard, and can thus be classified as digital public goods. +The DPG Standard is operationalized through a [questionary](https://app.digitalpublicgoods.net/form). This set of questions is used to screen projects or products and validate whether they conform to the DPG Standard, and can thus be classified as digital public goods. -### Priority +### 3A. Input mechanisms -Our priority for year 2023 is to establish a stable version of the DPG Standard that encompasses specific requirements for open standard, open data, open AI solutions. To do so, we ask for all comments and edits to be centered around the DPG Standard rather than the associated set of questions. The rationale being if the DPG Standard were to significantly change, so would the questionary, therefore any preliminary work on the questions may need to be discarded. +Participation mechanisms ensure that individuals, organisations, and stakeholders have opportunities to contribute to the development of the DPG Standard. This includes engaging in discussions, proposing changes, and providing feedback. -### Proposing Changes +There are two mechanisms for the DPGA to gather input on the DPG Standard. -These are the suggested steps for proposing changes to the DPG Standard: -- Start an issue: You can create [an issue](https://github.com/DPGAlliance/DPG-Standard/issues) to suggest changes and invite other community members to weigh in with their thoughts -OR -- Start a Pull Request -- First, to avoid duplication, review the existing [Pull Requests](https://github.com/DPGAlliance/DPG-Standard/pulls) to see if your proposed change -has already been proposed or not. If it has already been proposed, you are encouraged to add your perspective -to the existing proposed change and argue for or against it with 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 when making the case for your suggested changes. If your -contribution is commentary or a general opinion, we will still review it, but we will deem it nonactionable and close it. -- Once your pull request has been submitted, follow the discussion that ensues. +**3a(i). Public Proposal Process - GitHub** -### Classification of Modifications +Anyone can propose changes to the standard using GitHub by: +- [Creating an issue](https://github.com/DPGAlliance/DPG-Standard/issues/new): You can create an issue to suggest changes, share thoughts and invite other community members to weigh in with their thoughts OR +- [Creating a Pull Request](https://github.com/DPGAlliance/DPG-Standard/edit/main/standard.md): You can edit the text of the Standard directly and make a pull request to propose your specific wording changes. -In order to streamline the review of proposals, we will use the following classifications and labelling them accordingly: +Before starting we recommend following these steps: +1. To avoid duplication, review the existing [issues](https://github.com/DPGAlliance/DPG-Standard/issues) and [pull requests](https://github.com/DPGAlliance/DPG-Standard/pulls) to see if your proposed change has already been proposed or not. If it has already been proposed, you are encouraged to add your perspective to the existing conversation and argue for or against it with constructive and compelling arguments. +2. If none of the open pull requests/issues address the issue you are proposing, start a new issue or edit the standard 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 when making the case for your suggested changes. If your contribution is commentary or a general opinion, we will still review it, but we will deem it non-actionable and close it. +3. Once your pull request has been submitted, follow the discussion that ensues. -* [![](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 -are mostly stylistic edits that include, but are not limited to: correcting typographical errors, making gramatical edits, adding or removing clarifying -statements with the aim of improving readibility, or facilitating understanding of the DPG Standard to the reader. These proposed changes do not alter the -intended meaning of the existing indicators, nor introduce or remove key concepts. +**3b(ii). Expert Input - Standard Expert Groups** -* [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change) These are modifications -that alter the existing indicators in significant ways that have broader implications, but they do not challenge the purpose or scope of the DPG Standard. -These may also include reorganization of the various sections of the DPG Standard, removing existing sections entirely, or adding new indicators to the DPG Standard. +Expert groups serve as forums for discussions and initiating amendments in areas where the Secretariat (via the Standards Council) identifies the need for greater discussion and guidance from the community on a topic. Expert groups are responsible for creating annexures of best practices for applicant compliance, researching, proposing modifications, and reviewing changes. They propose recommendations based on their discussions and deliberations. These proposals are submitted to the DPG Standard Council for review and consideration. Each proposal outlines specific changes, enhancements, or additions to the DPG Standard. Expert groups are comprised of external subject matter experts who participate in their personal capacity to ensure neutrality in standard development. To read more about the expert groups go [here](https://github.com/DPGAlliance/DPG-Standard/blob/main/expert-groups.md). -* [![](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, scope, or very existence of the DPG Standard. +### 3B. The Change Proposal Process -## Proposal Review +Once changes have been proposed, the Change Proposal Process is a crucial mechanism within the governance framework of the Digital Public Goods Standard to ensure that proposed changes to the standard undergo thorough review, consideration, and community engagement before being finalised and implemented. -The process for reviewing and accepting proposals varies depending on the classification of the proposal: +**3b(i) Proposing changes** -* [![](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 of accepting additional comments 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, there -are monthly meetings to catch and address any outstanding issues. +Proposed changes to the DPG Standard made in the form of issues and/or pull requests through GitHub, which will then be taken up for discussion by the Standard Council. If the suggested changes are approved, these proposed changes will be published on GitHub for public comments for timeframes based on the type of change made (see below). This allows for transparency and accessibility, allowing stakeholders to review and provide feedback on proposed changes. -* [![](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 DPGA for further investigation over a period of up to two weeks. That person will report 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 [DPGA's Governance Board](https://digitalpublicgoods.net/governance/) (the Board) giving them an equal opportunity to comment. Reviewing these changes will happen quarterly. Consensus from the 2 co-leads and 2 technical leads -(see [Current Roles](#current-roles)) will be required to accept or reject these proposals. +**3b(ii) Classifications of Modifications** -* [![](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 significant communities and stakeholders throughout the ecosystem, including all [endorsers](endorsement.md). -The findings from this consultation process will be presented to the[DPGA's Governance Board](https://digitalpublicgoods.net/governance/) (the Board) , 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 -either accept or reject the proposal. Reviewing these changes will occur twice per year during the first year, and yearly thereafter. +All incoming issues will be classified as follows: -## Versioning +* [![](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 are mostly stylistic edits that include, but are not limited to: correcting typographical errors, making grammatical edits, adding or removing clarifying statements with the aim of improving readability, or facilitating understanding of the DPG Standard to the reader. These proposed changes do not alter the intended meaning of the existing indicators, nor introduce or remove key concepts. -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): +* [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change) - These are modifications that alter the existing indicators in significant ways that have broader implications, but they do not challenge the purpose or scope of the DPG Standard. These may also include reorganisation of the various sections of the DPG Standard, removing existing sections entirely, or adding new indicators to the DPG Standard. -* *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) +* [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) - These involve fundamental or philosophical changes that challenge or affect the purpose, scope, or very existence of the DPG Standard. + +**3b(iii) Community Comments** + +Community engagement is a key aspect of the Change Proposal Process. Stakeholders, including individuals, organisations, and interested parties, are invited to review the proposed changes and provide feedback. The duration for community comments varies depending on the significance of the proposed change: + +- [![](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) - Stakeholders have one week to review and provide feedback on minor fixes, which typically involve small adjustments or corrections to the standard. +- [![](https://img.shields.io/badge/-major_change-FFA500)](https://github.com/DPGAlliance/DPG-Standard/labels/major%20change) - For more substantial changes, stakeholders have three weeks to review and provide feedback. Major changes may include but not be limited to revisions to existing indicators of the standard or the introduction of new elements within specific indicators. +- [![](https://img.shields.io/badge/-fundamental-b60205)](https://github.com/DPGAlliance/DPG-Standard/labels/fundamental) - For significant revisions that impact the core principles or structure of the DPG Standard, stakeholders have four weeks to review and provide feedback. This allows for in-depth analysis and discussion of the proposed fundamental changes + +**3b(iv) Amendments Review by Standard Council** + +Following the community comment period, the proposed amendments, along with the feedback received, are classified and reviewed by the Standard Council. The council evaluates the proposed changes, taking into account technical feasibility, alignment with organisational goals, and feedback from the community and stakeholders. + +**3b(v) Final Updates Publication and Implementation** + +After thorough review and consideration, final updates to the DPG Standard are published on GitHub. These updates reflect any revisions or modifications based on community feedback and council review. Once published, the updated standard is implemented, ensuring that stakeholders have access to the latest version of the standard for reference and adoption. + +## 4. Decision Making: Standard Council -### Releasing a New Version +The Standard Council serves as the governing body responsible for stewarding and overseeing the development and maintenance of the Digital Public Goods Standard. To uphold the neutrality of the standard, the council comprises Secretariat Staff members. This ensures that decision-making processes remain impartial and aligned with the goals of the Digital Public Goods Alliance. -Follow these steps to release a new version: +It's important to note that the Standard Council functions as a facilitator reviewing, organising and consolidating feedback from the community, ensuring that the standard is developed through a well-planned and transparent process. They play a crucial role in facilitating discussions, coordinating efforts, and ensuring that the standard evolves in line with the community's needs and objectives. -1. Document your upcoming changes in `CHANGELOG.md`. Follow the existing structure and be consistent with the order of subsections: `Added`, `Changed`, `Deleted`. Also be sure to link the version in the diff list at the very bottom of the CHANGELOG. -2. Update the version number in both `standard.md` and `README.md`. -3. Commit all the changes that will be included in the new version. -4. Tag the last commit, for example, for version 1.0.1: - ```bash - git tag -a v1.0.1 -m "Version 1.0.1" - ``` -5. Push the tag to the origin: - ```bash - git push origin --tags - ``` -6. Visit https://github.com/DPGAlliance/DPG-Standard/releases and click on `Draft a New Release`: - - Select the version you just tagged above in step 3 - - Enter the `Release title`, for example `v1.0.1` consistent with the preceeding steps. - - In the `Describe this release`, copy and paste the text from the CHANGELOG for this version in *raw form* (it's markdown after all). Preview and verify that it looks good (you can edit this information again later, no big deal if something is wrong in the description). +The council is composed of [Secretariat staff members](https://digitalpublicgoods.net/digital-public-goods-alliance-secretariat/) dedicated to ensuring responsiveness to feedback, stability, and predictability for the DPG Standard. Their responsibilities include facilitating decision-making processes, strategic planning, and ensuring alignment with the goals of the Digital Public Goods Alliance. -## Propagating Changes +**4a. The council's composition includes** + +- A Core Team consisting of key secretariat staff: Chief Operations Officer, Chief Technology Officer, and Standards Lead. +- Observer members, including the Director of Communications & Programs and Technical Specialist Coordinator contribute insights and perspectives to Standard Council discussions. +- Contributors invited in an advisory capacity, when required, include specialists from the DPGA Secretariat and DPG Standard Expert group co-convenors. + +Any potential changes to the DPG Standard require approval by the Standard Council, ensuring that decisions are made based on sound input, collaboratively and in alignment with organisational objectives. + +Decision-making within the Standard Council is consensus-based, with all members contributing to discussions and reaching agreement on topics of importance. Advisory members provide suggestions, while Contributors offer specialised expertise relevant to the discussion at hand. + +**4b. Impasse resolution** + +In the event of an impasse, a formal voting mechanism is used, with each member casting a single vote. A supermajority vote is required to break the impasse and determine the outcome. Additionally, the COO considers suggestions provided by advisory members before formalising decisions. Following discussions in the Standard Council, any decisions regarding fundamental changes in the DPG Standard need to be approved by the Chief Executive Officer of the DPGA, after which they are opened for comments from the Community. + +Transparency measures are implemented through the publication of relevant Standard Council meeting outcomes on GitHub on a regular basis. These outcomes are open for public comments, fostering transparency and accountability in the standard-setting process. + +## 5. 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) + +## 6. Propagating Changes This repository [DPGAlliance/DPG-Standard](https://github.com/DPGAlliance/DPG-Standard) is the source of truth for any information pertaining to the **Digital Public Goods Standard**, and any changes to the information contained herein need to be propagated and synced with the following list of resources, where applicable: @@ -125,9 +130,12 @@ This repository [DPGAlliance/DPG-Standard](https://github.com/DPGAlliance/DPG-St 5. The [Eligibility Form](https://digitalpublicgoods.net/eligibility/) through the [unicef/publicgoods-scripts](https://github.com/unicef/publicgoods-submission) repository, by editing [quizQuestions.js](https://github.com/unicef/publicgoods-scripts/blob/master/packages/eligibility/src/api/quizQuestions.js) -# Current Roles +## 7. Appeal Mechanism + +In order to maintain transparency, fairness, and the principles of neutrality within the governance of the Digital Public Goods Standard, an appeal mechanism is established to address concerns or disputes regarding decisions made by the Standards Council. + +If any member of the community wishes to appeal a decision, they may initiate the appeal process by creating a pull request on GitHub. This pull request should be addressed to both the Standards Council and the CEO of DPGA, outlining the reasons for the appeal. -* [Liv Marte Nordhaug](https://github.com/livmarte) Secretariat Co-Lead /OOO[Lucy Harris](https://github.com/lucyeoh) -* [Christer Gunderson](https://github.com/christer-io), Technical Advisor -* [Prajakta Kuwalekar](https://github.com/prajectory), Product Manager, current Moderator +Upon receipt of the appeal, the Standards Council will carefully review the decision and provide a detailed justification for its position. The CEO of DPGA will then consider the appeal, taking into account the justification provided by the Standards Council, as well as any additional information or arguments presented by the appellant. +This comprehensive approach ensures that all voices are heard and considered in the decision-making process. By involving multiple stakeholders and providing an avenue for appeal, the appeal mechanism upholds the integrity of the governance process and fosters trust within the community.