Repository navigation
Issue Triage Role #370
Description
I was speaking with @joelanford, @ncdc and @oceanc80 and we got on the topic of Issue Triaging. The weekly meeting is called OLM WG and Issue Triage Meeting and we haven't done much issue triaging.
Our discussion focused on a few points:
- There is a general sentiment that in person issue triaging isn’t very effective
- We think that it would benefit the community if we embraced closing issues asynchronously.
- There is a concern that if “everyone is responsible for triaging issues asynchronously, no one will close issues asynchronously”.
The goal of this thread is to identify how we'd like to triage issues as a community and decide how this might impact our "OLM WG and Issue Triage Meeting"
Originally posted by @awgreene in #335 (comment)
Activity
joelanford commentedon Aug 30, 2023
To stretch an analogy, I get the impression (maybe I'm wrong!) that GH is not quite our town square yet, and that folks often come here to conduct some specific business, but then leave without going window shopping to see what else is going on.
I'm not sure what others do, but my setup is:
If there's some way to encourage everyone to hang out here more, be on the lookout for new issues and PRs landing in repos, and be proactive about responding to them, that would be an awesome outcome IMO.
I realize that might fall into the "everyone is accountable, so in fact no one is" problem. But maybe if we can overcome some inertia and get a critical mass of contributors drinking the Kool-Aid, the dominos will start to fall?
camilamacedo86 commentedon Mar 4, 2025
@joelanford @awgreene
This issue has had no interactions since
August 30, 2023So, I think we can close this for now. If a need arises in the future, we can always revisit and review it or reopen it as needed.
WDYT?
github-actions commentedon Jan 2, 2026
This issue has been closed due to inactivity.