[Hwdb-devel] Re: [andrelop@debian.org: Re: Official support/certification by hardware vendors]

[Arnaud Quette]

Hi Roland,

I'm a core upstream developer in the major UPS
support project, called NUT - Network UPS Tools [1].

I'm also a DD, and a person who like to standardise
things and help to improve opensource to give its best.

The HWDB is an interesting notion, but I think this
should be a shared effort between Debian, other
distros, upstream projects and opensource users.
On such not trivial subject, make our own effort
would lead in a pure waste of effort.

I'm sure that there is a need to formalise things,
and maybe to create or join a wider GNU/Linux
Hardware Compatibility effort.

While waiting for the above discussion, here are few
remarks and ideas (feel free to go on):

1)  thanks to add me <aquette> to the CVS
and to subscribe me to the list.

2) debian/README:

    - add an explicit reference to the hwdb URL
    ie: "* Point your prefered browser at http://localhost/hwdb/ to
    access Debian HWDB"

    - add in Related Links the following references (to be
    completed with _all_ existing HWDB efforts)
    * "Network UPS Tools (UPS support):
    http://eu1.networkupstools.org/compat/"
    Note that the source file of this HWDB is available
    in NUT Debian packages [2].
    * "LinuxPrinting.org (Printer support):
     http://www.linuxprinting.org/printer_list.cgi"
    * "Linux USB devices overview:
    http://qbik.ch/usb/devices/"


3) HWDB itself:

    - replace the Driver notion by a Software one,
    or link the Driver to a Software (or package).
    ie linux/hid, nut/newhidups, sane/epson, ...

    - add version to Driver and software

    - add support level for Devices, such as in Mdk [3]
     with the same kind of levels.

    - add support level for Manufacturers (ie no support,
    good support, excellent support, ...) and detail the
    requirement for each.

    - Report:

    * a DD signed report gives a "tested" level
    * need to create TestCase, containing scripts
    that automates and proof the report
 
    - automated list updates from upstream: having
    driver.list (such as in nut [2] in each packages
    that should provide hw support would be a good
    thing.

    - merge all existing effort, as sub part of the project,
    to involve existing people.

I've some more, but I need to clarify some ideas in
my mind. While waiting, I hope the above will have
a positive echo.

See you,
Arnaud
---
[1] http://eu1.networkupstools.org/
[2] nut: /usr/share/doc/nut/docs/driver.list.gz
[4] http://www.mandrakelinux.com/fr/hardware.php3