Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove 9a #1

Merged
merged 5 commits into from
Nov 9, 2020
Merged

Remove 9a #1

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e7d653c
Remove 9a
Lucyeoh Sep 21, 2020
10652f3
merge master
lacabra Oct 21, 2020
dd4a76c
Merge branch 'master' into Lucyeoh-patch-1
lacabra Oct 22, 2020
e23c0c6
Merge branch 'master' into Lucyeoh-patch-1
lacabra Nov 6, 2020
6178c8a
BLD: removed 9a from standard-questions
lacabra Nov 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,8 @@ Indicator | Requirement
**7. Adherence to privacy and applicable laws** | The project must state that to the best of its knowledge it complies with relevant privacy laws, and all applicable international and domestic laws.
**8. Adherence to standards & best practices** | Projects must demonstrate some adherence to standards, best practices and/or principles. i.e. the principles for digital development
**9. Do No Harm** | All projects must demonstrate that they have taken steps to ensure that the project anticipates, prevents and does no harm.
**9a) Privacy & Freedom of Expression** | All projects must have strategies in place to anticipate, respond to and minimize adverse impacts on privacy and freedom of expression where governments are believed to be using the project’s product or services for illegitimate or political purposes.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are technical approaches to the development of digital public goods that advance this purpose more than others. Perhaps requiring a statement about how the project accomplishes this goal, and to what extent, would be useful for transparency.

I agree that how digital public goods are used is not easily policed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sgoggins: I would like to ask you specifically what is your take on whether strategies in place to anticipate, respond to and minimize adverse impacts on privacy and freedom of expression is intrinsic to the development of digital public goods, or is an external factor tied to the implementation of that good out into the world. If it's the latter, it becomes a matter of policing which I would argue is out of the scope of this standard. On the other hand, if it is intrinsic, it should somehow be part of the standard.

What I am understanding from your statement about how the project accomplishes this goal, and to what extent, would be useful for transparency is something that seems to be under the purview of the the implementing party, and can be separated (completely?) from the actual digital public good.

**9b) Data Privacy & Security** | Projects that collect data must identify the types of data collected and stored and demonstrate that the project ensures the privacy and security of this data and has taken steps to prevent adverse impacts resulting from it’s collection, storage and distribution.
**9c) Inappropriate & Illegal Content** | Projects that collect, store or distribute content must have policies identifying inappropriate and illegal content such as child sexual abuse materials and mechanisms for detecting, moderating and removing inappropriate/illegal content.
**9d) Protection from harassment** | If the project facilitates 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 project must have a mechanism to address the safety and security of underage users.
**9a) Data Privacy & Security** | Projects that collect data must identify the types of data collected and stored and demonstrate that the project ensures the privacy and security of this data and has taken steps to prevent adverse impacts resulting from it’s collection, storage and distribution.
**9b) Inappropriate & Illegal Content** | Projects that collect, store or distribute content must have policies identifying inappropriate and illegal content such as child sexual abuse materials and mechanisms for detecting, moderating and removing inappropriate/illegal content.
**9c) Protection from harassment** | If the project facilitates 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 project must have a mechanism to address the safety and security of underage users.

*NOTE: that evidence for requirements 7-9 can only be given by someone authorized to speak on behalf of the project. We collect title, name and contact information to confirm this authority.*