Labeling System for Resource Aggregation

[j12y]

We currently have the default set of issues:

• bug
• documentation
• duplicate
• enhancement
• good first issue
• help wanted
• invalid
• question
• wontfix

For question we could just convert to a discussion.

For wontfix, duplicate, and invalid we could just close it without tracking why.

The good first issue makes sense but help wanted seems true of any unassigned issue.

Use of bug or enhancement makes sense for software, not as much standards or data. GitHub also added issue types (task, bug, feature) so would be redundant.

Doesn't feel like the defaults were entirely meeting the needs we have for filtering issues so propose editing them.

How about we change...

[j12y]

Resource Types

• personas
• events
• tools

[j12y]

Issue Scope

• project
• documentation
• schema
• decision

[j12y]

Does GitHub have a solution for filtering issues between those that are open versus those that are pending review of a PR?

Any common conventions?

• waiting-for-pr
• waiting-for-review
• review-required
• pending