HardwareDatabaseRoadmap
Revision 3 as of 2005-04-20 23:47:05
Clear message
Priority
People
Goal
Analyze data collected by the Hoary hardware database client, and consider improvements for Breezy.
Where are we now
more then 16000 datasets in < 30 days (currently 763 submissions a day in average)
- collecting device and bios data, as well as xorg log/config and boot data
- client points you to your online record on 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 a lot of improvement to have the full featureset i planned
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 ?
- more automated tests
- checking for second network-, sound- and videocard
- update functionallity for the dataset
- make the client configurable, so it can send to a local server instead
- make a own server package for integration in intranet helpdesk systems
- pull more kernel information/module data and settings
- invent some server security to prevent us from being slashdotted by marketing companys that might want to hook up to our data
- get more patches into the upstream hal version (easier with hal 0.5), to make hwdb-client usable in debian too (we get some malformed datasets from crossgraders with the wrong hal version)