HardwareDatabaseRoadmap

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2005-04-21 00:10:52 →
Size: 1950
Editor: CPE-60-225-18-37
Comment:
← Revision 5 as of 2005-04-21 00:46:28 → ⇥
Size: 1954
Editor: 150
Comment: typo etc. fixes
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
 * more then 16000 datasets in < 30 days (currently 763 submissions a day in average)  * more than 16000 datasets in < 30 days (currently 763 submissions a day on average)
Line 19: Line 19:
 * client needs improvement to have the full featureset i planned  * client needs improvement to have the full feature set I planned
Line 33: Line 33:
 * checking for second network-, sound- and videocard
 * client sided update functionality for the dataset		  * checking for second network, sound and video card
 * client-side update functionality for the dataset
Line 36: Line 36:
 * make a own server package for integration in standalone intranet helpdesk systems  * make a local server package for integration in standalone intranet helpdesk systems
Line 38: Line 38:
 * invent some server security to prevent us from being slashdotted by marketing companys 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 dont want to tighten the dependencys)		  * 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)

Priority

NeedPriorityAssigned

People

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
  • 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 so the user cant resist playing with it and must submit

UbuntuDownUnder/BOFs/HardwareDatabaseRoadmap (last edited 2008-08-06 16:34:36 by localhost)