Agenda
- Meeting to discuss the work done so far on this project and talk about next steps and priorities.
Attendees
- marcia, kairo, chofmann, smooney
Notes
- Categories so far look good but might want to tune those a big or even subcategorize.
- Priorities
- 1. Get reports we use in the main system
- 2. Workflow improvements
- 3. Support new kinds of analysis
- Custom reports
- There are a number of custom reports that people have put together.
- Figure out what those are and get them on the crash stats site.
- Some might be logged already but we need a full list with bugs.
- Project details
- Start moving stuff to the mozilla wiki from Kairo's private wiki.
- Keep working with private categorization for now.
- UI tweaks
- High and low priority items (call it analysis efficiency).
- We want to improve workflow - rank based on how much they speed up the workflow.
- Maybe we need to file some more bugs
- For example...workflow
- find a top crash
- look at the list of reports
- look at individual report
- find top line in the source file
- look at revision history of the source file
- any recent revisions that caused a regression
- you keep going through every line in the source file
- Need a way to correlate a crash signature with revision history.
- Crash spikes
- Another category of alarms and notifications
- Some ideas of algorithms and settings
- Some kind of prototyping with csv reports first.
- bugs on file for all of Chris - integrated report - nightly report - mozilla central trend - rank comparison - plugin
- redesign of Socorro home page
- redesign of admin panel to support multiple
- crash analysis - can we turn this into a script that runs off the csv files
- history timeline for malware crash signatures - log a bug so that Socorro can generate this - crash volume history. Give us a csv and graph - signature over time. any combination of signatures.
- need to have some coherent story put together by the first