-
Notifications
You must be signed in to change notification settings - Fork 192
Contributor role: Web Opener
A Web Opener is someone who helps to find contact information for sites/frameworks/projects and to send them messages telling them about ways they can increase their compatibility with web browsers.
The bugs on webcompat.com follow these stages:
-
Issue filed
-
Triage: to understand if the bug is real, temporary, etc. Trying to reproduce it with the same or close to same configuration than the bug reporter. Defining if it's really a Webcompat issue. If yes, switching to needsdiagnosis
-
Diagnosis: We try to understand technically what the bug is about. Client/Server side. JS, CSS, HTTP, HTML, video? And probably explain how it could be fixed. Switching to needscontact.
-
Contacts Search: One of the hard tasks is to find the right contact. It can sometimes be a developer inside the company, sometimes the project manager, sometimes the client of a Web agency, etc. Switching to contactready. Check everything in https://webcompat.com/contributors#outreach it explains a lot. Ask for more details.
-
Contacting: Once the contact has been found, we can try to contact the person found. Be gentle is my main recommendation here. ^_^ Even if the site sucks, or the people on the other side are acting like they don't care, they have their own job constraints, their own bosses, their own bad hair day ;) Once the contact initiated, you can switch to sitewait.
-
Revisiting: Let it rest a bit. and after a couple of weeks/months. Try to contact again. If silence, let's switch the bug back to needscontact. And we go for another round of trying to find a new contact.
For the Web Opener,
4, 5 and 6 are super important. Basically:
- https://webcompat.com/issues?stage=needscontact
- https://webcompat.com/issues?stage=contactready
- https://webcompat.com/issues?stage=sitewait
Sitewait has plenty of backlog currently and it's good to clean that too. ^_^
With ❤️ from WebCompat team.