Compatibility/Outreachy

Web Compatibility Outreachy

Thank you for your interest in Web Compatibility. To familiarize yourself with the project, follow the steps below.

Report a fake bug on the test site

This exercise will help you better understand how webcompat.com works and provide us with feedback from a first time user.

Prerequisites:

• A computer running Windows / OSX / Linux
• Firefox installed
• One of the following browsers installed:
  • Edge
  • Safari
  • Opera
  • Chrome

Steps:

Test in Firefox

• Open Firefox
• Navigate to https://miketaylr.com/misc/exercises/apple.html
• Notice the page reloading continuously
• Close Firefox

Test another browser

• Open another browser (not Firefox)
• Navigate to https://miketaylr.com/misc/exercises/apple.html
• Notice the page does not continuously reload
• Close this browser

There is a bug on this page which affects one browser (Firefox) but not others. This is a web compatibility issue.

• Open Firefox again
• Navigate to http://s:s@staging.webcompat.com/
  • On the staging (test) website, we require a username and password. Please note that this is not required on the production website.
  • Username is “s” without the quotes
  • Password is “s” without the quotes
• Click “Report Bug"
• Fill out the form for the site https://miketaylr.com/misc/exercises/apple.html
• Explain the issue you encountered
• Click “Report Anonymously” to finish the bug report
• If you have a Github account, you can file it again and click “Report via Github” to see that process as well

When you have completed, take a minute to document your thoughts on the experience.

• How would you describe the bug reporting process?
• Is there anything that wasn’t clear or missing?
• What challenges might other users, with varying levels of technical experience, face?
• After a bug report is filed someone has to triage it, which involves reproducing the issue on their own computer or mobile device.
  • How can we change the bug reporting process to ensure bug reports contain enough information to reproduce the issue being reported?

Review the current contribution documentation

There is quite a bit of documentation for new contributors to webcompat.com, but it is spread out in different locations. Read through some of the documentation to get familiar (it is not required that you read all of it):

• https://webcompat.com/about
• https://webcompat.com/contributors
• https://wiki.mozilla.org/Compatibility/Guide
• https://github.com/webcompat/webcompat.com/wiki/Contributor-role:-Issue-Triager
• https://github.com/webcompat/webcompat.com/wiki/Contributor-role:-Web-Opener
• https://github.com/webcompat/webcompat.com/blob/master/CONTRIBUTING.md (for webcompat.com development)

When you feel you understand the purpose of the web compatibility effort and the process we follow at webcompat.com, document some ideas that could make it easier for new contributors to get involved.

Reach out

Send all feedback you’ve documented from the steps above in an email to Adam Stevenson (astevenson@mozilla.com).

We don’t bite! :) You can say hi on IRC in the #webcompat channel on the Mozilla IRC network.

We’re also on twitter.

Lastly, if you feel comfortable you can start triaging some bugs.