Write the label strategy section of the Contributor Guide

[binadamu-isiyoonekana]

Aim

This task aims at writing the section of the Contributor's bible which explains how GitHub actionnable items, such as, for instance, issues or pull requests (PRs) should be labelled.

As an output, a clear strategy for labelling must be created, with color-codes (such as red for critical items, like bug fixes or panic crashes, blue for devops-related items, and so on).

Assumption

• None

Acceptance criteria

• Define a matrix of labels, with clear organisation and color-codes.

Dependencies

• None

Risks

• No specific risks

References

• Sane GitHub Labels
• GitHub Labels that are logical, colorful and sensible
• GiHub labels guide
• About the label colors
• GitHub Issues: Tagging Best Practices - Save Time!