Mobile/Evangelism/Outreach plan: Difference between revisions

Line 13: Line 13:
# Outreach: reach out to the site to notify them of the problems, provide recommendations on what they can do to fix the issues, and give them information about why it would be good for their site & the web to fix them.
# Outreach: reach out to the site to notify them of the problems, provide recommendations on what they can do to fix the issues, and give them information about why it would be good for their site & the web to fix them.


== Phase 1: detecting problematic web sites ==
== Phase 1: Detecting web sites that have issues in Firefox for Android ==
This phase consists in testing Web sites and determining if the experience is correct or not.


This phase consists of testing Web sites and determining if the experience in the Firefox for Android browser is correct or not.
There is a testing guide available that details the steps to take when testing web sites on mobile devices:
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_for_Android/Compatibility_Testing
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_for_Android/Compatibility_Testing


'''Open point 1: how to report working sites?''' I guess a lot of the white sites on http://people.mozilla.org/~lmandel/arewecompatibleyet/#about may be just working ones.
For many regions, you can start with the sites listed on the "Are We Compatible Yet" site: http://people.mozilla.org/~lmandel/arewecompatibleyet and test their compatibility in your locale (if they are localized for your country/region/language). 
 
''How & When to Test (some ideas)'':
* '''Test for 1/4 hour''' (or longer). Take a short break to test & find bugs. Be sure to report what you find in Bugzilla.
* '''Regional competition''': Show progress in your locale by comparing to others (25% of the Top-100 pl Web sites tested were compatible vs 12% of the sk ones).
* '''Organize test days in your city/town/region''' - get people together to test websites and report issues.  


'''Open point 2: a way to report without a bugzilla account?'''
''Who can help'': anybody with an Android phone -> '''crowdsourcing'''


'''Open point 3: asking Moz Reps of the different countries to bring a Top-100 for their countries'''
''Result'': bugs documenting non-working web sites globally.


''Who can help'': anybody with an Android phone -> '''crowdsourcing'''


''Result'': a bug entry per non-working web sites.
'''Open point 1: Is there a way to report issues without a bugzilla account?'''


''Events that can be done'':
'''Open point 2: Can we have Mozilla Reps in different countries create a Top-100 for their countries (beyond what is in the Are We Compatible Yet list)'''
* '''The testing 1/4 hour''' (or longer). In the middle of another event, pause, test, report. This can be done online too. To coordinate with QA.
* '''Mini-contest''': by showing progress in testing by locale (25% of the Top-100 pl Web sites tested vs 12% of the sk ones), we can foster emulation. To coordinate with reps


== Phase 2 : triage / analyse of the problematic ==
== Phase 2 : triage / analyse of the problematic ==
canmove, Confirmed users
842

edits