Add doc on triaging

[d-buckner]

Description

This is to outline the triaging process, which will be helpful context as I'll be starting community triaging calls in the next week or so.

Changelog

• doc: add triaging process documentation

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Invalid Prefix

Invalid description prefix. Found "docs". Expected "breaking", "deprecate", "feat", "fix", "infra", "doc", "chore", "refactor", "security", "skip", or "test".

[zhongnansu]

Thanks for the contribution, this will be helpful for community to get involved. I wonder for most community member, who couldn't make it to the meetings, how can they be informed of the updates of issues? I've seen issues with "untriaged" label removed, and a [Catch triaged, 1, 2, 3] comment which I do not have a clue what it means. Any mechanism to keep tracking of the traiged issues, and keep open to the community? I've also seen issues that has been assigned to a maintainer but stale for months, wonder if you have any proposal for these? Thanks

[d-buckner]

@zhongnansu these are all really valid points. I don't have a proposal at this time, but if you're able to join I think this is exactly the type of conversation that would be valuable in our triaging call. Essentially the more feedback and discourse from other contributors the better we can improve the mechanisms.