HardwareDatabaseRoadmap

Differences between revisions 9 and 10
⇤ ← Revision 9 as of 2005-04-23 08:11:21 →
Size: 2121
Editor: CPE-60-225-18-37
Comment:
← Revision 10 as of 2005-04-23 09:17:34 → ⇥
Size: 3066
Editor: ppp112-230
Comment: convert to SpecTemplate
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Priority = ##(see the SpecSpec for an explanation)
Line 3: Line 3:
NeedPriorityAssigned = Hardware Database Roadmap =
Line 5: Line 5:
= People = == Status ==
Line 7: Line 7:
 * OliverGrawert   * Created: [[Date(2005-04-23T09:17:34Z)]] by MattZimmerman[[BR]]
  * Priority: NeedsPriority[[BR]]
  * People: OliverGrawertLead, NeedsSecond[[BR]]
  * Contributors: MattZimmerman[[BR]]
  * Interested: [[BR]]
  * Status: BrainDump, UduBof, DistroSpecification[[BR]]
  * Branch: [[BR]]
  * Malone Bug: [[BR]]
  * Packages: [[BR]]
  * Depends: [[BR]]
  * UduSessions: 1, 4, 8, etc [[BR]]
Line 9: Line 19:
= Goal = == Introduction ==
Line 11: Line 21:
Analyze data collected by the Hoary hardware database client, and consider improvements for Breezy. Create a roadmap for the Ubuntu hardware database and related projects
Line 13: Line 23:
= Where are we now =
 * more than 18000 datasets in < 30 days (currently 755 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		 == Rationale ==
Line 21: Line 25:
= Ideas and suggestions = == Scope and Use Cases ==
Line 23: Line 27:
== 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		  * Analyze data collected in the database
 * Import the data into a system suitable for reporting
 * Generate summary reports
  * How well a certain device is supported, and how popular it is
  * What fraction of users are having a good experience with a subsystem (e.g., sound)
Line 30: Line 33:
== 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
 * building a base for ubuntu hardware certification		 == Implementation Plan ==

=== Data Preservation and Migration ===

=== Packages Affected ===

=== User Interface Requirements ===

== Outstanding Issues ==

=== UDU BOF Agenda ===

 * Where are we now?

  * more than 18000 datasets in < 30 days (currently 755 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

 * 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

 * What's 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
  * building a base for ubuntu hardware certification

=== UDU Pre-Work ===

Hardware Database Roadmap

Status

Introduction

Create a roadmap for the Ubuntu hardware database and related projects

Rationale

Scope and Use Cases

  • Analyze data collected in the database
  • Import the data into a system suitable for reporting
  • Generate summary reports
    • How well a certain device is supported, and how popular it is
    • What fraction of users are having a good experience with a subsystem (e.g., sound)

Implementation Plan

Data Preservation and Migration

Packages Affected

User Interface Requirements

Outstanding Issues

UDU BOF Agenda

  • Where are we now?

    • more than 18000 datasets in < 30 days (currently 755 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
  • 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
  • What's 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

    • building a base for ubuntu hardware certification

UDU Pre-Work

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