MozillaSecurity / MozillaSecurity/WebCompatManager
Sort buckets with highest liklihood of containing a reproducable issue to the top
Open
Nobody has claimed this yet.
priority:p2
- Dominant language
- Python
- Stars
- 1
- Forks
- 5
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
Sorting of buckets according to more properties than just number of reports e.g. number of reports with some threshold of likely usefulness (e.g. based on comment length or similar)
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
The issue names no files, tests, or entry points. Start by locating the code that groups and sorts buckets, then determine how report usefulness should be measured and validated. Done means buckets are ordered using the agreed usefulness signal rather than report count alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100