Evangelism/WebsiteCompatibilityInternational: Difference between revisions

Jump to navigation Jump to search
Line 133: Line 133:
*  Consider a tool a bit more dynamic than a wiki to capture websites that need evangelizing.  Perhaps a simple web app with a database collecting information and then a great way to display it.  Would this be hard?  Don't know... (sethb)
*  Consider a tool a bit more dynamic than a wiki to capture websites that need evangelizing.  Perhaps a simple web app with a database collecting information and then a great way to display it.  Would this be hard?  Don't know... (sethb)
** The reporter site can do this and won't be a wiki.  It's entirely data driven.  Here's an example of a report for www.google.com for one day: http://tinyurl.com/c3rz4s
** The reporter site can do this and won't be a wiki.  It's entirely data driven.  Here's an example of a report for www.google.com for one day: http://tinyurl.com/c3rz4s
* Should look into combining information with herdict: http://futureoftheinternet.org/herdict-launch - lots of good visualization and data ideas here. (blizzard)
* Should look into combining information with [http://futureoftheinternet.org/herdict-launch herdict]:  - lots of good visualization and data ideas here. (blizzard)
* As for Reporter addons, people think that their report will be checked and used by Mozilla. They don't know how to search the database. They also don't know they can see the reports on http://reporter.mozilla.org/. This is because reporter UI don't tell "you can see your report here" nor "you can search reports here". I think if reporter include such a information (link to search interface or metrics), locale web evangelism community will know about it and start using it. That is, if we want to develop local evangelist team, we should update reporter UI to make people know how to see the reports. (dynamis)
* As for Reporter addons, people think that their report will be checked and used by Mozilla. They don't know how to search the database. They also don't know they can see the reports on http://reporter.mozilla.org/. This is because reporter UI don't tell "you can see your report here" nor "you can search reports here". I think if reporter include such a information (link to search interface or metrics), locale web evangelism community will know about it and start using it. That is, if we want to develop local evangelist team, we should update reporter UI to make people know how to see the reports. (dynamis)
** of course, we should prepare introduction page for search page, top 10 sites (per locale), and other metrics and should link to the page from reporter addons UI. (dynamis)
** of course, we should prepare introduction page for search page, top 10 sites (per locale), and other metrics and should link to the page from reporter addons UI. (dynamis)
* As for type of the problem, in Japan (and I believe in China, Korea etc too) [http://en.wikipedia.org/wiki/Mojibake mojibake] (garbage text) is the most famous broken case (caused by lack or miss of charset in the content type header). I thinks it's nice to add mojibake in the type list in the reporter (at least for multibyte locales). (dynamis)
* As for type of the problem, in Japan (and I believe in China, Korea etc too) [http://en.wikipedia.org/wiki/Mojibake mojibake] (garbage text) is the most famous broken case (caused by lack or miss of charset in the content type header). I thinks it's nice to add mojibake in the type list in the reporter (at least for multibyte locales). (dynamis)
* Some problems are caused by addons and reporter should also include installed addons list (not only build config). (dynamis)
* Some problems are caused by addons and reporter should also include installed addons list (not only build config). (dynamis)
Confirmed users
364

edits

Navigation menu