Improve the componentspecific model to use information from the component model
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
The componentspecific model currently just takes as input the data from the bug and decides whether it should be moved out of Firefox:General or not.
A better approach would be to add the output of the component model as features (maybe the top-3 choices):
- top1 choice = Firefox::Component 1
- top1 score = 0.8
- top2 choice = Core::Component 2
- top2 score = 0.15
- top3 choice = Core::Component 7
- top3 score = 0.05
Then use the following as labels:
- keep in general
- use top1
- use top2
- use top3
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 locating the component model and componentspecific model training or feature-building entry points. Add the component model's top-three choices and scores as inputs, use the four listed outcomes as labels, and verify that the resulting model can distinguish keeping a bug in general from selecting each proposed component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100