I've been working with Asa on a new webtool to help some of the problems faced by the evangelism effort. The tool uses a Firefox extension to allow users to submit sites that block Firefox, misrender, mangle, bust, destroy, or otherwise molest Gecko in some way/shape/form. Most of the data collected is automated (all but problem description category, and a free comment area), and it's completely guided. This forces users to submit valid clean useful data, with minimal effort.
Given that criteria, I was confused by the presence of the categories "freeze", "crashes Mozilla", and "slows down Mozilla" as options. These don't sound like issues that are automatically layout-related, or tech evangelism-related (I assume that is what is meant by "evangelism" here). If the goal (here comes another assumption on my part) is to use this as a tool to stem the flow of bugs filed on layout (or misfiled bugs that should have been filed on layout) that are actually tech evangelism issues, I would have guessed that freezes/crashes/slowdowns would not be layout bugs more often than they are.
This obviously has some positive impacts on layout. Mainly that it will be easy to use evangelism data to evaluate what website issues are bothering Gecko users the most.
What we would like is some input on how we can improve the tool. Note it's still in development and not complete. We will be collecting "language". We will also be dropping "Gecko" since it's been said the API is unstable and not recommended at this time.
I would have just been happy knowing how to launch the tool. The help menu was the last place I looked. ;)
There will also be report generation tool that will generate the top X hosts in the database with a list of the problems reported for them. You'll be able to limit that by things like platform, language, etc. etc.
So the question is... any special requests that we can take into account while refining this tool? How can this tool be modified to better serve you.
You can play with queries here: http://reporter-test.mozilla.org
You can install the extension (still a bit rough) from: http://reporter-test.mozilla.org/install
This is still under development, but should give a good feel of the functionality we are looking to provide.
When it's done, this will sit between the user and bugzilla. So only when problems are confirmed in this database will they be entered in bugzilla. This will avoid dups and provide some statistical information that we just can't seem to get out of bugzilla when average-joe is submitting reports.
Who is going to be entering reports into Bugzilla that are deemed valid?
What sort of information is anticipated will be mined from this? Just on the face of looking at the tool's form, I don't see how one will get more information from this than from a Bugzilla report, even a bad one. The freeform "Describe problem" box seems to not really offer improvement over bad Bugzilla bugs like 'broken in Mozilla, just compare it to IE'.
-- Bill Mason Accessible Internet http://www.accessibleinter.net/ prefix @accessibleinter.net with anything but 'usenet' to reply _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
