Hey Manu, I don't explicitly use the labels, but they help me to categorize the issues mentally. I agree that there is room for improvement as there are more issues being raised every day.
Other communities also have interesting approaches, such as: - Triage label: When a new bug, improvement, proposal, or question is being raised it gets a triage label to make sure that someone from the community looks at it. Assesses the severity of the issue, assesses the effort, etc. After an initial follow-up, the triage label can be removed, this can be done by either a committer or someone who has contributor rights. - Full process: Arrow takes this to the next level and has a full process for it: https://github.com/apache/arrow/pulls. There are many different issues to indicate the process: awaiting review, awaiting committer review, awaiting changes, awaiting change review, and probably a few more. For me, this feels a bit too much. I think it might be good to add a triage label, and this might also be included in a report. You could also easily see the newest issues by filtering on this issue. WDYT? Kind regards, Fokko Op ma 27 mei 2024 om 18:03 schreef Manu Zhang <owenzhang1...@gmail.com>: > Hi all, > > Currently, a label, one of bug, improvement, proposal and question, is > applied automatically > to an issue if it's created from a template. However, I'm not sure we are > actually making use of those labels. We have questions without answers, > bugs without double checks and improvements without discussions. > > Do you think we can send a weekly report of those issues somewhere to get > more attention from the community? I remember @Jean-Baptiste Onofré > <j...@nanthrax.net> having a similar proposal before. > > Thanks, > Manu >
