apache / apache/pulsar

Optimize color selection of labels used in repository

Open
#21,883 6 comments 1 reaction 0 assignees View on GitHub
type/enhancement
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Motivation

Today's color selection for labels in Pulsar's repository is not this intuitive to give a good overview.
The main reasons:
- very different types use similar or near similar colors, e.g. `type/bug` and `type/enhancement`
- color section does not follow the typical/most used color theme, e.g. `type/bug` is in most repositories red background and white font color

in this repository it looks like this and people already ad a prefix like `[Bug]` to the title to have a better orientation...
![2024-01-11_15h07_52](https://github.com/apache/pulsar/assets/5681880/845d4fc0-c6df-4235-a213-26aa3d9002f5)

typical color scheme in most repositories:
![2024-01-11_15h08_51](https://github.com/apache/pulsar/assets/5681880/00af0081-3e5f-467d-b633-983dfbe9bffe)

### Solution

a good write up with some good ideas/principles for label design:
https://seantrane.com/posts/logical-colorful-github-labels-18230/

following this, it may look like this way:
![2024-01-11_15h11_05](https://github.com/apache/pulsar/assets/5681880/c23b1e7f-046e-42b5-8efc-65754e93cb31)

=> as a first quickfix on could at least recolor some of the negatively important ones to
red background and white font color
- `type/bug`
- `release/blocker`
- `component/security`

### Alternatives

_No response_

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Review the repository's current GitHub labels and compare their colors with the proposed scheme and linked label-design guidance. Update the specified labels, including type/bug, release/blocker, and component/security, so their meanings are visually distinct and negative-impact labels use the suggested red treatment.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
developer-experience
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.