Triaging the large number of open issues.

[chrisdebian]

Hi, all.

Just looking at the large number of open issues in "cosmic-epoch", and I also realised that as well as cosmic-epoch, we also have separate component parts for the different desktop constituents.

I was wondering, should we have a way of labelling all issues, to help triage these and to help the devs focus on what's important to them. Not sure whether the devs use JIRA to manage the issues, but if we assign labels to all of the open issues, the GitHub Project functionality can automatically make a kanban board. I'm just trying to help.

The below looks like a lot, but in reality, it just adds the following to an issue:

✅ Example Label Combination

type:crash
moscow:must
component:cosmic-comp

Thanks,

Chris.

---

📌 Proposed Label Taxonomy for COSMIC Issues

This proposal introduces three orthogonal label groups to improve triage, prioritisation, and routing of issues across COSMIC and its component repositories.

Each issue should ideally have:

• 1 type: label (what kind of issue it is)
• 1 moscow: label (priority using MoSCoW)
• 1 component: label (which COSMIC component is affected)

---

🏷️ type: Labels (What kind of issue?)

🔧 Bugs & Stability

• type:bug — Something is broken or behaving incorrectly
• type:crash — Causes a crash, freeze, or unusable session
• type:regression — Worked previously, broken now
• type:performance — Slowness, stutter, high CPU/GPU/memory usage
• type:memory-leak — Memory usage increases over time

---

🖥️ UI / UX

• type:ui — Visual/layout issues (z-order, missing elements, overlap)
• type:ux — Confusing or unintuitive behaviour
• type:accessibility — Accessibility issues (keyboard nav, contrast, screen readers)

---

🧠 System & Core Behaviour

• type:session — Login, logout, suspend, resume, session lifecycle
• type:workspace — Workspaces, window movement, overview behaviour
• type:power — Power management, suspend, idle, battery behaviour

---

🖱️ Input & Devices

• type:input — Keyboard, mouse, touchpad
• type:keyboard-layout — Layout-specific shortcut/input problems
• type:touch — Touchscreen or tablet input
• type:gamepad — Controller / joystick input

---

🖥️ Graphics & Hardware

• type:display — Monitors, HDMI/DP, scaling, refresh rate
• type:graphics — GPU drivers, Wayland, Vulkan/OpenGL, llvmpipe fallback
• type:audio — Sound, microphones, media keys

---

📦 Apps & Ecosystem

• type:application-compatibility — Issues with third-party apps (Steam, Spotify, etc.)
• type:flatpak — Flatpak-specific issues
• type:xwayland — XWayland-specific issues
• type:tray — System tray / background apps

---

🧩 Triage & Maintenance

• type:more-info-needed — Missing logs, steps to reproduce, or system info
• type:cannot-reproduce — Unable to reproduce with provided information
• type:duplicate — Duplicate of an existing issue
• type:blocked — Blocked by upstream dependency (kernel, drivers, Wayland, etc.)

---

✨ Enhancements

• type:feature-request — New functionality request
• type:enhancement — Improvement to existing behaviour
• type:configuration — Settings/configuration related
• type:polish — Visual or interaction refinements

---

🧭 moscow: Labels (Priority)

MoSCoW prioritisation — exactly one should be applied per issue.

• moscow:must — Critical: crashes, freezes, data loss, core workflows broken
• moscow:should — High priority but with a workaround
• moscow:could — Nice-to-have improvements or minor issues
• moscow:wont — Out of scope, deferred, or explicitly not planned

---

🧩 component: Labels (Which COSMIC component?)

Based on the official Components of COSMIC Desktop list.

🔹 Core System

• component:cosmic-comp — Wayland compositor & window management
• component:cosmic-session — Session startup, lifecycle
• component:cosmic-settings-daemon — System settings backend
• component:cosmic-idle — Idle & power management
• component:cosmic-workspaces-epoch — Workspace handling
• component:xdg-desktop-portal-cosmic — XDG desktop portals

---

🔹 UI & Interaction

• component:cosmic-panel — Panel / status bar
• component:cosmic-applets — Panel applets (network, battery, etc.)
• component:cosmic-launcher — App launcher / search
• component:cosmic-notifications — Notifications system
• component:cosmic-osd — On-screen displays (volume, brightness)
• component:cosmic-greeter — Login screen
• component:cosmic-bg — Desktop background & wallpaper
• component:cosmic-randr — Display configuration
• component:cosmic-screenshot — Screenshot tooling

---

🔹 COSMIC Applications

• component:cosmic-files — File manager
• component:cosmic-edit — Text editor
• component:cosmic-player — Media player
• component:cosmic-store — App store
• component:cosmic-term — Terminal emulator
• component:cosmic-theme-editor — Theme editor

---

🔹 Triage Helpers

• component:not-yet-triaged — Component not yet identified
• component:multi-component — Affects multiple components
• component:unknown — Component unclear even after review

---

✅ Example Label Combination

type:crash
moscow:must
component:cosmic-comp

---

🎯 Benefits

• Clear routing of issues to the correct component
• Explicit prioritisation using MoSCoW
• Scales across COSMIC sub-repositories
• Works well with GitHub Projects & automation