Issues labelling conventions

[matteocargnelutti]

Let's experiment with tagging and see if it helps us keep track of how things are going 😄 .

We now have 5 different types of labels, only 1 of which is required to create an issue.
The idea is to help us query the issues tracker as such:

• "Show me all open bugs with a high priority"
• "Show me all the open bugs that should be quick to fix"
• "Show me all the features-related issues that are low priority"
• "Show me all the issues that we should consider closing"
• "Show me all the issues for which we think prioritization should be discussed"
• Etc ...

---

Available labels and how to use them

1. What type of task / issue is this?

This is the only type of label that is "required".
Find them quickly in the "Labels" drop down by typing "Issue type".

• bug
• feature
• enhancement
• housekeeping
• question

2. This issue is in relation to:

Optional.
Find them quickly in the "Labels" drop down by typing "Subcategory".

• accessibility
• database
• capture-challenge
• playback-challenge
• client-side-playback
• performance
• security
• tests
• website-content
• internet-archive
• memento
• warcprox
• webrecorder
• perma-capture
• devops
• user-interface
• api
• admin
• ui

3. Triage hints:

Optional.
Find them quickly in the "Labels" drop down by typing "Triage hint".

• duplicate
• likely-obsolete
• maybe-close

4. Effort hints:

Optional.
Find them quickly in the "Labels" drop down by typing "Effort hint".

• should-be-small
• needs-design
• policy-decision-needed
• missing-context
• wishlist

5. Priority hints:

Optional.
Find them quickly in the "Labels" drop down by typing "Priority hint".

• priority-tbd
• priority-low
• priority-mid
• priority-high

---

Complete list of our labels: https://github.com/harvard-lil/perma/labels