grouping targets in the target list
Open
Nobody has claimed this yet.
A-frontend
E-easy
S-needs-design
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
I came across #2170 and the screenshot inspired me to ask if it makes sense to group the targets by platform tier
Contributor guide
No contributing guide indexed for this repository
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
Start by reading issue #2170 and reviewing the linked screenshot to understand the target list and the proposed platform-tier grouping. Identify the target-list entry point and decide with maintainers what grouping and completion criteria should be used; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100