Is your feature request related to a problem? Please describe.
When reading through the github issues, it's clear that the Issues are a bit disorganized. This repository will clearly benefit from labeling issues for easier filtering. The problem will get worse as more people provide feedback. Starting a process of labeling issues now before feedback gets overwhelming is a big quality of life improvement!
Describe the solution you'd like
Most major projects have a system for labeling their issues for easier organization. Some examples I've seen in other projects: Bug, Duplicate, Feature Request, Invalid (not a bug), Enhancement, Question, wontfix, help wanted, and "good first issue" (issue that is useful for onboarding new contributors).
If all the devs are too busy to go through and apply labels, I might suggest assigning someone trusted (applying labels apparently requires write access to the repository) as a "collaborator" for the repository.
Is your feature request related to a problem? Please describe.
When reading through the github issues, it's clear that the Issues are a bit disorganized. This repository will clearly benefit from labeling issues for easier filtering. The problem will get worse as more people provide feedback. Starting a process of labeling issues now before feedback gets overwhelming is a big quality of life improvement!
Describe the solution you'd like
Most major projects have a system for labeling their issues for easier organization. Some examples I've seen in other projects: Bug, Duplicate, Feature Request, Invalid (not a bug), Enhancement, Question, wontfix, help wanted, and "good first issue" (issue that is useful for onboarding new contributors).
If all the devs are too busy to go through and apply labels, I might suggest assigning someone trusted (applying labels apparently requires write access to the repository) as a "collaborator" for the repository.