Call for help: SANE
I am currently going through the SANE bugs reported on bugs.d.o. There are quite a few of them, and verifying them already takes a long, long time; fixing them is another story entirely, given I own none of the affected scanners or platforms.
I’ll be going through the bugs this week-end, re-reading the logs, tagging/retitling as needed so hopefully the list will be easier to read.
If you have - or are affected by - an open bug against SANE, please try to reproduce the bug on an up-to-date unstable system. I’ll be uploading a CVS snapshot to unstable today for that purpose.
SANE is a complex piece of software that is best maintained in a team, if only because there’s so much hardware involved that the more maintainers you have, the more different hardware you can have too. If you have a scanner, have some knowledge about USB, shared libraries, GTK among other things and want to help, mail me and tell me what you can/want to do. Some knowledge about SCSI can help too, though SCSI scanners aren’t exactly mainstream anymore.
I currently own only 3 scanners, one old SCSI scanner and a pair of nearly identical USB scanners; so that really makes 2 scanners.
If you have some scanners lying around that you don’t use anymore, I (and the SANE developers too) could probably use them. I’m primarily interested in any scanner that is involved in one of the bugs currently open against SANE. I’m also looking for a scanner supported by the epson backend (the Epson scanners I have are supported by the snapscan backend).
Now, back to these damn bugs.