Compatibility/Contribute: Difference between revisions

Jump to navigation Jump to search

Compatibility/Contribute (view source)

Revision as of 04:20, 28 May 2014

1,312 bytes added ,  28 May 2014
m
no edit summary
mNo edit summary
Line 42: Line 42:
**'''Get started:'''
**'''Get started:'''


== Testing and Technical analysis ==
== 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)


*'''Testing websites for compatibility issues'''
*'''User Experience'''
**'''How you can help:''' Test popular sites in your region and file bugs. Use screenshot application, install an automated testing program or manually test
**'''How you can help:''' Use your expertise to help us design the way users interact with our sites and tools.
**'''Skills required:''' A keen eye for spotting visual differences
**'''Skills required:''' UX
**'''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.
**'''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:''' //maybe hallvors can help to write this *screenshot vid*
**'''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!


*'''Analyzing Web Compat Issues'''
*'''Design'''
**'''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.
**'''How you can help:''' Logos, sticker/shirt designs, improving current sites
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection
**'''Skills required:''' Photoshop, Illustrator, Design skills, etc.
**'''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).
**'''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:'''  
**'''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.
***[[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 ==
== Writing code ==
Line 77: Line 83:
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!
**'''Get started:''' Check out the open issues in the [[Compatibility/Contribute/SitesTools|sites & tools]] and dig in!


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


*'''Translation'''
*'''Testing websites for compatibility issues'''
**'''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.
**'''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:''' Languages: English + more
**'''Skills required:''' A keen eye for spotting visual differences
**'''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.
**'''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:''' Check out the [https://etherpad.mozilla.org/webcompat-translate translation guide] to see where you can help.
**'''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.
Adam s
Confirmed users
44

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/983432"

Navigation menu