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

Add guidelines for issue triage #74

Open
djzager opened this issue Feb 1, 2024 · 0 comments
Open

Add guidelines for issue triage #74

djzager opened this issue Feb 1, 2024 · 0 comments
Assignees

Comments

@djzager
Copy link
Member

djzager commented Feb 1, 2024

konveyor/enhancements#160 talks about enforcing standards for what it means for an issue (and maybe later) a PR to be triaged. However, we don't currently have a document that details these so called standards.

Create an issue_triage.md that explains:

  1. Triaged issues will have a triage/accepted, kind/*, priority/* label. If they don't they will be marked with needs-(triage|kind|priority).
  2. If an issue is an issue suitable for new contributors, we should label it good first issue.
  3. ... maybe more.

This might be a good reference for ideas on what all might be included in the document...but we aren't really trying to mirror Kube. https://www.kubernetes.dev/docs/guide/issue-triage/#triage-related-tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant