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

[Sherwin-14]

@mfisher87 Hey I am thinking of working on this one, any specific opinions on this one?

[mfisher87]

Awesome, thanks Sherwin! I would love a flowchart diagram. In answering the questions in the description of the issue, I think it would be OK to leave some questions partially answered. For example, there are some labels like hackathon, good first issue, help wanted, etc. that we're really confident we want people to use and will stay around for a long time. But there are other labels, like "python", that I could imagine being removed or renamed to e.g. "impact/code". We can skip the ones we're not sure about for now, and perhaps once the PR is open others will share their ideas.

[Sherwin-14]

@mfisher87 I had a doubt regarding the flowchart. Should I come up with a flowchart different than the one you linked above in the 2nd comment. If yes, how can I decide or how would I know which are the hierarchies and what things are going to be listed under it? I have little idea about this one

[mfisher87]

I think we can use their flowchart as a base. There are some places I would make things more "Friendly". E.g. instead of "Close and ask to follow template", I'd suggest "Change to draft and ask to follow template".

We currently don't have prioritization labels, so we could omit that part. Or maybe we should add the prioritization labels and start using them! What do you think?

If you're comfortable doing a first draft and opening a PR, that could help start some conversation with the community that will guide us towards a solution.

[Sherwin-14]

I think we can use their flowchart as a base. There are some places I would make things more "Friendly". E.g. instead of "Close and ask to follow template", I'd suggest "Change to draft and ask to follow template".

We currently don't have prioritization labels, so we could omit that part. Or maybe we should add the prioritization labels and start using them! What do you think?

If you're comfortable doing a first draft and opening a PR, that could help start some conversation with the community that will guide us towards a solution.

I am thinking of coming up with the first draft. Then we can discuss further on prioritization labels as well as the flowcharts.

[Sherwin-14]

@mfisher87 Hey Matt, I have been working on this one for a while now and I have run into some issues with mermaid, so should I make a PR with whatever I have done uptill now(barring the mermaid part) or should I complete the chart as well and then make the PR? Which option would you deem as plausible former or the latter one?

[mfisher87]

Feel free to open a PR in draft mode at any time if you'd like feedback or to enable other contributors to follow your progress! I'd appreciate if you'd include your work-in-progress mermaid code so we can take a look and see if we can help :)