Expand the traning dataset for the component_specific model
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
Yeah... Unfortunately we are not great when it comes to moving bugs in the right components out of Firefox::General...
Maybe we could pick a subset that we think should be really good, e.g. uplifted bugs. But I would do this as a follow-up because it needs to be evaluated (and maybe we want to use them for training but not for testing, which means we must wait for #4407).
Originally posted by @marco-c in https://github.com/mozilla/bugbug/pull/5892#discussion_r3016597808
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
Start by reviewing the discussion in PR #5892 and the dependency on issue #4407. Define which subset of bugs should expand the component_specific training dataset, and determine whether the selected bugs belong in training, testing, or both. Done means the subset and evaluation approach are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- machine-learning, python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100