search

trinodb / trino

Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
https://trino.io
Apache License 2.0
10.18k stars 2.94k forks source link

Improve issues management #23121

Open mosabua opened 3 weeks ago

mosabua commented 3 weeks ago

The backlog of over 2.3k issues is unmaintainable. We need to clear this up and define a process for managing issues going forward.

Things to look at:

Akanksha-kedia commented 2 weeks ago

@mosabua We have enhance the template of issues, where sometimes issue is not finally an issues its suspected to be an issue so we can have some labels added while creating an issue so that its becomes easy to filter out.

mosabua commented 2 weeks ago

I saw some of these approaches already @Akanksha-kedia .. but you want to point out where you have done that?

hashhar commented 2 weeks ago

The idea of having a triage label applied automatically to all incoming issues is good.

It helps maintainers to see which issues need attention and then either closing it, moving discussion to Slack or confirming issue as a bug etc. can be done. Right now I have no idea if an issue was already looked at (or being looked at) by someone else or not.

It would only help with preparing the queue though - what happens after things get triaged is the harder part IMO.

mosabua commented 2 weeks ago

yeah .. we want to do more than just that though .. still need to flesh it out .. automatic messaging, and closing after some time like the PRs and so on.

lozbrown commented 1 week ago

Suggest using the power of Gen AI you help you out here, at my employer we've used Gen AI to help triage our issue management, flagging issues as related or dupes. Ensuring issues have enough information (and requesting missing) and because the application team have been flagged as SMEs its been able to respond to issues raised with accurate responses on the causes of issues because its seen similar issues raised in the past and closed after comments by the app team. We've had great success where users have closed the issues because the bot has successfully addresses the issues with comments.

a quick google find this https://dev.to/maurerkrisztian/building-an-innovative-ai-tool-to-revolutionize-github-issues-management-14bb

I get that the current situation is unmanageable, and getting out of that is a gargantuan task. But any cull of issues that are seen to be 'stale' risks leading to community feeling un-cared for and unaddressed.

In reality all github issues are either, not an issue, responses needed to make the user see that. OR are an issue, probably needs to be address or at least marked as not a priority, Anything you can get to help with that would be an improvement.