You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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,
bug
,enhancement
,question
, ...performance
,security
,testing
, ...validator
,tp
,sdk
,pbft
,rest
,cli
, ...js
,python
,rust
, ...build
,install
,run
, ...The text was updated successfully, but these errors were encountered: