Label Taxonomy

[McCodeman]

As a project manager, maintainer, or contributor, I would like to quickly analyze existing issues and PRs by applying label filters to understand what work needs to be triaged, assigned, completed, etc. and to help me manage the backlog.

The goal is not to create every label we think we may need as this list can evolve.

Review and update label taxonomy to enable visibility of:

• [ ] clear priority of backlog
• [ ] triage needed on issues (more information, duplicate, etc.)
• [ ] type of issue (feature request, documentation, proposal, bug, security, etc.)
• [ ] area/ownership
• [ ] support of automated processes (requires-cla, cla-not-needed, test failure, etc.)
• [ ] contributor support (good-first-issue, need-help, etc.)
• [ ] issue lifecyle (active, frozen, rotten, stale) so we can auto close (or prevent close of) issues that have no activity - backlog maintenance

Acceptance Criteria

• [ ] Asciidoc documenting list of labels
• [ ] Labels created in GitHub
• [ ] Description of each label
• [ ] Who can assign each label (person or automated process)
• [ ] Which labels are requirements for the submission of a new issue (this can also be handled in a initial issue triage step).
• [ ] Document process for requesting and adding new labels.