Consider adding text asking the reporter to provide their about:support for all bugs created by reporters who dont have "editbug" access
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Intention : To reduce the manual burden of devs and triage folks by not requiring them to manually ask the reporter to provide about:support.
This can be done where the reporter DOES NOT have "editbugs" access - which IMHO is a good proxy for "reporter is new to b.m.o".
Potential risk: Reporter may think that Mozilla is pushing them to do work.
Counter point: It is fair to assume that a user advanced enough to file a bug on bmo would understand that without basic information from them, Firefox with its large/complex code and interaction with OS/Drivers/external software/customization needs some basic information to diagnose issues.
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
No files, tests, or entry points are named. Start by tracing how bugbot handles newly created bugs and how it determines whether a reporter has editbugs access. Done should include agreed wording and coverage for prompting eligible reporters while avoiding the prompt for reporters with that access.
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
- Mostly clear
- Newbie friendliness
- 35/100