Suggestion: Improve issue labeling
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
## Summary
There's some places where the issue tracker could be improved.
## 💬 Description
To make it easier to interact with the ic-ui-kit repo and its issue tracker, I suggest the following issue-labels:
- Good first contribution
- Issue difficulty (low, medium, high)
- Scoped labels (react, nextjs, web-components etc)
- Docs
- Tests
- Internal
## 💰 Use value
It's easier for contributors to figure out where to contribute if this is in place.
## 📝 Acceptance Criteria
*Given* the issue tracker
*When* using the tracker
*Then* it should be easy to know what kind of work is intended
## ✏ Designs
N/A
## 🧾 Guidance
N/A
## Additional info
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the ic-ui-kit issue tracker and the proposed labels in issue #2736, including contribution, difficulty, scope, Docs, Tests, and Internal categories. Define the label set so contributors can identify the intended kind of work from the tracker; done means the tracker communicates this clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100