Easy and interesting starting point to start with

Very very dangerous label ! Indicates that a MR should not be merged (Wrong Milestone, ...)

Denotes a disruption to IT services and the associated issues require immediate attention

Document how the algorithm works (internal and/or article publication)

Only for Debian OS (patches,...).

Only macos system

Works on Windows.

Tasks unfeasible, or not valid at current time.

Tasks ready to be shipped, or MR ready to be merged

Why a MR is not merged yet : Needs a specific feedback for a team members (should be tagged in MR)

Why a MR is not merged yet : author needs to reply to reviewers.

Why a MR is not merged yet : Needs specific hardware to be tested.

Why a MR is not merged yet : needs more work (more than small MR corrections)

Requires an expert to validate the current stage (especially for the design stage)

The issue or the merge-request brings a breaking change, that probably needs special attention.

Tasks in specifications and design phase.

Tasks needing review for the design phase.

Tasks being implemented.

Tasks waiting to be reviewed.

Tasks with specifications validated, waiting to go in code phase