Updating "project" to "digital solution"

[Lucyeoh]

Fixes #57.

Changes proposed in this pull request:

The term "project" conflates the specific solution and the context or environment in which it is being implemented, used, or deployed. As the DPG Standard strives to assess the societal value of the "good" (software, content collection, data set) itself it is important to increase the precision of the language we use.

Therefore we are proposing replacing the term "project" throughout the DPG standard to "digital solution". See files changed to view all of the implications of this change.

As per the Standard Governance this issue is now open for two weeks for additional input from the community. We will inform the members of the DPGA's Internal Strategy Group (ISG) 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) will be required to accept or reject these proposals.

Propagation of Changes

Identify where of the following the proposed changes need to be propagated, and include the relevant pull request where appropriate:

• The DPGA website contains https://digitalpublicgoods.net/standard/ which needs to be updated manually matching the contents of standard.md.
• The DPGA website also contains the submission guide which needs to be updated manually.
• The unicef/publicgoods-candidates repository needs the following to be updated:
  • the nominee-schema.json
  • the screening-schema.json
  • propagate any changes to all encoded nominees and digital public goods.
  • Link to the corresponding pull request: unicef/publicgoods-candidates#
• The Submission Form through the unicef/publicgoods-submission repository, and its corresponding schema.js
  • Link to the corresponding pull request:
• The Eligibility Form through the unicef/publicgoods-scripts repository, by editing quizQuestions.js
  • Link to the corresponding pull request:

[Lucyeoh]

From @livmarte I understand the need to change focus from project to digital solution (ref. issue 3), but ref. the issue below: a digital solution can’t state anything. That is giving agency to a non-living thing. It still must be a person speaking on behalf of a digital solution, who takes some kind of responsibility for its’ design? But I guess this applies to several indicators?

Hence; Can it be “the digital solution has been designed and developed to comply with relevant privacy laws”, and then in one place at the end – the person nominating/filling in this info, who must be in a position to speak for the digital solution, writes “I confirm that I have filled out all the information above to the best of my knowledge”? Thoughts? I am sure some of this has been discussed already.

From @Lucyeoh I really like this suggestion, we actually do ask between indicators 6-7 that the person filling out the form confirms they have authority to speak on behalf of the project so changing the language to "the digital solution has been designed and developed to comply with relevant privacy laws" makes a lot of sense.

[prajectory]

Draft proposal to accommodate these changes:

7. Adherence to Privacy and Applicable Laws | The digital solution must be designed and developed to comply with relevant privacy laws, and all applicable international and domestic laws.

8. Adherence to Standards & Best Practices | Digital solutions 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 | All digital solutions must be designed to anticipate, prevent, and do no harm by design.

9a) Data Privacy & Security | Digital solutions designed to collect data must indicate the types of data they were designed to collect and store. Solutions must also demonstrate how they have been designed to ensure the privacy and security of this data in addition to how to design of the solution prevents adverse impacts resulting from its collection, storage and distribution.

9b) Inappropriate & Illegal Content | Digital solutions designed to collect, store or distribute content must have mechanisms for identifying inappropriate and illegal content such as child sexual abuse materials in addition to mechanisms for detecting, moderating and removing inappropriate/illegal content.

9c) Protection from Harassment | If the digital solution was designed to facilitate interactions with or between users or contributors there must be a mechanism for users and contributors to protect themselves against grief, abuse, and harassment. The solution must have a mechanism to address the safety and security of underage users.

The questionary will also change to accommodate language. Note: At no point do we give the solution itself agency in this process?