Maintainers

The Team

Issues and PRs are triaged daily and the process for triaging may be found under triaging issues in our contributors guide repository.

The process for reviewing PRs may be found under review guidelines in our contributors guide repository.

A maintainer that looks at an issue/PR must define its kind/*, area/*, and status/*.

The status/* labels represent the desired state in the workflow.

status/0-needs-triage: all the new issues and PRs have this status. [bot only]
status/1-needs-design-review: needs a design review. (only for PR)
status/2-needs-review: needs a code/documentation review. (only for PR)
status/3-needs-merge: ready to merge. (only for PR)
status/4-merge-in-progress: merge is in progress. [bot only]

contributor/need-more-information: we need more information from the contributor in order to analyze a problem.
contributor/waiting-for-feedback: we need the contributor to give us feedback.
contributor/waiting-for-corrections: we need the contributor to take actions in order to move forward with a PR. (only for PR) [bot, humans]
contributor/needs-resolve-conflicts: use it only when there is some conflicts (and an automatic rebase is not possible). (only for PR) [bot, humans]

kind/enhancement: a new or improved feature.
kind/question: a question. (only for issue)
kind/proposal: a proposal that needs to be discussed.
- Proposal issues are design proposals
- Proposal PRs are technical prototypes that need to be refined with multiple contributors.
kind/bug/possible: a possible bug that needs analysis before it is confirmed or fixed. (only for issues)
kind/bug/confirmed: a confirmed bug (reproducible). (only for issues)
kind/bug/fix: a bug fix. (only for PR)

resolution/duplicate: a duplicate issue/PR.
resolution/declined: declined (Rule #1 of open-source: no is temporary, yes is forever).
WIP: Work In Progress. (only for PR)

Automatically set by a bot.