Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a bug/triage checklist #3215

Open
seanmonstar opened this issue Apr 28, 2023 · 0 comments
Open

Create a bug/triage checklist #3215

seanmonstar opened this issue Apr 28, 2023 · 0 comments
Labels
A-meta Area: meta (the hyper project itself) B-rfc Blocked: More comments would be useful in determine next steps.

Comments

@seanmonstar
Copy link
Member

This is an action item of the COE on hyper's surprise CVE:

There is a triage guide for bug reports, which is a good thing. But that doesn’t mean everyone (me included!) always remembers all the steps. Checklists are famous in aviation and medicine for their effectiveness in saving lives. They can also help us make sure all issues are treated properly.

Making sure the checklist is complete would be part of the routine decided on in #3214.

If I just take the headlines from the triager's guide, they would be this:

  1. Acknowledge
  2. Ask for more info
  3. Categorize
  4. Adjust the title
  5. Mentor

I think there's a need to fill in a few more items for step 2, "Ask for more info".

There's also a question of how to make sure we complete the checklist for each bug report. One idea I had was to setup an autoresponder bot which includes the checklist in markdown checkbox form. Then the first comment would always have it, and triagers should have "edit" permissions which would be required to check them off.

@seanmonstar seanmonstar added B-rfc Blocked: More comments would be useful in determine next steps. A-meta Area: meta (the hyper project itself) labels Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: meta (the hyper project itself) B-rfc Blocked: More comments would be useful in determine next steps.
Projects
None yet
Development

No branches or pull requests

1 participant