Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
suggestion: use Triage-Party for engaging community for github issues #39412
I have an issue with golang tool test2josn that I asked for help but I didn't get any response and quite undrestandably I noticed the golang repo has more than 5000+ issues and it is a bit hard to answer to every issue and problem,
and I wish I (and the community) could help in triage golang issues.
in minikube, we use Triage Party and it helps with the triage so that community and users also participate in labeling and triage the incoming issues
here is the public minikube triage to see it in action: https://teaparty-tts3vkcpgq-uc.a.run.app/s/daily-triage
I don't think we have much of a "triaging issues" problem, the real problem is simply that more issues are opened every day than the people working on the project can fix.
"Triaging" means giving the issue a first (more or less quick/superficial) look, in order to understand if the issue is valid, label it accordingly, and assess its severity ("is this something that would be nice to fix someday, or it's a problem that requires immediate attention from the runtime team?" etc...). That gamification tool seems to address this, but I think we are already doing it.
The problem in your case is that you commented on an old thread and nobody had an answer for you (it would have been better to open a new one). It is a problem, and I agree it was a suboptimal experience. Just I don't think it's a "issues triaging" problem. We have ~6000 threads that are open and potentially active, and it seems inevitable that sometimes there's no activity on some of them even when someone adds a new comment/asks a question. I'm not sure gamifying can help with this, though.
Hey @medyagh. I think this is a good suggestion, but I don't think it will get visibility in our issue tracker, which focuses on the language itself, the core library, and x/ repos. I'd suggest starting a discussion on a mailing list.
We tend to triage issues on the GitHub issue tracker to package owners. It's not clear that this would get appropriate feedback, whereas golang-dev or golang-nuts will reach a broader audience.
I also agree with @ALTree. It's not clear to me how triage party would help your particular issue.
I think the feedback you left on #33419 was perfect: you left a clear, well-explained response explaining how the issue is still a problem. The issue seems to have the appropriate people cc'd, and I assure you that we read those (many!) emails.
There is nothing stopping the community from participating in the triage process right now. You are most welcome to cc package owners, set labels, follow up on old issues.
Take a look at: https://github.com/golang/go/wiki/gopherbot for how to attach labels.