Mobile/Evangelism/Outreach plan: Difference between revisions

Mobile/Evangelism/Outreach plan (view source)

Revision as of 15:43, 11 December 2012

551 bytes added , 11 December 2012

→‎Phase 2 : triage / analyse of the problematic

Aspivak

canmove, Confirmed users

842

edits

@@ Line 36: / Line 36: @@
 '''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)'''
-== Phase 2 : triage / analyse of the problematic ==
+== Phase 2 : Triage / Analyze the Problems with each site ==
-This is the most complex phase as it needs to be carefully done, or the information given to the Web site will be incorrect or incomplete and not everybody have the technical background to do it.
-There are two sub-phases
+This is the most complex phase as the issues and solutions need to be carefully analyzed and reported, or the information given to the problematic Web site will be incorrect or incomplete. It is also important to realize that not everybody who receives notification about issues with their web site will have the technical background to make the recommended changes. There may be questions about how much work it will take to fix the site. etc. These should be covered in the email as well as the reference sites we provide to the site owner/developer.
-# reproducing the problem -> anybody can help here (crowdsourcing)
-# categorizing the problems -> This is the critical element and the resource bottleneck
+There are two sub-phases:
+# reproducing the problem -> anybody can help do this (crowdsourcing).
+:Look up bugs, go to the site, reproduce and verify the issues. Make a note in the bug that it has been tested and verified.
+# Defining and categorizing the problems -> This is the critical element and the resource bottleneck
+Common issues:
 :UA: different web sites Android/iPhone/Fx
 :layout: something doesn't look ok, what.
 :Behavioral problem: an action doesn't work.
 :Library problem
-'''Open Point 4: How to make this more efficient?'''
+===How to participate in this phase:===
+*Pick a web site bug to analyze (or analyze your own bugs from Phase 1): add [Analysis in progress] and put themselves under ''Assignee''.
+*Document the causes of the problems in the bug. When you have solved the issues, label the bug with [Analysis done]
+*The mobile team runs weekly metrics on new [Analysis in progress], new [Analysis done] and list of [Analysis in progress] older than two weeks to see if the assignee need help.
+'''NOTES: Tools ARE needed to make this process more efficient'''
+* Call for help: assignee should be able to ask more skilled people to help (devs) -> ''process to establish'' (?)
 *Automatic tools to help (detection of Webkit-only properties, detection of different site for different UA, even if it may be imperfect)
 *Documentation of the problems and how to check them.
-How to follow work in this phase:
-*people take a few web sites to analyze: they add [Analysis in progress] and put themselves under ''Assignee''.
-*weekly metrics on new [Analysis in progress], new [Analysis done] and list of [Analysis in progress] older than two weeks to see if the assignee need help.
-Call for help: assignee should be able to ask more skilled people to help (devs) -> ''process to establish'' (?)
-'''Open point 5''': process for call for help
-'''Open point 6''': how to recruit skilled people to help here? This is the bottleneck, at least at the beginning.
 == Phase 3 : outreach ==