Optimize color selection of labels used in repository
- 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...

typical color scheme in most repositories:

### 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:

=> 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
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