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.

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

Add section on website for community labels #180

Closed
ninadicara opened this issue Sep 19, 2023 · 1 comment
Closed

Add section on website for community labels #180

ninadicara opened this issue Sep 19, 2023 · 1 comment
Assignees

Comments

@ninadicara
Copy link
Contributor

ninadicara commented Sep 19, 2023

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).

@ninadicara
Copy link
Contributor Author

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants