We don't have documentation about "triaging"

[mfisher87]

Should we use this term? It's just the term GitHub uses for the role, but we can call it whatever we want. I think the main thing that needs to be explained is labeling issues. What do each of the labels mean and when do we use them? How do you share a link to a label in GitHub Markdown (e.g. hackathon An issue we'd like to visit during a hackathon event is from pasting https://github.com/nsidc/earthaccess/labels/hackathon)? When to use "close issue as not planned"? What is a discussion vs an issue and when should we migrate between them (e.g. discussions for feature requests, issues for bugs?)? etc.

[mfisher87]

Stumbled on a great example which uses mermaid to draw a triage flowchart!!

https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md#issue-triaging-workflow