Scanner Hardware Database

[Michael Nagel]

This serves as a placeholder to plan the creation of a Scanner Hardware Database.

[Michael Nagel (nailor)]

TODO: write "bug" description
merge irc backlog:

(19:12:39) Michael Nagel: hardware database http://nailor.devzero.de/tmp/scandb/loop/hardware.htm
(19:13:29) Michael Nagel: i have been thinking about this from time to time.
(19:13:45) Michael Nagel: i still think this is a good idea.
(19:14:21) Michael Nagel: your feedback was it should become even simpler.
(19:14:34) robert_ancell: yes
(19:14:53) Michael Nagel: the feedback from skanlite was positive but no active involvement.
(19:16:02) Michael Nagel: the feedback from sane-devel made me fear i could get trapped in a tarpit...
(19:16:11) robert_ancell: heh
(19:16:54) robert_ancell: don't overcomplicate it - any table of positive / negative experiences with each scanner would be useful
(19:17:50) Michael Nagel: my main concerns are that i dont want to do it alone (dont feel qualified to create a public webservice alone (security concerns, ...)) and how/where it could be hosted (cost & legal & whatnot)
(19:17:59) robert_ancell: right
(19:18:51) Michael Nagel: maybe you have some connections in this regard?!
(19:19:40) robert_ancell: unfortunately not in regard of setting up any services. But you could look at https://wiki.ubuntu.com/Testing/Automation/Checkbox and modify that if necessary
(19:19:51) Michael Nagel: what i definitely can and will do is to create a ticket or wiki page to collect information, right now this thing lives in my head and some mails...
(19:22:09) Michael Nagel: hmmm... i will think about this some more.

[Thomas (tz2)]

Hello,
There is already a database: http://www.sane-project.org/sane-mfgs.html

m.f.G.:Thomas131

[Thomas (tz2)]

Sorry, I just saw, that simplescan is not a frontend for sane. Soory.

Thomas131

[Michael Nagel (nailor)]

simplescan *IS* a frontend for sane.

the sane database linked above just lists what should be supported/is supported theoretically, but it is not "full stack". often things break at the kernel/libusb/application-level or with certain combinations of these things.