pqrs-org/Karabiner-Elements

No documented issue triaging workflow

Open

#4292 opened on Oct 18, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (22,112 stars) (909 forks)batch import
enhancementhelp wantedneeds to be addressedstale

Description

A while back I volunteered to help triage the issue reports. It seems the total number of open issues has increased by 30% since last time. I figured the time contributors can spend on KE is used more effectively if we decide on a concrete strategy to deal with issues for KE, both the backlog and the new ones.

Given the influx of new issues all the time I hope @tekezo does not mind me pinging him directly for this one.

Contributor guide

Tech stack
None
Domain
documentationdeveloper experience
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the existing open issues to understand the backlog. Engage with maintainers (@tekezo) and other commenters to define criteria for labeling and prioritization. Propose a documented workflow that includes issue triage steps, response time expectations, and labels. This is discussed in issue #4292.