|
| 1 | +# NodeDB-Lab org-wide CORE label taxonomy. |
| 2 | +# Every repo syncs these four axes so issues filter identically across the org. |
| 3 | +# Repos add their own domain labels (e.g. nodedb's engine:* / area:*) on top. |
| 4 | +# |
| 5 | +# type:* what kind of issue it is |
| 6 | +# sev:* TECHNICAL impact — reporter proposes, triage confirms |
| 7 | +# priority:* urgency/scheduling — MAINTAINERS ONLY, set at triage |
| 8 | +# status:* lifecycle |
| 9 | + |
| 10 | +# ── type ── |
| 11 | +- name: "type:bug" |
| 12 | + color: "d73a4a" |
| 13 | + description: "A defect — broken, incorrect, or lost data" |
| 14 | +- name: "type:feature" |
| 15 | + color: "a2eeef" |
| 16 | + description: "New capability or behavior change" |
| 17 | +- name: "type:docs" |
| 18 | + color: "0075ca" |
| 19 | + description: "Documentation is wrong, missing, or misleading" |
| 20 | +- name: "type:question" |
| 21 | + color: "d876e3" |
| 22 | + description: "Needs clarification; may not be a defect" |
| 23 | +- name: "type:epic" |
| 24 | + color: "5319e7" |
| 25 | + description: "Tracking issue spanning multiple sub-issues" |
| 26 | +- name: "type:chore" |
| 27 | + color: "cfd3d7" |
| 28 | + description: "Build, CI, refactor, or maintenance" |
| 29 | + |
| 30 | +# ── severity (technical impact — reporter proposes, triage confirms) ── |
| 31 | +- name: "sev:1-critical" |
| 32 | + color: "b60205" |
| 33 | + description: "Data loss, corruption, security, or crash; no workaround" |
| 34 | +- name: "sev:2-high" |
| 35 | + color: "d93f0b" |
| 36 | + description: "Major functionality broken; no acceptable workaround" |
| 37 | +- name: "sev:3-medium" |
| 38 | + color: "fbca04" |
| 39 | + description: "Feature wrong, but operational and a workaround exists" |
| 40 | +- name: "sev:4-low" |
| 41 | + color: "0e8a16" |
| 42 | + description: "Minimal impact / cosmetic" |
| 43 | + |
| 44 | +# ── priority (MAINTAINERS ONLY — urgency, set at triage) ── |
| 45 | +- name: "priority:P0" |
| 46 | + color: "5319e7" |
| 47 | + description: "Drop everything — fix now" |
| 48 | +- name: "priority:P1" |
| 49 | + color: "5319e7" |
| 50 | + description: "Fix in the current milestone" |
| 51 | +- name: "priority:P2" |
| 52 | + color: "5319e7" |
| 53 | + description: "Scheduled, not urgent" |
| 54 | +- name: "priority:P3" |
| 55 | + color: "5319e7" |
| 56 | + description: "Backlog / someday" |
| 57 | + |
| 58 | +# ── status (lifecycle) ── |
| 59 | +- name: "status:needs-triage" |
| 60 | + color: "ededed" |
| 61 | + description: "Awaiting maintainer triage (severity + priority)" |
| 62 | +- name: "status:needs-repro" |
| 63 | + color: "e99695" |
| 64 | + description: "Cannot reproduce yet — more info needed" |
| 65 | +- name: "status:confirmed" |
| 66 | + color: "0e8a16" |
| 67 | + description: "Reproduced by a maintainer" |
| 68 | +- name: "status:in-progress" |
| 69 | + color: "3becf4" |
| 70 | + description: "Actively being worked on" |
| 71 | +- name: "status:blocked" |
| 72 | + color: "000000" |
| 73 | + description: "Waiting on another issue or decision" |
| 74 | +- name: "status:wontfix" |
| 75 | + color: "ffffff" |
| 76 | + description: "Working as intended or out of scope" |
| 77 | + |
| 78 | +# ── cross-cutting flags ── |
| 79 | +- name: "regression" |
| 80 | + color: "b60205" |
| 81 | + description: "Worked on an earlier build; broke since" |
| 82 | +- name: "good first issue" |
| 83 | + color: "7057ff" |
| 84 | + description: "Good for newcomers" |
| 85 | +- name: "help wanted" |
| 86 | + color: "008672" |
| 87 | + description: "Extra attention is needed" |
0 commit comments