Data Hazards is a project to find a shared vocabulary for talking about worst-case scenarios of data science - and to use that vocabulary to help people understand and avoid Data Hazards.
We would like to make it easier for people to be credited for contributions to the repository. Our workshops have operated on the basis that people were anonymous, but some would have liked to be credited.
We'd also like to make it clearer that people contributing to the repository will have their suggestions publicly credited on the website.
To do:
[ ] Write letter explaining three ways of collecting feedback and suggested consent process for each
[ ] Paper written suggestions (eg AI UK)
[ ] Formal workshops
[ ] Github contributors like Issues and Pull Requests
[ ] Update the Contributing File with these updates (in branch with issues/PR templates)
[ ] Update workshop Consent Form
Can be credited for specific suggestions or for attending/being a project owner at a workshop
Survey data remains anonymous
[ ] Update workshop Participant Information Sheet with the above
[ ] Draft a PR with the suggested auto-reply for issues and PR template changes, and Contributing File updates
We would like to make it easier for people to be credited for contributions to the repository. Our workshops have operated on the basis that people were anonymous, but some would have liked to be credited. We'd also like to make it clearer that people contributing to the repository will have their suggestions publicly credited on the website.
To do:
Once approved: