Priority

NeedPriorityAssigned

People

• OliverGrawert

Goal

Analyze data collected by the Hoary hardware database client, and consider improvements for Breezy.

Where are we now

• more than 16000 datasets in < 30 days (currently 763 submissions a day on average)

• collecting device and bios data, as well as xorg log/config and boot data
• client points you to your online record on the second run
• postgres server solution is in the works
• no inclusion of the client in reportbug yet (automated inclusion of the hwdb ID in bugreports)
• client needs improvement to have the full feature set I planned

Ideas and suggestions

What can we do with the current data

• 1st usecase is a online device manager with log viewer
• getting hardware statistics and detailed reports
• determining the quality of our current hardware support
• find good/bad supported HW to improve the situation
• loads of statistics are possible

Whats the future ?

• fixing the remaining bugs in the client indeed
• rearrange the untranslateable parts of the code to be translatable and put a .po file in rosetta
• additional automated test sets
• checking for second network, sound and video card
• client-side update functionality for the dataset
• make the client configurable, so it can send to a local server instead
• make a local server package for integration in standalone intranet helpdesk systems
• pull more kernel information/module data and settings (use hal's defined but unused module options)
• invent some server security to prevent us from being slashdotted by marketing companies that might try to hook up scripts to our data
• get more patches into the upstream hal version (easier with the new hal 0.5), to make hwdb-client usable in debian too (we get some malformed datasets from crossgraders with the wrong hal version but don't want to tighten the dependencies)

• a new rocking "breezy" GUI design so the user cant resist playing with it and just must submit