-
Notifications
You must be signed in to change notification settings - Fork 191
Contributor role: Issue Triager
We receive a number of site compatibility reports from webcompat.com and this role is to try to understand the underlying issues. Sometimes that might be a Gecko bug, a platform bug (Windows or Android specific, etc), or website bug (JS framework, buggy code, UA sniffing, something else).
Good places to start are:
Once we figure out what the issue is (or might be), we do a few things:
- Close the issue (sometimes because there's not enough info to proceed, or we can't reproduce)
- Close the issue as a dupe of another issue (search helps with this)
- Try to reproduce the bug. If you can reproduce it, add the "needsdiagnosis" label.
- Describe the issue in issue comments, and if we're ready for someone to do site outreach change the label from "needsdiagnosis" to "needscontact".
- Find the underlying bug in Bugzilla/Gecko and link them (we can explain how to do this).
Here are a few sample issues to give you an idea of the kind of work we do:
- https://github.com/webcompat/web-bugs/issues/1267
- https://github.com/webcompat/web-bugs/issues/2231
- https://github.com/webcompat/web-bugs/issues/1483
The secret to how this all works is webcompat.com is a frontend to GitHub issues:
https://github.com/webcompat/web-bugs/issues/
So you can ping people (like @hallvors or @miketaylr) in comments if you have questions. Or if you're more comfortable doing the triage work from GitHub's end of things, that's also great.
We have some simple instructions at https://webcompat.com/contributors, but those could probably be updated. Any suggestions or contributions to that would awesome. Code for that is here:
https://github.com/webcompat/webcompat.com/tree/master/webcompat/templates/contributors, or just filing an issue with questions/suggestions/etc. is also great.
We're in #webcompat on Mozilla's IRC network if you have any questions. You can also ask questions via our mailing list if that's better for you: