Evangelism/WebsiteCompatibilityInternational: Difference between revisions

adding category
(adding category)
 
(3 intermediate revisions by one other user not shown)
Line 50: Line 50:


* Look at the current reporter database to see if there are any changes required to improve scaling with today's data
* Look at the current reporter database to see if there are any changes required to improve scaling with today's data
* Set up a dashboard of reports that include:
* Set up a dashboard of reports that include:
** Number of daily reports (total)
** Number of daily reports (total)
** Number of daily reports (per-browser)
** Number of daily reports (per-browser)
** Per-country reports (total)
 
** Per-country reports vs. local market share
* Set up a search box that returns the most recent reports for that domain.  That result should also be available as an RSS feed.
** Top 10 sites per country (zeitgeist-style)
 
* Expose this information to the public to help drive awareness and value of the data.
* Expose this information to the public to help drive awareness and value of the data.


Line 62: Line 63:
* From first set of data and scoping from stage one, execute on changes to Firefox to improve data fidelity.
* From first set of data and scoping from stage one, execute on changes to Firefox to improve data fidelity.
* Involve support in this process to see if there are things that can improve end user support.
* Involve support in this process to see if there are things that can improve end user support.
* Set up a dashboard of reports that include:
** Per-country reports (total)
** Per-country reports vs. local market share
** Top 10 sites per country (zeitgeist-style)


== Stage Four ==
== Stage Four ==
Line 168: Line 174:
** Yep - that's in the list here.  We'll need data from somewhere else to cross-match, but if we have country data it will be pretty useful to make things actionable. (blizzard)
** Yep - that's in the list here.  We'll need data from somewhere else to cross-match, but if we have country data it will be pretty useful to make things actionable. (blizzard)
* This all looks good but I think we're perhaps missing an opportunity to use our mozilla.org/com traffic to really drive the message directly to broken sites. What about a more highly visible "wall of shame" for these broken sites? One could imagine a tool not unlike the beginning of spreadfirefox where we identify target broken sites ask contributors to help us find webmaster emails and perhaps even more aggressive than that by adding a "email the site and tell them to support standards" (localized) form once we do have an email address. The form email could have stock text that included advertising for the "RSS feed for your site in reporter occurrences" and links to the most common problem types and their solutions (I think the old devedge had some list of documents for common issues.) ( Asa)
* This all looks good but I think we're perhaps missing an opportunity to use our mozilla.org/com traffic to really drive the message directly to broken sites. What about a more highly visible "wall of shame" for these broken sites? One could imagine a tool not unlike the beginning of spreadfirefox where we identify target broken sites ask contributors to help us find webmaster emails and perhaps even more aggressive than that by adding a "email the site and tell them to support standards" (localized) form once we do have an email address. The form email could have stock text that included advertising for the "RSS feed for your site in reporter occurrences" and links to the most common problem types and their solutions (I think the old devedge had some list of documents for common issues.) ( Asa)
[[Category:Web Compatibility]]
Confirmed users
1,567

edits