MozillaSecurity / MozillaSecurity/WebCompatManager
Surface installed extensions when known, and consider using them for clustering
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 5
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
We collect some/all installed extensions with each report. We know that extensions can be the cause of compatibility issues. Therefore the dashboard should:
- Have some way to see installed extensions for each report
- Add extensions as additional data to the clustering
- Where a bucket has a high prevalence of a particular extension being installed, add that to the summary of the bucket along with the domain and the example of a typical report.
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 locating the code that collects installed extensions, renders report details in the dashboard, and performs clustering. Review how bucket summaries are generated and determine how extension prevalence should be displayed; done means extensions are visible per report, included in clustering, and high-prevalence extensions appear in bucket summaries alongside the domain and typical report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100