Skip to content
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

Meta: Issue triage and labeling #2456

Open
mtbc opened this issue Jul 11, 2023 · 0 comments
Open

Meta: Issue triage and labeling #2456

mtbc opened this issue Jul 11, 2023 · 0 comments

Comments

@mtbc
Copy link

mtbc commented Jul 11, 2023

This issue captures community discussion on how we triage issues. This could focus simply on categorizing, making it easy for individuals to find what they might next do, or it could include more prioritization for team-directed selection of issues. GitHub labels could usefully assist triage but require answering: (a) How eagerly to create labels? (b) Who can label issues? Examples of possibly useful types of label include,

  • GitHub defaults: bug, enhancement, question, ...
  • generic from elsewhere: performance, security, testing, ...
  • by component: validator, tp, sdk, pbft, rest, cli, ...
  • by language/technology: js, python, rust, ...
  • stage of process: build, install, run, ...
  • priorities.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant