MozillaWiki - User contributions [en]

Compatibility/Mobile/GeckoImprovements

2014-06-11T20:23:09Z

Adam s: /* Gecko Improvements from Mobile Web Compat Effort */

=Gecko Improvements from Mobile Web Compat Effort=

This list includes bugs that were first found through web compat analysis, and bugs that were already known but got a higher priority when we found breakage on production sites.

==Audio/Video==
* {{Bug|780379}} - Firefox mobile cannot open .m3u8 file (broken file?)
* {{Bug|881072}} - Flash Video (VideoJS Player) doesn't play on vine.co
* {{Bug|887517}} - Android: Audio's canPlayType() fails for MP3 if codec is supplied
* {{Bug|938772}} - empty <video> tag attempts to load href of <base> tag (prioritised)
* {{Bug|941351}} - Handle VIDEO element with M3U8 source

== Graphics, Panning and Zooming ==
* {{Bug|935615}} - Apple.com homepage is super zoomed in
* {{Bug|976616}} - Support dynamic viewport changes (Firefox for Android)
* {{Bug|976618}} - Support dynamic viewport changes (Firefox OS)

==Password==
* {{Bug|1023974}} - Banking site causes numerous "Remember Password" doorhangers
==Keyboard==
* {{Bug|918863}} [B2G][Browser][Youtube]Search does not execute after pressing enter
==Scrolling==
* {{Bug|911574}} - (yahoo) Can not scroll on Yahoo Fantasy Sports Football
==Network/Loading==
* {{Bug|881487}} - document.write causes updates to location.hash to refresh the entire page (prioritised)
==Layout==
* {{Bug|928074}} a element with display: table-cell children does not expand to the width of parent li element
[[Category:Web Compatibility]]

Compatibility/Contribute

2014-05-29T18:16:24Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
The mobile web is broken and you can help to make it better! With the accelerated growth of technology we should be able access the web from anywhere, but that’s not always the case. We need your help to advocate for a compatible web both globally and locally, together we can make the web work for everyone.

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners.
**'''Skills required:''' Passion for a free and open web.
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, only takes two minutes.
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add-ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication.
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. We need your help to determine the most popular sites in your region. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:''' Become a leader in your region and get others involved!
**'''Skills required:''' Passion for the open web, good communication skills.
**'''Description:''' Web Compatibility is a global effort that needs help in all regions. It’s your insight to local culture that gives you the chance to start a community of web compatibility advocates and contributors.
**'''Get started:''' Check [https://wiki.mozilla.org/Compatibility/Mobile#Volunteers_Leading_Web_Compatibility_efforts what activities] are going on in your region and create a new locale if it doesn’t exist. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Compatibility Guide] and become an ambassador for the project!

== Translation ==
Communication is key to any project but even more so for a global one. Websites are made by many developers in many languages, we need to be able to communicate with all of them. You can help make others understand the importance of a compatible web by helping with translations!

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
We want users and developers to have great experiences with the web compatibility effort. We need great UX and design specialists to help make that happen. Join us to help make the web more open!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
Do you love writing code? So do we! Part of web compatibility is providing tools that help perform automated testing, report/track bugs and help make the overall experience better. If this sounds like fun to you, join us and help make the web more open.

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
Bugs, they're everywhere! Web compatibility is all about finding bugs on websites and figuring out what's causing the issue. If you're an experienced developer who loves digging into code or you're just starting to learn, there ways that you can help out. You can make a difference to make the web more open!

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use our screenshot comparing application, install an automated testing program or manually test.
**'''Skills required:''' A keen eye for spotting visual differences in websites.
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-29T17:56:03Z

Adam s: /* Writing code */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
The mobile web is broken and you can help to make it better! With the accelerated growth of technology we should be able access the web from anywhere, but that’s not always the case. We need your help to advocate for a compatible web both globally and locally, together we can make the web work for everyone.

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners.
**'''Skills required:''' Passion for a free and open web.
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, only takes two minutes.
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add-ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication.
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. We need your help to determine the most popular sites in your region. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:''' Become a leader in your region and get others involved!
**'''Skills required:''' Passion for the open web, good communication skills.
**'''Description:''' Web Compatibility is a global effort that needs help in all regions. It’s your insight to local culture that gives you the chance to start a community of web compatibility advocates and contributors.
**'''Get started:''' Check [https://wiki.mozilla.org/Compatibility/Mobile#Volunteers_Leading_Web_Compatibility_efforts what activities] are going on in your region and create a new locale if it doesn’t exist. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Compatibility Guide] and become an ambassador for the project!

== Translation ==
Communication is key to any project but even more so for a global one. Websites are made by many developers in many languages, we need to be able to communicate with all of them. You can help make others understand the importance of a compatible web by helping with translations!

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
We want users and developers to have great experiences with the web compatibility effort. We need great UX and design specialists to help make that happen. Join us to help make the web more open!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
Do you love writing code? So do we! Part of web compatibility is providing tools that help perform automated testing, report/track bugs and help make the overall experience better. If this sounds like fun to you, join us and help make the web more open.

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
(Intro goes here)

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-29T17:41:07Z

Adam s: /* User experience and design */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
The mobile web is broken and you can help to make it better! With the accelerated growth of technology we should be able access the web from anywhere, but that’s not always the case. We need your help to advocate for a compatible web both globally and locally, together we can make the web work for everyone.

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners.
**'''Skills required:''' Passion for a free and open web.
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, only takes two minutes.
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add-ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication.
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. We need your help to determine the most popular sites in your region. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:''' Become a leader in your region and get others involved!
**'''Skills required:''' Passion for the open web, good communication skills.
**'''Description:''' Web Compatibility is a global effort that needs help in all regions. It’s your insight to local culture that gives you the chance to start a community of web compatibility advocates and contributors.
**'''Get started:''' Check [https://wiki.mozilla.org/Compatibility/Mobile#Volunteers_Leading_Web_Compatibility_efforts what activities] are going on in your region and create a new locale if it doesn’t exist. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Compatibility Guide] and become an ambassador for the project!

== Translation ==
Communication is key to any project but even more so for a global one. Websites are made by many developers in many languages, we need to be able to communicate with all of them. You can help make others understand the importance of a compatible web by helping with translations!

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
We want users and developers to have great experiences with the web compatibility effort. We need great UX and design specialists to help make that happen. Join us to help make the web more open!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
(Intro goes here)

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
(Intro goes here)

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-28T05:59:14Z

Adam s: /* Translation */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
The mobile web is broken and you can help to make it better! With the accelerated growth of technology we should be able access the web from anywhere, but that’s not always the case. We need your help to advocate for a compatible web both globally and locally, together we can make the web work for everyone.

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners.
**'''Skills required:''' Passion for a free and open web.
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, only takes two minutes.
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add-ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication.
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. We need your help to determine the most popular sites in your region. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:''' Become a leader in your region and get others involved!
**'''Skills required:''' Passion for the open web, good communication skills.
**'''Description:''' Web Compatibility is a global effort that needs help in all regions. It’s your insight to local culture that gives you the chance to start a community of web compatibility advocates and contributors.
**'''Get started:''' Check [https://wiki.mozilla.org/Compatibility/Mobile#Volunteers_Leading_Web_Compatibility_efforts what activities] are going on in your region and create a new locale if it doesn’t exist. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Compatibility Guide] and become an ambassador for the project!

== Translation ==
Communication is key to any project but even more so for a global one. Websites are made by many developers in many languages, we need to be able to communicate with all of them. You can help make others understand the importance of a compatible web by helping with translations!

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
(Intro goes here)

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
(Intro goes here)

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
(Intro goes here)

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-28T05:51:30Z

Adam s: /* Advocacy and Regional */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
The mobile web is broken and you can help to make it better! With the accelerated growth of technology we should be able access the web from anywhere, but that’s not always the case. We need your help to advocate for a compatible web both globally and locally, together we can make the web work for everyone.

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners.
**'''Skills required:''' Passion for a free and open web.
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, only takes two minutes.
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add-ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication.
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. We need your help to determine the most popular sites in your region. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:''' Become a leader in your region and get others involved!
**'''Skills required:''' Passion for the open web, good communication skills.
**'''Description:''' Web Compatibility is a global effort that needs help in all regions. It’s your insight to local culture that gives you the chance to start a community of web compatibility advocates and contributors.
**'''Get started:''' Check [https://wiki.mozilla.org/Compatibility/Mobile#Volunteers_Leading_Web_Compatibility_efforts what activities] are going on in your region and create a new locale if it doesn’t exist. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Compatibility Guide] and become an ambassador for the project!

== Translation ==
(Intro goes here)

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
(Intro goes here)

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
(Intro goes here)

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
(Intro goes here)

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-28T04:39:17Z

Adam s: /* Advocacy and Regional */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
(Intro goes here)

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners.
**'''Skills required:''' Passion for a free and open web.
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, only takes two minutes.
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add-ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication.
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. We need your help to determine the most popular sites in your region. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:''' Become a leader in your region and get others involved!
**'''Skills required:''' Passion for the open web, good communication skills.
**'''Description:''' Web Compatibility is a global effort that needs help in all regions. It’s your insight to local culture that gives you the chance to start a community of web compatibility advocates and contributors.
**'''Get started:''' Check [https://wiki.mozilla.org/Compatibility/Mobile#Volunteers_Leading_Web_Compatibility_efforts what activities] are going on in your region and create a new locale if it doesn’t exist. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Compatibility Guide] and become an ambassador for the project!

== Translation ==
(Intro goes here)

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
(Intro goes here)

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
(Intro goes here)

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
(Intro goes here)

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-28T04:20:05Z

Adam s:

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
(Intro goes here)

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:'''
**'''Skills required:'''
**'''Description:'''
**'''Get started:'''

== Translation ==
(Intro goes here)

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

== User experience and design ==
(Intro goes here)

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Writing code ==
(Intro goes here)

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Testing and Technical analysis ==
(Intro goes here)

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

Compatibility/Contribute

2014-05-28T04:15:51Z

Adam s: /* Writing code */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
(Intro goes here)

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:'''
**'''Skills required:'''
**'''Description:'''
**'''Get started:'''

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code ==
(Intro goes here)

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Translation ==
(Intro goes here)

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

Compatibility/Contribute

2014-05-28T04:15:29Z

Adam s: /* Writing code*/

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
(Intro goes here)

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:'''
**'''Skills required:'''
**'''Description:'''
**'''Get started:'''

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

== Translation ==
(Intro goes here)

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

Compatibility/Contribute

2014-05-28T04:14:00Z

Adam s: /* Translation */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
(Intro goes here)

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:'''
**'''Skills required:'''
**'''Description:'''
**'''Get started:'''

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Translation ==
(Intro goes here)

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

Compatibility/Contribute

2014-05-28T04:11:39Z

Adam s: /* Advocacy and Regional */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Advocacy and Regional ==
(Intro goes here)

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!]
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites

*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Regional Ambassador'''
**'''How you can help:'''
**'''Skills required:'''
**'''Description:'''
**'''Get started:'''

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute/SitesTools

2014-05-16T17:06:10Z

Adam s: /* Web Compatibility Sites & Tools */

== Web Compatibility Sites & Tools ==
Below is a list of websites and tools that are used in Web Compatibility. These are all hosted on Github with open issues that you can help with!

* Simplebug - [http://webcompat.com/simplebug/#mozilla/ site] | [https://github.com/webcompat/simplebug/issues issues]
** Tool that helps with site contacting by writing Bugzilla bug reports into non-technical language.
* Are We Compatible Yet? - [http://arewecompatibleyet.com/ site] | [https://github.com/hallvors/mobilewebcompat/issues issues]
** Lists of top sites by region with compatibility bugs, fast bug search, regression test results.
* Webcompat.com - [http://www.webcompat.com site] | [https://github.com/webcompat/webcompat.com/issues issues]
** A place for all web users, developers and browser vendors to get involved in the web compatibility effort. The goal is to make it easy to report and view problems for any part of the web
* Webcompat.com Browser Extensions - [https://github.com/webcompat/webcompat-reporter-extensions site] | [https://github.com/webcompat/webcompat-reporter-extensions/issues issues]
** Tool that makes reporting compatibility problems simple. Adds an icon to your browser to quick report any site issue while browsing.
* Bugs Ahoy! - [http://webcompat.com/bugsahoy/ site] | [https://github.com/webcompat/bugsahoy/issues issues]
** Tool that provides a simple interface to find web compatibility bugs to work on.

Compatibility/Contribute

2014-05-16T16:52:53Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility issues. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-16T16:52:02Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility bugs which need to be analyzed. These bugs are an easy introduction to analyzing compatibility bugs. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-16T16:51:22Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this *screenshot vid*

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:'''
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section
*** Create a Bugzilla account
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.
*** There are also older desktop compatibility which need to be analyzed. These bugs are an easy introduction to analyzing compatibility bugs. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-16T16:31:51Z

Adam s: /* Regional and language */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web research and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' [[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section, create a Bugzilla account and use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Mobile/Russia

2014-05-16T01:16:33Z

Adam s:

You are speaking Russian? You care about the open Web? This is a list of Web sites we need:

# Analyze the bugs when not already done
# Find the contact information
# Contact the Web site for negotiating a solution

Check the [[Compatibility/Guide|Guide]] and use the [[Compatibility/StdLetters#Russian|Russian template letter]] if you do not know how what to say exactly

We are currently collecting the list of [https://etherpad.mozilla.org/top-russian-sites top 100 Russian Web sites].

<bugzilla>
{"quicksearch": "status:new,assigned,reopened,unconfirmed",
"product": "Tech Evangelism",
"component": "Mobile",
"status_whiteboard": "[country-ru]",
"status_whiteboard_type":"allwordssubstr"}
</bugzilla>

== Some context ==

[[Category:Mobile]]
[[Category:Web Compatibility]]

Compatibility/Desktop

2014-05-14T04:43:02Z

Adam s: /* Sorting Desktop Bugs */

=Desktop Web Compatibility=

==What Are Web Compatibility Issues?==
'''A person should be able to use the Web with whichever browser they choose.'''

Unfortunately, some developers by choice or negligence will make their Web sites unusable by specific devices or browsers. We need to open up the Web to any rendering engines (Blink, Gecko, Trident, etc.) and/or browsers.

==Background==
Desktop web compatibility has a '''long history''' at Mozilla. Many of the compatibility issues from the past have been resolved thanks to the efforts of Mozilla volunteers, staff and web developers adopting web standards. This doesn't mean there aren't problems in the current state. A small percentage of ghosts of issues past do still linger on the web. Also with the high adoption of Webkit, some developers are choosing to use non-standard code without a Gecko equivalent or not test their sites with other browsers. Some of the same issues are happening for Microsoft's Trident engine.

==Goal==

Unlike [[Compatibility/Mobile|Mobile Web Compatibility]] desktop has no dedicated Mozilla resources allocated and is mostly driven by volunteers at the moment. The vague goal for this project is to continue to pursue equal opportunity for all desktop browsers and maintain the standards based environment we enjoy ''' for the most part''' today.

===Scope===

;In scope
* Any site that serves a desktop optimized version
* Any locale

;Out of scope
* Site enhancements
* Trivial site layout or functional bugs

== Get Involved ==

You can help '''keep the web open''' on desktop by:

*Reporting Web sites issues
*Analyzing Web sites issues
*Contacting Web sites for solving the issues

Get started here: [https://bugzilla.mozilla.org/buglist.cgi?f1=component&list_id=8384365&o1=notequals&resolution=---&query_format=advanced&v1=Mobile&product=Tech%20Evangelism List of Desktop Web Compatibility issues]

==Sorting Desktop Bugs==

In previous years there were large volumes of web compatibility bugs for Desktop and with it became [https://bugzilla.mozilla.org/describecomponents.cgi?product=Tech%20Evangelism more categories] in Bugzilla to organize them. There are currently many language components that these bugs are sorted to, the largest being "[https://bugzilla.mozilla.org/buglist.cgi?component=English%20US&product=Tech%20Evangelism&query_format=advanced&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0&list_id=10190566 English US]". In order to make it easier to monitor and maintain, all desktop bugs that are still valid are being moved to the [https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Desktop&resolution=---&list_id=10190589 Desktop component] in Bugzilla.

"[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Mobile&resolution=--- Mobile]" and "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Preinstalled%20B2G%20Apps&resolution=--- Preinstalled B2G Apps]" are two other active areas of Tech Evangelism. They do not belong to the Desktop Component except if they were miss-categorized.

==Old Tech Evangelism Bugs==

There are some desktop bugs in Bugzilla that are very old, some dating back to the early 2000's. These bugs should be treated the same as any bug today. If the issue still exists, move the bug to the Desktop component and leave a comment.

There is also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ video walk through] that explains how to assess these bugs.

Compatibility/Desktop

2014-05-14T04:33:52Z

Adam s: /* Sorting Desktop Bugs */

=Desktop Web Compatibility=

==What Are Web Compatibility Issues?==
'''A person should be able to use the Web with whichever browser they choose.'''

Unfortunately, some developers by choice or negligence will make their Web sites unusable by specific devices or browsers. We need to open up the Web to any rendering engines (Blink, Gecko, Trident, etc.) and/or browsers.

==Background==
Desktop web compatibility has a '''long history''' at Mozilla. Many of the compatibility issues from the past have been resolved thanks to the efforts of Mozilla volunteers, staff and web developers adopting web standards. This doesn't mean there aren't problems in the current state. A small percentage of ghosts of issues past do still linger on the web. Also with the high adoption of Webkit, some developers are choosing to use non-standard code without a Gecko equivalent or not test their sites with other browsers. Some of the same issues are happening for Microsoft's Trident engine.

==Goal==

Unlike [[Compatibility/Mobile|Mobile Web Compatibility]] desktop has no dedicated Mozilla resources allocated and is mostly driven by volunteers at the moment. The vague goal for this project is to continue to pursue equal opportunity for all desktop browsers and maintain the standards based environment we enjoy ''' for the most part''' today.

===Scope===

;In scope
* Any site that serves a desktop optimized version
* Any locale

;Out of scope
* Site enhancements
* Trivial site layout or functional bugs

== Get Involved ==

You can help '''keep the web open''' on desktop by:

*Reporting Web sites issues
*Analyzing Web sites issues
*Contacting Web sites for solving the issues

Get started here: [https://bugzilla.mozilla.org/buglist.cgi?f1=component&list_id=8384365&o1=notequals&resolution=---&query_format=advanced&v1=Mobile&product=Tech%20Evangelism List of Desktop Web Compatibility issues]

==Sorting Desktop Bugs==

In previous years there were large volumes of web compatibility bugs for Desktop and with it became [https://bugzilla.mozilla.org/describecomponents.cgi?product=Tech%20Evangelism more categories] in Bugzilla to organize them. There are currently many language components that these bugs are sorted to, the largest being "[https://bugzilla.mozilla.org/buglist.cgi?component=English%20US&product=Tech%20Evangelism&query_format=advanced&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0&list_id=10190566 English US]". In order to make it easier to monitor and maintain, all desktop bugs that are still valid are being moved to the [https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Desktop&resolution=---&list_id=10190589 Desktop component] in Bugzilla.

Two other areas in Tech Evangelism on Bugzilla to be aware of are "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Mobile&resolution=--- Mobile]" and "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Preinstalled%20B2G%20Apps&resolution=--- Preinstalled B2G Apps]". These bugs do not belong to Desktop Tech Evangelism.

==Old Tech Evangelism Bugs==

There are some desktop bugs in Bugzilla that are very old, some dating back to the early 2000's. These bugs should be treated the same as any bug today. If the issue still exists, move the bug to the Desktop component and leave a comment.

There is also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ video walk through] that explains how to assess these bugs.

Compatibility/Contribute

2014-05-14T00:26:23Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it.
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' [[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section, create a Bugzilla account and use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Desktop

2014-05-13T23:46:23Z

Adam s: Created page with "=Desktop Web Compatibility= ==What Are Web Compatibility Issues?== '''A person should be able to use the Web with whichever browser they choose.''' Unfortunately, some deve..."

=Desktop Web Compatibility=

==What Are Web Compatibility Issues?==
'''A person should be able to use the Web with whichever browser they choose.'''

Unfortunately, some developers by choice or negligence will make their Web sites unusable by specific devices or browsers. We need to open up the Web to any rendering engines (Blink, Gecko, Trident, etc.) and/or browsers.

==Background==
Desktop web compatibility has a '''long history''' at Mozilla. Many of the compatibility issues from the past have been resolved thanks to the efforts of Mozilla volunteers, staff and web developers adopting web standards. This doesn't mean there aren't problems in the current state. A small percentage of ghosts of issues past do still linger on the web. Also with the high adoption of Webkit, some developers are choosing to use non-standard code without a Gecko equivalent or not test their sites with other browsers. Some of the same issues are happening for Microsoft's Trident engine.

==Goal==

Unlike [[Compatibility/Mobile|Mobile Web Compatibility]] desktop has no dedicated Mozilla resources allocated and is mostly driven by volunteers at the moment. The vague goal for this project is to continue to pursue equal opportunity for all desktop browsers and maintain the standards based environment we enjoy ''' for the most part''' today.

===Scope===

;In scope
* Any site that serves a desktop optimized version
* Any locale

;Out of scope
* Site enhancements
* Trivial site layout or functional bugs

== Get Involved ==

You can help '''keep the web open''' on desktop by:

*Reporting Web sites issues
*Analyzing Web sites issues
*Contacting Web sites for solving the issues

Get started here: [https://bugzilla.mozilla.org/buglist.cgi?f1=component&list_id=8384365&o1=notequals&resolution=---&query_format=advanced&v1=Mobile&product=Tech%20Evangelism List of Desktop Web Compatibility issues]

==Sorting Desktop Bugs==

In previous years there were large volumes of web compatibility bugs for Desktop and with it became [https://bugzilla.mozilla.org/describecomponents.cgi?product=Tech%20Evangelism more categories] in Bugzilla to organize them. There are currently many language components that these bugs are sorted to, the largest being "[https://bugzilla.mozilla.org/buglist.cgi?component=English%20US&product=Tech%20Evangelism&query_format=advanced&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0&list_id=10190566 English US]". In order to make it easier to monitor and maintain, all desktop bugs that are still valid are being moved to the [https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Desktop&resolution=---&list_id=10190589 Desktop component] in Bugzilla.

Two other areas in Tech Evangelism on Bugzilla to be aware of are "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Mobile&resolution=--- Mobile]" and "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Preinstalled%20B2G%20Apps&resolution=--- Preinstalled B2G Apps]". These bugs do not belong to Desktop Tech Evangelism and should not be moved.

==Old Tech Evangelism Bugs==

There are some desktop bugs in Bugzilla that are very old, some dating back to the early 2000's. These bugs should be treated the same as any bug today. If the issue still exists, move the bug to the Desktop component and leave a comment.

There is also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ video walk through] that explains how to assess these bugs.

Compatibility

2014-05-13T22:15:27Z

Adam s: /* Desktop Web Compatibility */

'''A person should be able to use the Web whatever the device and the browser they are using.'''

Web Compatibility issues are related to Web sites implementing techniques that create issues for a certain class of browsers and/or devices. A person will not be able to use a Web site according to his/her own choices.

These issues are cross-platforms, cross-products and related to the Web as a whole. There are circumstances when a company will choose to use a standardized techniques which is not available for an old browser, but that should be mitigated in making the [http://christianheilmann.com/2012/02/16/stumbling-on-the-escalator/ Web site usable in any circumstances]. So if a person is using the last version of [[Firefox]] or a vocal browser such as Jaws, or a proxy browser such as Opera Mini or UCWeb, the Web site should be able to work.

[[Mozilla]] has two areas for dealing with Web Compatibility issues. The goal is to make the Web usable by anyone and not only Firefox products, but we will focus the efforts on solving issues for Firefox users.

== Desktop Web Compatibility ==

The [[Compatibility/Desktop|Desktop Web Compatibility]] effort is at this time '''mostly driven by volunteers'''. There are no specific Mozilla resources allocated on it. You are more than welcome to contribute and help solving the issues by contacting Web sites.

* [https://bugzilla.mozilla.org/buglist.cgi?f1=component&list_id=8384365&o1=notequals&resolution=---&query_format=advanced&v1=Mobile&product=Tech%20Evangelism List of Desktop Web Compatibility issues]

== Mobile Web Compatibility ==

The [[Compatibility/Mobile|Mobile Web Compatibility]] effort focuses on solving Web Compatibility issues with [[Fennec|Firefox for Android]] and [[FirefoxOS]]. Mozilla can't fix the Web alone, so you are welcome to participate with us

* [https://bugzilla.mozilla.org/buglist.cgi?list_id=8384376&resolution=---&query_format=advanced&component=Mobile&product=Tech%20Evangelism List of Mobile Web Compatibility issues]

== Web Compatibility How-To ==
In case, you want to contribute time or help fix issues, you can learn how to [[Compatibility/Guide|get involved]]

[[Category:Web Compatibility]]

Compatibility/Contribute

2014-05-13T22:04:36Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' [[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section, create a Bugzilla account and use Bugs Ahoy! to find bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-13T22:03:28Z

Adam s: /* Testing and Technical analysis */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' [[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues Read this]] wiki section, create a Bugzilla account and use Bugs Ahoy! to find bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line.

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-13T21:46:53Z

Adam s: /* Advocacy */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], join our [https://lists.mozilla.org/listinfo/compatibility mailing list] or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-13T21:45:43Z

Adam s: /* Advocacy */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on [https://twitter.com/MozWebCompat twitter], [https://lists.mozilla.org/listinfo/compatibility join our mailing] list or come chat with us [https://wiki.mozilla.org/Irc on IRC] in #webcompat. To learn more browse the [[Compatibility/Mobile|compatibility wiki]] or read our [http://planet.webcompat.com/ blog posts].

Compatibility/Contribute

2014-05-13T21:38:25Z

Adam s: /* Writing code and UX */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute/SitesTools

2014-05-13T21:37:19Z

Adam s: Created page with "== Web Compatibility Sites & Tools == Below is a list of websites and tools that are used in Web Compatibility. These are all hosted on Github with open issues that you can he..."

Compatibility/Contribute

2014-05-13T21:32:02Z

Adam s: /* Writing code and UX */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools **link for automated tools** and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.
*** [https://github.com/seiflotfy/compatipede/ Compatipede]
*** [https://github.com/hallvors/sitecomptester-extension SiteCompTester-Extension]

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute

2014-05-13T21:25:16Z

Adam s: /* Writing code and UX */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools **link for automated tools** and [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20automated%20testing reach out] when you’re ready to start.

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compatibility websites and tools.
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the [[Compatibility/Contribute/SitesTools|sites & tools]]. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20UX reach out] to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our [[Compatibility/Contribute/SitesTools|sites]], [https://bug927478.bugzilla.mozilla.org/attachment.cgi?id=8376727 logo] and t-shirt designs. Then [mailto:compatibility@lists.mozilla.org?Subject=Help%20with%20design reach out] to get started.

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute

2014-05-13T04:46:10Z

Adam s: /* Regional and language */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding good contacts and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools {{tools links}} and reach out when you’re ready to start{{contacts}}

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compat websites (Webcompat.com / AWCY)
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the websites and planned features, contact us to let us know and fork away!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools. (AWCY.com)
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the sites and tools. Then reach out to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our sites, logo and t-shirt designs. Then reach out to get started {{contact}}

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute

2014-05-13T04:43:50Z

Adam s: /* Regional and language */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, your help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools {{tools links}} and reach out when you’re ready to start{{contacts}}

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compat websites (Webcompat.com / AWCY)
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the websites and planned features, contact us to let us know and fork away!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools. (AWCY.com)
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the sites and tools. Then reach out to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our sites, logo and t-shirt designs. Then reach out to get started {{contact}}

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute

2014-05-12T21:23:38Z

Adam s: /* Regional and language */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [[Compatibility/Countries|Check for your country]] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, you’re help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [[Compatibility/StdLetters|email templates]] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs that are ready for the site to be contacted. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla].
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.
::# [[Compatibility/Guide#Finding_The_Right_Contact_on_a_Web_site|Learn more]] about finding and contacting websites.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools {{tools links}} and reach out when you’re ready to start{{contacts}}

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compat websites (Webcompat.com / AWCY)
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the websites and planned features, contact us to let us know and fork away!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools. (AWCY.com)
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the sites and tools. Then reach out to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our sites, logo and t-shirt designs. Then reach out to get started {{contact}}

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute

2014-05-12T21:13:55Z

Adam s: /* Regional and language */

== Help make the web more open! ==

The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compatibility. We need your skills, insight and opinions to help reach keep the web open globally.

== Regional and language ==
*'''Collecting information on popular sites in your local region'''
**'''How you can help:''' Build lists of most frequently used sites in your country/region
**'''Skills required:''' Knowledge of popular web sites in your region
**'''Description:''' In order to ensure websites are working in Firefox all around the world, we build lists of the most popular sites in specific countries. The list usually starts by taking the top 100 sites for the region from a site like Alexa.com then asking volunteers to add and refine the list as makes sense. The list is used to perform automated compatibility tests for each site in that region.
**'''Get started:''' [https://wiki.mozilla.org/Compatibility/Countries Check for your country] to see if there is a top 100 sites list already created and start adding. Please leave your changes highlighted in another color so we can update the master lists. If you think a site on the list is not important for the region, leave a note beside it but do not delete it. If your region is not listed or there is no link for a top site list [mailto:compatibility@lists.mozilla.org?Subject=New%20top%20sites%20list%20request let us know] so we can add it.

*'''Translation'''
**'''How you can help:''' Many sites and tools built for Web Compatibility are only in English, you’re help translating goes a long way to bringing the effort to more countries around the world.
**'''Skills required:''' Languages: English + more
**'''Description:''' Web compatibility is a global effort, that has sites and tools which should be available in multiple languages. Translating these can help others get involved, let site owners understand the reported bugs and help supporters spread the word.
**'''Get started:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.

*'''Casual bug reporting'''
**'''How you can help:''' During your web travels if you notice a website works properly in one browser but not in another, you can report a bug to help get it fixed!
**'''Skills required:''' Being awesome, takes two minutes
**'''Description:''' One of the great things about Web Compatibility is once you know what to look for it’s much easier to notice potential bugs during your regular browsing. If you notice a problem with a website you can report it in less than 1 minute with the Web Compatibility browser add ons.
**'''Get started:''' Report site issues at [http://www.webcompat.com Webcompat.com] or [https://github.com/webcompat/webcompat-reporter-extensions install a browser extension] for Chrome, Firefox (29+), Opera and Safari for the fastest bug reporting experience.

*'''Outreach: Contacting web sites with fixes'''
**'''How you can help:''' Find contacts for websites. Contact websites with suggested fixes.
**'''Skills required:''' Web researching and communication
**'''Description:''' Once a compatibility bug is analyzed a fix has been suggested, the site should be contacted to notify them of the issue. Your language skills and local knowledge make finding contacts easier. Find a contact at the website and send them a polite message. We have a tool to help explain the problem to non-technical contacts and [https://wiki.mozilla.org/Compatibility/StdLetters email templates] to make communicating in other languages easier.
**'''Get started:'''

::# Create a Bugzilla account
::# Find bugs to contact. Use [http://webcompat.com/bugsahoy/?outreach=1 Bugs ahoy!] or [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&columnlist=bug_status%2Cbug_id%2Copendate%2Ccf_last_resolved%2Cshort_desc%2Cbug_file_loc%2Cstatus_whiteboard&o1=substring&resolution=---&o2=notsubstring&query_format=advanced&f2=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5bcontactready%5d&component=Mobile&v2=%5bsitewait%5d&product=Tech%20Evangelism&list_id=10172504 search on Bugzilla] for bugs with whiteboard flag set to Contactready.
::# Use the simple bug tool by going to [http://webcompat.com/simplebug/#mozilla/ this link] and adding the bug number you're working on to the end of the URL. Example: http://webcompat.com/simplebug/#mozilla/966310
::# Don't be afraid to ask for help! Mentors are assigned to most bugs for this reason. If you want to talk something over just comment on the bug that you some need help, a mentor will be notified and reach out to you.

== Testing and Technical analysis ==

*'''Testing websites for compatibility issues'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''Skills required:''' A keen eye for spotting visual differences
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists.
**'''Get started:''' //maybe hallvors can help to write this

*'''Analyzing Web Compat Issues'''
**'''How you can help:''' Assign a bug to yourself and dig in. Each bug has a description of the issue to read, test the site and look through the code to find the issue. Bonus points if you can suggest a way to fix it. (Bugs ahoy, OLD TE bugs)
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit).
**'''Get started:''' Read this (https://wiki.mozilla.org/Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues), create a bugzilla account and use Bugs Ahoy! to find bugs to work on.
** Provide some info on common types and blogs with info eg. Karl’s blog with httpie (http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing)

== Writing code and UX ==

*'''Building tools for automated testing'''
**'''How you can help:''' Build tools that run through lists of sites and perform tests to identify compatibility issues
**'''Skills required:''' JS, Your favorite language
**'''Description:''' The web is big, really big. In order to test sites for compatibility issues and keep track of regressions we rely on a healthy share of automated testing. We have a few tools at our disposal that work very well, but there’s always room for improvement.
**'''Get started:''' There are lots of ways you can help, read about our current tools {{tools links}} and reach out when you’re ready to start{{contacts}}

*'''Web coding'''
**'''How you can help:''' There are lots of great features that need to be built for the compat websites (Webcompat.com / AWCY)
**'''Skills required:''' JS, HTML, CSS, Python/Ruby/PHP/Your preference
**'''Description:''' Web Compatibility hosts a few web sites/tools that make our jobs easier and help spread the word. There are lots of current and future features that need to be worked on. We can use your help to code these sites and tools.
**'''Get started:''' Check out the websites and planned features, contact us to let us know and fork away!

*'''User Experience'''
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools. (AWCY.com)
**'''Skills required:''' UX
**'''Description:''' Although we try to always put the user front of mind when designing Web Compatibility sites/tools, the expertise of a UX designer is a goes a long way. Help us shape the designs and interactions of the Web Compatibility toolset.
**'''Get started:''' Check out the sites and tools. Then reach out to us to get started!

*'''Design'''
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''Description:''' In order to make Web Compatibility stand out we need help from great designers. Everything from our websites, to logos and even t-shirts need a creative eye to really shine.
**'''Get started:''' Check out our sites, logo and t-shirt designs. Then reach out to get started {{contact}}

== Advocacy ==

*'''Spreading the word'''
**'''How you can help:''' Talks, tweets, blogs, videos, handing out flyers on corners
**'''Skills required:''' Passion for a free and open web
**'''Description:''' The more users and developers are aware of web compatibility the better! You can post as small as a tweet or as big as a blog, we can use your help spreading the word.
**'''Get started:''' Follow us on twitter, join our mailing list or come chat with us in #webcompat.

Compatibility/Contribute

2014-05-12T20:20:58Z

Adam s: /* Regional and language */

Compatibility/Contribute

2014-05-12T20:00:27Z

Adam s: /* Regional and language */

Compatibility/Contribute

2014-05-12T19:59:54Z

Adam s: /* Regional and language */

Compatibility/Contribute

2014-05-12T15:33:16Z

Adam s: /* Regional and language */

Compatibility/Contribute

2014-05-10T01:02:22Z

Adam s: /* Testing and Technical analysis */

Compatibility/Contribute

2014-05-10T00:32:20Z

Adam s: Created page with "== Help make the web more open! == The web is meant to be open and accessible to everyone regardless of how they access it. Help to keep it open by contributing to Web Compat..."

Compatibility/Mobile

2014-05-09T19:57:41Z

Adam s: /* Get Involved */

=Mobile Web Compatibility=

==What Are Web Compatibility Issues?==
'''A person should be able to use the Web with whichever device and browser they are using.'''

Unfortunately, some developers by choice or negligence will make their Web sites unusable by specific devices or browsers. We need to '''open up the Web''' to any rendering engines (Blink, Gecko, Trident, etc.) and/or browsers, when used on mobile devices.

There are 4 key problem areas that must be addressed:

# [[UA/UseCases|user agent (UA) detection]]
# specific CSS prefixes (such as WebKit)
# specific DOM/JS/content (such as WebKit)
# Gecko limitations (for Mozilla)

==Goal==

The vague goal for this project is to open up the mobile Web to all browsers. A specific project goal is being defined by the market insights, product, and project management teams.

===Scope===

;In scope
* Any site with a mobile version
* Any locale

;Out of scope
* Site enhancements
* Trivial site layout or functional bugs
* Firefox Marketplace app testing

== Get Involved ==

'''Fixing the Web''' will only be successful with the efforts of everyone (Web site developers, Volunteers, Partners, and Mozilla employees). '''Mozilla can't do it alone'''.

* Web Compatibility 101 (@@TODO@@)
* Subscribe to [https://lists.mozilla.org/listinfo/compatibility Web Compatibility] ([https://groups.google.com/forum/#!forum/mozilla.compatibility Archives])
* Read the [[Compatibility/Mobile#Minutes_and_Progress_Reports|previous meetings minutes]]
* [[Compatibility/Guide|How to participate?]]
** Reporting Web sites issues
** Analyzing Web sites issues
** Contacting Web sites for solving the issues
* [[Compatibility/Contribute|Ways to contribute]]

==Projects==

Web Compatibility is wide. There are many possible projects around this topics. Some are currently active, some are either [[Compatibility/Projects|would be good to do or have been actually done]].

=== Wipe Out User Agent (UA) Overrides {{WebCompatStatus|progress}}===
owner: kdubost 
The [[UA/override|UA override]] mechanism allows B2G to force mobile content by sending a custom UA to a specified domain. The goal of this project is to drive the B2G UA override list to zero.

=== Fixing UA detection libraries {{WebCompatStatus|progress}}===
owner: miketaylr 
[[Compatibility/UADetectionLibraries|User Agent detection libraries]] sometimes do not take into account Firefox OS and/or Firefox for Android. We (Mozilla and the community) try to contact them to fix the libraries.

=== Evangelism {{WebCompatStatus|progress}}===
Part of the [[Evangelism]] effort, the [[Compatibility/Guide|Web Compatibility Guide]] helps individuals to report, analyze and contact Web sites for issues with Web Compatibility. (work in progress)

=== (Mobile) Library and Framework Investigation {{WebCompatStatus|progress}}===
The ongoing goal of this [[Compatibility/Mobile/Libraries | project]] is to "audit" source code and issues/bug trackers of popular mobile frameworks to identify bugs, workarounds, or performance issues that need increased attention from Mozilla.

=== Video project {{WebCompatStatus|progress}}===
owner: hallvors 
The [[Compatibility/Video|Video project]] aims to get an overview of and improve the compatibility state of video watching sites.

=== 90% Mobile Compatibility for the Alexa Top 1000 Sites {{WebCompatStatus|backlog}}===
[[Compatibility/Mobile/90AlexaTop1000|90% Mobile Compatibility for the Alexa Top 1000 Sites]] to achieve 90% compatibility in terms of mobile content sent to Firefox for Android and Firefox OS by the Alexa top 1000 global sites.

==Communication==
{| class="wikitable fullwidth-table"
! Communication Type !! Mechanism !! Audience
|-
| Announcements || [https://lists.mozilla.org/listinfo/compatibility compatibility] and [https://lists.mozilla.org/listinfo/dev-planning dev-planning] lists || all
|-
| General discussion || [https://lists.mozilla.org/listinfo/compatibility compatibility] list || all
|-
| Meetings || Tuesdays 6am PT
{{conf|98830}}
* Vidyo: compatibility ([https://v.mozilla.com/flex.html?roomdirect.html&key=59AT9HQ8BY9R room link])
* IRC: [irc://irc.mozilla.org/webcompat #webcompat]
* Agenda: [https://etherpad.mozilla.org/webcompat etherpad]. If no agenda items the evening before, there will be no meeting held. Anyone can add agenda items.
|| all
|-
| Meeting summaries || [[Compatibility/Mobile | this wiki]] and [http://lawrencemandel.com Lawrence Mandel's blog]|| all
|-
| Evangelism status || [http://arewecompatibleyet.com arewecompatibleyet.com report] || all
|}

===Press & Blog Posts===

Our blog posts are aggregated through [http://planet.webcompat.com/ Planet Web Compatibility]. You will also find an history of our blog posts in the meeting minutes, check for the section "Broken Voices Of the Web"

* Mar 1, 2013 - [http://lawrencemandel.com/2013/03/01/help-wanted-firefox-os-ua-detection/ Lawrence Mandel: Help Wanted: Firefox OS UA Detection]
* Oct 30, 2012 - [http://blog.gerv.net/2012/10/website-evangelism-mobilizing-mozilla/ Website Evangelism: Mobilizing Mozilla (Gerv Markham)]

===Minutes and Progress Reports ===
{| class="wikitable collapsible" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" colspan="2" | 2014
|-
|
* Tuesday, May 27, 2014 -
* Tuesday, May 20, 2014 -
* Tuesday, May 13, 2014 -
* Tuesday, May 6, 2014 -
* Tuesday, April 29, 2014 - [[Compatibility/Mobile/2014-04-29|Minutes]]
* Tuesday, April 22, 2014 - [[Compatibility/Mobile/2014-04-23|Minutes]] (summary only)
* Tuesday, April 15, 2014 - [[Compatibility/Mobile/2014-04-15|Minutes]] (summary only)
* Tuesday, April 8, 2014 - [[Compatibility/Mobile/2014-04-08|Minutes]] (summary only)
* Tuesday, April 1, 2014 - [[Compatibility/Mobile/2014-04-01|Minutes]]
* Tuesday, March 25, 2014 - [[Compatibility/Mobile/2014-03-25|Minutes]]
* Tuesday, March 18, 2014 - [[Compatibility/Mobile/2014-03-18|Minutes]] '''Date change'''
* Monday, March 10, 2014 - [[Compatibility/Mobile/2014-03-10|Minutes]]
* Monday, March 3, 2014 - [[Compatibility/Mobile/2014-03-03|Minutes]]
* Monday, February 24, 2014 - [[Compatibility/Mobile/2014-02-24|Minutes]]
* Monday, February 17, 2014 - [[Compatibility/Mobile/2014-02-17|Minutes]] (summary only)
* Monday, February 10, 2014 - [[Compatibility/Mobile/2014-02-10|Minutes]] (summary only)
* Monday, February 3, 2014 to Friday, February 7, 2014 - [[Compatibility/Mobile/2014-02-work-week|Work Week Minutes]] (Mountain View, California)
* Monday, February 3, 2014 - [[Compatibility/Mobile/2014-02-03|Minutes]] (summary only)
* Monday, January 27, 2014 - [[Compatibility/Mobile/2014-01-27|Minutes]]
* Monday, January 20, 2014 - [[Compatibility/Mobile/2014-01-20|Minutes]]
* Monday, January 13, 2014 - [[Compatibility/Mobile/2014-01-13|Minutes]]
* Monday, January 6, 2014 - [[Compatibility/Mobile/2014-01-06|Minutes]]
|}

{| class="wikitable collapsible collapsed" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" colspan="2" | 2013
|-
|
* Monday, December 30, 2013 - Meeting canceled for holidays
* Monday, December 23, 2013 - Meeting canceled for holidays
* Monday, December 16, 2013 - [[Compatibility/Mobile/2013-12-16|Minutes]]
* Monday, December 9, 2013 - [[Compatibility/Mobile/2013-12-09|Minutes]]
* Monday, December 2, 2013 - [[Compatibility/Mobile/2013-12-02|Minutes]]
* Monday, November 25, 2013 - Meeting canceled for week without meetings
* Monday, November 18, 2013 - [[Compatibility/Mobile/2013-11-18|Minutes]]
* Monday, November 11, 2013 - [[Compatibility/Mobile/2013-11-11|Minutes]]
* Monday, November 4, 2013 - [[Compatibility/Mobile/2013-11-04|Minutes]]
* Monday, October 28, 2013 - [[Compatibility/Mobile/2013-10-28|Minutes]]
* Monday, October 21, 2013 - [[Compatibility/Mobile/2013-10-21|Minutes]]
* Monday, October 14, 2013 - [[Compatibility/Mobile/2013-10-14|Minutes]]
* Monday, September 30, 2013 - [[Compatibility/Mobile/2013-09-30|Minutes]]
* Monday, September 23, 2013 - [[Compatibility/Mobile/2013-09-23|Minutes]]
* Monday, September 16, 2013 - [[Compatibility/Mobile/2013-09-16|Minutes]]
* Monday, September 9, 2013 - [[Compatibility/Mobile/2013-09-09|Minutes]]
* Monday, August 26, 2013 - [[Compatibility/Mobile/2013-08-26|Minutes]]
* Monday, August 19, 2013 - [[Compatibility/Mobile/2013-08-19|Minutes]]
* Monday, August 12, 2013 - [[Compatibility/Mobile/2013-08-12|Minutes]]
* Monday, August 5, 2013 - [[Compatibility/Mobile/2013-08-05|Minutes]]
* Monday, July 29, 2013 - [[Compatibility/Mobile/2013-07-29|Minutes]]
* Monday, July 22, 2013 - [[Compatibility/Mobile/2013-07-22|Minutes]]
* Monday, July 8, 2013 - [[Compatibility/Mobile/2013-07-08|Minutes]]
* Monday, June 24, 2013 - [[Compatibility/Mobile/2013-06-24|Minutes]]
* Monday, June 10, 2013 - [[Compatibility/Mobile/2013-06-10|Minutes]]
* Monday, June 3, 2013 - [[Compatibility/Mobile/2013-06-03|Minutes]]
* Monday, May 27, 2013 - Cancelled due to Memorial Day
* Monday, May 20, 2013 - Cancelled due to Victoria Day
* Monday, May 13, 2013 - [[Compatibility/Mobile/2013-05-13|Minutes]]
* Monday, May 6, 2013 - [[Compatibility/Mobile/2013-05-06|Minutes]]
* Monday, April 29, 2013 - [[Compatibility/Mobile/2013-04-29|Minutes]]
* Monday, April 22, 2013 - [[Compatibility/Mobile/2013-04-22|Minutes]]
* Monday, April 15, 2013 - Meeting cancelled due to availability
* Monday, April 8, 2013 - [[Compatibility/Mobile/2013-04-08|Minutes]]
* Monday, April 1, 2013 - [[Compatibility/Mobile/2013-04-01|Minutes]]
* Monday, March 25, 2013 - [[Compatibility/Mobile/2013-03-25|Minutes]]
* Monday, March 18, 2013 - [[Compatibility/Mobile/2013-03-18|Minutes]]
* Monday, March 11, 2013 - [[Compatibility/Mobile/2013-03-11|Minutes]]
* Monday, March 4, 2013 - [[Compatibility/Mobile/2013-03-04|Minutes]]
* Monday, February 25, 2013 - [[Compatibility/Mobile/2013-02-25|Minutes]]
* Thursday, February 14, 2013 - [[Compatibility/Mobile/2013-02-14|Minutes]]
* Thursday, February 7, 2013 - [[Compatibility/Mobile/2013-02-07|Minutes]]
* Thursday, January 31, 2013 - [[Compatibility/Mobile/2013-01-31|Minutes]]
* Thursday, January 24, 2013 - Meeting cancelled due to availability
* Thursday, January 17, 2013 - [[Compatibility/Mobile/2013-01-17|Minutes]]
* Thursday, January 10, 2013 - Meeting cancelled due to B2G work week
* Thursday, January 3, 2013 - Meeting cancelled for holidays
|}

{| class="wikitable collapsible collapsed" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" colspan="2" | 2012
|-
|
* Thursday, December 27, 2012 - Meeting cancelled for holidays
* Thursday, December 20, 2012 - [[Compatibility/Mobile/2012-12-20|Minutes]]
* Thursday, December 13, 2012 - Meeting cancelled due to availability to regular participants
* Thursday, December 6, 2012 - [[Compatibility/Mobile/2012-12-06|Minutes]]
* Thursday, November 29, 2012 - [[Compatibility/Mobile/2012-11-29|Minutes]]
* Thursday, November 22, 2012 - Meeting cancelled for US Thanksgiving
* Thursday, November 15, 2012 - [[Compatibility/Mobile/2012-11-15|Minutes]]
* Thursday, November 8, 2012 - [[Compatibility/Mobile/2012-11-08|Status]] (meeting cancelled), [http://lawrencemandel.com/2012/11/09/mobile-web-compatibility-nov-9-2012-video-update-ua-detection-tools-phony-for-b2g/ Blog – Video update, UA detection tools, Phony for B2G?]
* Thursday, November 1, 2012 - [[Compatibility/Mobile/2012-11-01|Minutes]]
* Monday, October 22, 2012 - [https://air.mozilla.org/the-monday-meeting-20121022/ Video update (at 4:00)]
|}

=== Events ===

We might be [[Compatibility/Calendar|somewhere in the world]], close to you and maybe we can find a way to help you kick start a Web Compatibility Activity in your own country. Or you want us to speak at a conference.

=== Presentations ===

Here we provide links to presentations about the WebCompat effort.
* https://miketaylr.com/pres/thunderplains/ by [https://wiki.mozilla.org/User:Bear Mike Taylor]
* [http://lmandel.github.io/buildmobileweb/ Building for the Mobile Web] by Lawrence Mandel

==People==

=== Mozilla Corporation ===
{| class="wikitable fullwidth-table"
| Project Champion ||
|-
| Program Management || Lawrence Mandel (irc: lmandel)
|-
| Engineering || Brad Lassey (irc: blassey)
|-
| Product Management || Vishy Krishnamoorthy
|-
| Incoming Bug Triage || Jason Smith (irc: jsmith), Aaron Train (irc: AaronMT)
|-
| QA || Tony Chung, Jason Smith, Aaron Train
|-
| Analysis and Contacts || Hallvord Steen (irc: hallvors), Mike Taylor (irc: miketaylr), [[User:Karlcow|Karl Dubost]] (irc: karlcow), Adam (irc: adam_s)
|-
| Dev Engagement || Ali Spivak
|-
|}

=== Volunteers Leading Web Compatibility efforts ===

You can be part of it. Check [https://groups.google.com/forum/#!msg/mozilla.compatibility/1NyYNpr_T-s/xT5H26MmTDcJ how-to start your own local community], read the [https://wiki.mozilla.org/Compatibility/Guide Guide], be an ambassador for the project, and take a free space down there or create a new locale if it doesn't exist yet. '''It's really up to you''' on making the Web more accessible by anyone. We can help you to start.

{| class="wikitable fullwidth-table"
| Activities || Leader || Joined on (Left)
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Brazil Brazil] || Leo Balter || October 2013
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Brazil Brazil] || Daniel Filho || October 2013
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Brazil Brazil] || Fabricio Zuardi || October 2013
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Colombia Colombia] || '''Free''' ||
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Germany Germany] || Sezen Günes || February 2014
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Greece Greece] || Thanos Lefteris || October 2013
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/India India] || Abdul Rauf (irc: haseeb) || October 2013
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Mexico Mexico] || Alex Mayorga || November 2013
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Poland Poland] || '''Free''' ||
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Serbia Serbia] || '''Free''' ||
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Spain Spain] || '''Free''' ||
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Sweden Sweden] || Oliver Propst || January 2014
|-
| [https://wiki.mozilla.org/Compatibility/Mobile/Venezuela Venezuela] || '''Free''' ||
|-
| Infrastructure || Seif Lotfy || October 2013
|-
| Communication || Kohei Yoshino || October 2013
|-
| UX/Design/webcompat.com || Alexa Roman || January 2014
|-
|}

==References==
* [https://hacks.mozilla.org/2012/01/firefox-goes-2-digit-time-to-check-your-ua-sniffing-scripts/ Firefox goes 2-digit, time to check your UA sniffing scripts]
* [http://hsivonen.iki.fi/vendor-prefixes/ Vendor Prefixes Are Hurting the Web]
* DOM properties that pose potential compat issues
** IE srcelement {{bug|453968}}
* [[Platform/Layout/CSS_Compatibility|Gecko CSS vendo-prefix Compatibility]]
* Analysis of the use of vendor-specific CSS property prefixes on the web {{bug|708406}}
* [http://www.google.com/webfonts#UsePlace:use/Collection:Open+Sans Google Web fonts]
* [https://developer.mozilla.org/en-US/docs/Gecko_user_agent_string_reference Gecko user agent string reference]
* [[Changing_the_UA_String|Changing the UA string]]
* [[Fennec/User_Agent|Fennec User Agent]]
* [https://developer.mozilla.org/en-US/docs/Web_development/Writing_forward-compatible_websites Writing forward-compatible websites]
* [http://www-archive.mozilla.org/projects/tech-evangelism/site/letters.html Site Evangelism Letters] from previous evangelism effort
* Site feedback from [http://input.mozilla.org/en-US/?q=&product=mobile&version=--&date_start=&date_end=&sentiment=sad input.mozilla.org]
* Add device info to User-Agent {{bug|625238}}
* [https://docs.google.com/spreadsheet/ccc?key=0AuIhlK0fCwP4dEFPR1pUWHk1QVczcV9xbFAtX19CMXc#gid=0 CoreMob (www.coremob.org): Mobile Web App Profile] (from [https://www.w3.org/community/coremob/track/actions/3 W3C])
* [http://www-archive.mozilla.org/newlayout/bugathon.html Firefox bug-a-thon]
* [http://www.quirksmode.org/blog/archives/2012/10/javascript_libr_1.html QuirksMode JavaScript library poll results]
* [http://blog.vlad1.com/2010/03/15/using_a_caching_proxy_server/ Vladimir Vukićević: Using a Caching Proxy Server for Web Demos]
* {{Bug|666041}} CSS Flexbox Layout Level 3
* [https://etherpad.mozilla.org/WebCompat-JobDescriptions Web Compat job descriptions etherpad]
* [[Compatibility/Mobile/GeckoImprovements|Gecko Improvements from Mobile Web Compat Effort]]

[[Category:Mobile]]
[[Category:Web Compatibility]]

WeeklyUpdates/2014-05-05

2014-05-05T17:52:22Z

Adam s: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

* Again, big thanks to [https://mozillians.org/en-US/u/kohei.yoshino/ Kohei Yoshino] to all his amazing pull requests, triaging, and [https://github.com/kyoshino contributions] to [[Webdev/Web_Production|Web Productions]] and specifically the Australis launch on [https://www.mozilla.org mozilla.org]! Without Kohei, it would have been difficult to deliver all of the changes and new content for last Tuesday's Fx 29 launch. <8

* Big thanks to the outgoing Featured Add-ons Board--Michael Balazs, Si Howard, Rejah Rehim, Swarnava Sengupta, Muhammad Mehmood Ali, and Jithin Joji Anchanattu! They were responsible for selecting all the featured add-ons on AMO for the past six months. Deadline to apply for the next board is tomorrow! More info: https://blog.mozilla.org/addons/2014/04/30/apply-featured-board/

* Many thanks to [https://mozillians.org/en-US/u/sjw/ Jonas Witmer] for helping out with over [https://bugzilla.mozilla.org/page.cgi?id=user_activity.html&action=run&who=sjw%40gmx.ch&from=2014-01-18&to=2014-01-20&sort=when 100 Web Compatibility bugs] in the Tech Evangelism component!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
*'''[http://conf.writethedocs.org/na/2014/index.html Write the Docs North America]''' in Portland, Oregon, US
** Mozilla is an Editor level sponsor
** Mozillians Christie Koehler, Eric Shepherd, Luke Crouch, Janet Swisher, Will Bamberg, and Kris Maglione are participating
** "Write the Docs is a series of conferences and local meetups focused on documentation systems, tech writing theory, and information delivery.

Writing and maintaining documentation involves the talents of a multidisciplinary community of technical writers, designers, typesetters, developers, support teams, marketers, and many others.

Our conferences create a time and a place for the global community of documentarians to share information, discuss ideas, and work together to improve the art and science of documentation. "

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* '''[http://indiewebcamp.com/events/2014-05-07-homebrew-website-club Homebrew Website Club Meetup]''', 18:30-19:30 at Mozilla [[SF]]. Description: <blockquote>Are you building your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy?If so (or you want to!), come on by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...</blockquote> Any questions? See [http://indiewebcamp.com/events/2014-05-07-homebrew-website-club the wiki page] or irc://irc.freenode.net/indiewebcamp.

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* '''[http://scotlandjs.com/ ScotlandJS]''' in Edinburgh, Scotland, UK
** Mozillian Angelina Fabbro is speaking.
** "JavaScript keeps growing and growing. It is the language most repos on GitHub are written in!"
* Institute for Women’s Leadership, which runs educational and exchange programs for women all over the world including the TechWomen program that Mozilla gets 'mentees' from, are holding an event at the Mozilla SF office called "Beyond Balance" with speaker Barbara Fittipaldi aimed at increasing women's leadership and empowerment.

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===
Webmaker: We’re helping people to teach the web starting May 12 with a free online training course. Here’s how you can join to help mentor, learn, or just observe: https://blog.webmaker.org/free_training_may12

== Project Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location:''

=== Firefox Mobile ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== [https://webmaker.org/ Webmaker] ===
''Silent Update:''

* We’re helping people to teach the web starting May 12 with a free online training course. Here’s how you can join to help mentor, learn, or just observe: [https://blog.webmaker.org/free_training_may12 https://blog.webmaker.org/free_training_may12]

=== [https://openbadges.org/ Open Badges] ===
''Speaker Location:''

=== [https://mozillascience.org/ Mozilla Science Lab] ===
''Speaker Location:''

=== Mozilla Reps ===
''Speaker Location:''

=== Grow Mozilla ===
''Speaker Location: San Francisco''

One of Mozilla’s goals this year is to [https://wiki.mozilla.org/2014#Enable_Communities_that_have_Impact increase the size of the community by 10 times].

What will these 20,000 active contributors be doing? That is something that the [http://davidwboswell.wordpress.com/2014/03/27/community-building-team/ Community Building team] has been spending the last few months looking into.

We’ve come up with a list of areas that have both high growth potential and align with our strategic goals.

<ul>
<li>Coding</li>
<li>Documentation</li>
<li>Engagement</li>
<li>Localization</li>
<li>Location Services</li>
<li>Privacy/Policy</li>
<li>QA</li>
<li>Support</li>
<li>User Research</li>
<li>Web Compatibility</li>
</ul>

To see all of the teams we’re supporting with their community building efforts, check out this [https://wiki.mozilla.org/Contribute/Areas#SmartSheet_version dashboard].

Are there high growth potential opportunities that we're missing? Are you looking for help bringing contributors in to your project? Send an email to community-building@mozilla.org.

=== Identity ===
''Speaker Location:''

=== Services ===
''Speaker Location:''

=== Firefox Marketplace ===
''Speaker Location:''

=== IT ===
''Speaker Location: mjeffries, San Francisco''

'''Conference Room Survey Update:'''
* Thanks to everyone who took the time to scan and fill out our conference room survey
* Here are some of the top issues from last week: WiFi Connectivity, improved input methods in some conference rooms (instead of the IR remotes)
* The good news: These line up with what IT feels are the top issues as well!
* We are actively working on these issues and will provide updates as they get resolved
* Don’t be shy: Keep the feedback coming! Scan and go!

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Diane Tate
| Developer Relations
| Vision Mobile Survey -- open thru May 9
| San Francisco
| No
| No
| Take the survey at http://www.vmob.me/DE3Q14Mozilla. And distribute this in newsletters, blogs, twitter posts, etc - more fodder for those is at https://data.visionmobile.com/survey-campaigns/DE3Q14Mozilla/promo-material/882785a6026f1b2e48a00fd15d1befe8
|-
| [https://mozillians.org/en-US/u/mchris/ Chris Riley]
| Sr. Policy Engineer
| Net Neutrality
| San Francisco
| No
|
| https://blog.mozilla.org/netpolicy/
|-
| [https://mozillians.org/en-US/u/daherman/ Darren Herman]
| Content Services
| Directory Tiles update
| New York (remote)
| No
|
|
|-
| [https://mozillians.org/en-US/u/fowler/ Alex Fowler]
| Privacy and public policy
| Yahoo! and DNT
| San Francisco
| No
|
| http://yahoopolicy.tumblr.com/post/84363620568/yahoos-default-a-personalized-experience
|-
| Mary Ellen Muckerman
| Engagement / Brand
| MozCamp update
| San Francisco
| No
|
|-
| [https://mozillians.org/en-US/u/mrbkap/ Blake Kaplan (mrbkap)]
| Platform engineer
| Electrolysis update
| New York (remote)
| No
|
|
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

| Cameron Zwarich
| Azita Rashed
| Mountain View
| Mountain View
| Research Engineering - Servo
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====

WeeklyUpdates/2014-05-05

2014-05-05T17:33:42Z

Adam s: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

* Again, big thanks to [https://mozillians.org/en-US/u/kohei.yoshino/ Kohei Yoshino] to all his amazing pull requests, triaging, and [https://github.com/kyoshino contributions] to [[Webdev/Web_Production|Web Productions]] and specifically the Australis launch on [https://www.mozilla.org mozilla.org]! Without Kohei, it would have been difficult to deliver all of the changes and new content for last Tuesday's Fx 29 launch. <8

* Big thanks to the outgoing Featured Add-ons Board--Michael Balazs, Si Howard, Rejah Rehim, Swarnava Sengupta, Muhammad Mehmood Ali, and Jithin Joji Anchanattu! They were responsible for selecting all the featured add-ons on AMO for the past six months. Deadline to apply for the next board is tomorrow! More info: https://blog.mozilla.org/addons/2014/04/30/apply-featured-board/

* Many thanks to [https://mozillians.org/en-US/u/sjw/ Jonas Witmer] for helping out with over 100 Web Compatibility bugs!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
*[http://conf.writethedocs.org/na/2014/index.html Write the Docs North America] in Portland, Oregon, US
** Mozilla is an Editor level sponsor
** Mozillians Christie Koehler, Eric Shepherd, Luke Crouch, Janet Swisher, Will Bamberg, and Kris Maglione are participating
** "Write the Docs is a series of conferences and local meetups focused on documentation systems, tech writing theory, and information delivery.

Writing and maintaining documentation involves the talents of a multidisciplinary community of technical writers, designers, typesetters, developers, support teams, marketers, and many others.

Our conferences create a time and a place for the global community of documentarians to share information, discuss ideas, and work together to improve the art and science of documentation. "

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* '''[http://indiewebcamp.com/events/2014-05-07-homebrew-website-club Homebrew Website Club Meetup]''', 18:30-19:30 at Mozilla [[SF]]. Description: <blockquote>Are you building your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy?If so (or you want to!), come on by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...</blockquote> Any questions? See [http://indiewebcamp.com/events/2014-05-07-homebrew-website-club the wiki page] or irc://irc.freenode.net/indiewebcamp.

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [http://scotlandjs.com/ ScotlandJS] in Edinburgh, Scotland, UK
** Mozillian Angelina Fabbro is speaking.
** "JavaScript keeps growing and growing. It is the language most repos on GitHub are written in!"

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===
Webmaker: We’re helping people to teach the web starting May 12 with a free online training course. Here’s how you can join to help mentor, learn, or just observe: https://blog.webmaker.org/free_training_may12

== Project Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location:''

=== Firefox Mobile ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== [https://webmaker.org/ Webmaker] ===
''Silent Update:''

* We’re helping people to teach the web starting May 12 with a free online training course. Here’s how you can join to help mentor, learn, or just observe: [https://blog.webmaker.org/free_training_may12 https://blog.webmaker.org/free_training_may12]

=== [https://openbadges.org/ Open Badges] ===
''Speaker Location:''

=== [https://mozillascience.org/ Mozilla Science Lab] ===
''Speaker Location:''

=== Mozilla Reps ===
''Speaker Location:''

=== Grow Mozilla ===
''Speaker Location: San Francisco''

One of Mozilla’s goals this year is to [https://wiki.mozilla.org/2014#Enable_Communities_that_have_Impact increase the size of the community by 10 times].

What will these 20,000 active contributors be doing? That is something that the [http://davidwboswell.wordpress.com/2014/03/27/community-building-team/ Community Building team] has been spending the last few months looking into.

We’ve come up with a list of areas that have both high growth potential and align with our strategic goals.

<ul>
<li>Coding</li>
<li>Documentation</li>
<li>Engagement</li>
<li>Localization</li>
<li>Location Services</li>
<li>Privacy/Policy</li>
<li>QA</li>
<li>Support</li>
<li>User Research</li>
<li>Web Compatibility</li>
</ul>

To see all of the teams we’re supporting with their community building efforts, check out this [https://wiki.mozilla.org/Contribute/Areas#SmartSheet_version dashboard].

Are there high growth potential opportunities that we're missing? Are you looking for help bringing contributors in to your project? Send an email to community-building@mozilla.org.

=== Identity ===
''Speaker Location:''

=== Services ===
''Speaker Location:''

=== Firefox Marketplace ===
''Speaker Location:''

=== IT ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Diane Tate
| Developer Relations
| Vision Mobile Survey -- open thru May 9
| San Francisco
| No
| No
| Take the survey at http://www.vmob.me/DE3Q14Mozilla. And distribute this in newsletters, blogs, twitter posts, etc - more fodder for those is at https://data.visionmobile.com/survey-campaigns/DE3Q14Mozilla/promo-material/882785a6026f1b2e48a00fd15d1befe8
|-
| [https://mozillians.org/en-US/u/mchris/ Chris Riley]
| Sr. Policy Engineer
| Net Neutrality
| San Francisco
| No
|
| https://blog.mozilla.org/netpolicy/
|-
| [https://mozillians.org/en-US/u/daherman/ Darren Herman]
| Content Services
| Directory Tiles update
| New York (remote)
| No
|
|
|-
| [https://mozillians.org/en-US/u/fowler/ Alex Fowler]
| Privacy and public policy
| Yahoo! and DNT
| San Francisco
| No
|
| http://yahoopolicy.tumblr.com/post/84363620568/yahoos-default-a-personalized-experience
|-
| Mary Ellen Muckerman
| Engagement / Brand
| MozCamp update
| San Francisco
| No
|
|-
| [https://mozillians.org/en-US/u/mrbkap/ Blake Kaplan (mrbkap)]
| Platform engineer
| Electrolysis update
| New York (remote)
| No
|
|
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

| Cameron Zwarich
| Lars Bergstrom
| US Remote
| Mountain View
| Research Engineering - Servo
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====