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.
Situation
Data Hazards currently uses a versioning system for versions of the main labels, with the intention being that these can be periodically revised and new labels (or changes to labels) added to the new version.
Problem
At the moment there isn't anywhere on the website for suggested labels to live - it wouldn't make sense to put them with the agreed and versioned labels, but equally they need to go somewhere so the community can look at and review them (ideally that doesn't require using GitHub).
Suggested Solution
To have a section on the website where newly suggested labels can be added. This could be underneath the main labels on the labels page, or a secondary page.
These labels may not have an icon, but should have a description etc.
We can make a PR template to make it simple for people to suggest them.
By making suggestions public we can also credit people earlier for their ideas, rather than just when the versioning is revised (which is not planned to be very frequent).
Different idea for this - made a label to specifically collect Hazard suggestions and link to this from the webpage. This is more efficient and non GitHub users can still browse the suggestions :)
Situation Data Hazards currently uses a versioning system for versions of the main labels, with the intention being that these can be periodically revised and new labels (or changes to labels) added to the new version.
Problem At the moment there isn't anywhere on the website for suggested labels to live - it wouldn't make sense to put them with the agreed and versioned labels, but equally they need to go somewhere so the community can look at and review them (ideally that doesn't require using GitHub).
Suggested Solution To have a section on the website where newly suggested labels can be added. This could be underneath the main labels on the
labels
page, or a secondary page. These labels may not have an icon, but should have a description etc. We can make a PR template to make it simple for people to suggest them. By making suggestions public we can also credit people earlier for their ideas, rather than just when the versioning is revised (which is not planned to be very frequent).