Bot enforcement of triage guidelines in Konveyor

[djzager]

Background

During the v0.3.0 milestone of the Konveyor project, we started making use of the Planning Board and milestones to track work being done in the release. One thing that was missing from this effort was triage and planning, not that it wasn't occurring, but it wasn't occurring in a standard way. This worked for us at the time because contributors had a general idea of the direction we were headed and the work to be done.

Problem

However, as we progress into v0.4.0 release cycle, our need to standardize on terms/process around issues that do/do not belong to the release will only increase. It is becoming less and less possible for a single person to know all that belongs in the release.

Solution

Leverage automation using GitHub Actions to enforce some standards for issues (and maybe PRs):

• Standardize how issues are to be labelled to communicate their having been triaged, their kind, and priority.
• Associate all issues and PRs to the same "Planning" project for tracking.

We will do this by creating a reusable workflow that will be configured to run whenever an issue (and maybe PRs) are opened, edited, closed, reopened, labeled, or unlabeled.

Labels

The basic idea is that in order for an issue to be considered triaged it must be labelled:

• triage/accepted
• kind/* -> ie. kind/bug or kind/documentation
• priority/*, for example priority/blocker or priority/important-longterm

Project

We expect that all issues (and maybe PRs) should be assigned to the "Planning" project. Use something like the add-to-project action to add issues to the Planning board.

Tasks

• Reconcile GitHub Issues Workflow release-tools#57

References

1. https://github.com/kubernetes/test-infra/blob/master/prow/plugins/require-matching-label/require-matching-label.go

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.