Extra tracking labels for libs team
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- tooling
Research direction
Start by reviewing the current Libs-Tracked and Libs-Small labels described in issue #864, then compare the referenced lang and types-team labels. The issue is exploratory, so done means agreeing on a labels or tracking scheme rather than making a specified code change.
Written by the indexing model from the issue text.
Description
Right now, we have two additional labels for the libs team that are not used:
- Libs-Tracked
- Libs-Small
This is a general placeholder for discussing options for new labels/tracking schemes for libs issues to help keep things in mind.
A few notable things used by other teams that might be relevant:
- I-lang-radar marks items as "on lang's radar" but not explicitly nominated for discussion (similar to Libs-Tracked. Probably we would want to move Libs-Tracked to an I-prefixed label.)
- P-lang-drag-[0-4] changes the prioritisation scheme for lang specifically. We've mentioned wanting some ways to distinguish what priority means for the libs team; for example, something could be P-high for a tier-3 target and thus actually P-low.
- S-types-tracked and S-types-deferred are used by the types team to differentiate between actively-worked-on and nice-to-have features.
Gonna nominate this but suggest we put it later in the meeting to not waste time on it if we have more important things.
- Dominant language
- Rust
- Stars
- 178
- Forks
- 28
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 2
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.
More from rust-lang/libs-team
-
api-change-proposal T-libs
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
api-change-proposal
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
api-change-proposal I-libs-nominated
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
ACP: `panic_abort!` Openapi-change-proposal
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
api-change-proposal
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in rust-lang/libs-team
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100