Standarize labels and issue templates so issues opened by external contributors are correctly labeled. This way kind/bugs can be easily found on the board on triage for example.
Acceptance criteria
For "user" facing repos (policy-server, kubewarden-controller, policies, kwctl..), not libraries and so,
-
When creating new issues from templates, some repositories add bug label, others add kind/bug, etc. Standardize labels between repositories. This may mean a PR to the terraform in kubewarden/automation repo.
-
Some repositories may be overwriting the issue templates hence not using the ones from this repo. If that is done, reevaluate if it is needed and if the templates do indeed ask for relevant info to the repository.
-
Consider reducing the fields and questions asked on bug templates, as sometimes they are too complex.
Standarize labels and issue templates so issues opened by external contributors are correctly labeled. This way
kind/bugs can be easily found on the board on triage for example.Acceptance criteria
For "user" facing repos (policy-server, kubewarden-controller, policies, kwctl..), not libraries and so,
When creating new issues from templates, some repositories add
buglabel, others addkind/bug, etc. Standardize labels between repositories. This may mean a PR to the terraform in kubewarden/automation repo.Some repositories may be overwriting the issue templates hence not using the ones from this repo. If that is done, reevaluate if it is needed and if the templates do indeed ask for relevant info to the repository.
Consider reducing the fields and questions asked on bug templates, as sometimes they are too complex.