Skip to content

dpg-review-policy.md

Latest commit

 

History

History
123 lines (92 loc) · 8.5 KB

dpg-review-policy.md

File metadata and controls

123 lines (92 loc) · 8.5 KB

DPG Review Policy

This document lays out the policies that govern the review process of Digital Public Good (DPG) applications.

Table of Contents

  1. Nomination Policy
  2. Application Review Policy
  3. DPG Registry Moderation Policy
  4. DPG Status Renewal Policy
  5. DPG Status Removal Policy
  6. Spam Policy
  7. Roles and Responsibilities
  8. Community Engagement with the DPG Review Team

Nomination Policy

  • Owners of digital solutions who wish to get their solution recognized as a digital public good must nominate their solution by submitting a DPG application.
  • An application can be created and submitted through the DPGA nomination portal at app.digitalpublicgoods.net.
  • The set of questions that are asked as part of the application are transparently available here.
  • Applications can only be submitted by an authorised representative of the digital solution (the applicant).
  • We collect the name and email address of the applicant. Email verification is required to submit an application.
  • Each application is assigned a unique application ID.
  • The content of each submitted application is made publicly available and licensed as such via Unlicense.

Application Review Policy

DPG Application Review Policy

  • Each application is assessed against the latest version of the DPG Standard at the time of creation of the application.
  • The application must meet all the requirements of the DPG Standard to become a DPG.
  • If the application fails to meet one or more requirements, it will be declared as Ineligible.
  • If clarifications are requested and the applicant fails to respond within the time allotted, the application will be automatically declared Ineligible.
  • Every review results in a binary decision: DPG or Ineligible.
  • The final determination on whether a solution adheres to the DPG Standard will be made by the DPGA Secretariat’s Technical Coordinator.
  • We anticipate each application to go through the entire review phase in 4-8 weeks. In some cases, this timeline will extend further due to increased pending backlogs or national holidays.
  • A digital solution recognized as a DPG will be listed on the public DPG Registry and their listing will also be made available to other databases via an API.

DPG Registry Moderation Policy

  • The public DPG Registry displays all digital solutions that are recognized as DPGs.
  • Solutions that appear on the registry as DPGs will be notified and invited to use the DPG term and the DPG badge to describe the digital solution, promote their solution, and link to the DPG Registry.
  • All of the information available on the DPG Registry is openly licensed and made accessible to any other entity wishing to display it via an API - as such information on the DPG registry may be mirrored or used by any number of other entities.
  • On an ongoing basis, DPGs must always be able to demonstrate relevance to the Sustainable Development Goals and use of an approved open license.
  • If at any point a DPG is found to no longer use an open license or be relevant to the SDGs, it will be removed from the DPG Registry. To report a DPG that may no longer meet this criteria please email [email protected].
  • A DPG listing can also be removed at the request of the applicant.

DPG Status Renewal Policy

  • DPG status is valid for one year from the date of completion of review.
  • To ensure that a DPG continues to comply with the latest DPG Standard, they must submit a Renewal application.
  • Renewal applications will be automatically generated by the system 60 days before the DPG expires. The DPG product owner is only expected to log into the dashboard and update any missing or outdated information before the expiration date. If the DPG product owner does nothing before the expiration date, the application will be automatically submitted for review with the previously submitted information.
  • Renewal applications must be edited via the DPGA nomination portal.
  • Upon a re-review, if the solution is found to comply with the latest DPG Standard, it will stay listed on the DPG Registry.

DPG Status Removal Policy

  • DPGA invites the community members to scrutinize the documentation submitted by DPG owners in order to validate their status as a DPG.
  • The review team will deliberate on the issues raised and do either of the following 3 things:
    1. Accept the reservations noted by the community and reach out to the DPG owner over email to seek clarification.
    2. Reject the reservations noted by the community and stick to the decision on validation of a DPG status.
    3. Convene a meeting with the stakeholder who has raised concerns to get a more detailed explanation or additional information.
  • Please note that the final decision for DPG status validation rests with the DPG review team.

Spam Policy

Any application that is deemed nonsensical, malicious, irrelevant, or in violation of our Code of Conduct will not be reviewed and will be removed immediately.

Roles and Responsibilities:

Internal Reviewers / L1

  • They are part of the DPGA team.
  • They attend all reviewer meetings.
  • They coordinate ‘internally’ with experts and the external reviewer.
  • They are responsible for owning the decisions as to which applications become DPGs and which ones are marked as Ineligible.
  • They spend the entire week (regular full-time working hours) pushing applications through the pipeline.
  • They have full access to all applications.

External Reviewers / L2

  • They are part of the DPGA team.
  • They attend all reviewer meetings.
  • They coordinate ‘externally’ with users to ask for and receive clarifications on applications.
  • They are responsible for owning the decisions as to which applications become DPGs and which ones are marked as Ineligible after the clarifications are received.
  • They spend the entire week (regular full-time working hours) pushing applications through the pipeline.
  • They have full access to certain applications.

Expert Reviewers

  • They work part-time with the DPGA team.
  • They may or may not attend the weekly review meetings depending on their availability.
  • They are responsible for giving their expert advice on certain indicators where they specialise when asked for by an internal reviewer.
  • They usually have fixed days or hours where they contribute their time to pushing applications in their pipeline (for example, two full days or four half days)
  • They have limited access to certain applications.

Expert Advisors

  • They are external to the DPGA team but may be part of the larger DPGA member association.
  • They do not attend any meetings with the rest of the DPGA review team.
  • They are responsible for answering a one-off question about a specific application from time to time
  • They do not have any fixed hours of contribution and usually take a few minutes each month to assist the team where they are getting stuck.
  • They don’t access applications at all.

Community Reviewers

  • They are not part of the DPGA team or larger ecosystem. They are people informally interested in reviewing applications.
  • They are not invited to attend any meetings of the DPGA team.
  • They are not ‘responsible’ for any decisions or subsequent actions taken for or on applications.
  • They do not have any fixed timings or commitments. They can informally volunteer their services for as little as one hour a month for 6 months.

Community Engagement with the DPG Review Team

The status of the review of an application is transparently visible on its public URL (digitalpublicgoods.net/r/[ID]). To raise disagreements with a review decision or any other issues related to reviews, please write to us at [email protected].