Curiously, I got contacted (out of the blue) by a ZapMicro field-sales
rep who found the DebianBug thread in Google Groups and assumed I was
having trouble. I replied back about our efforts to get some type of
integration for the driver going but haven't got anything back yet.
I'd vouch for doing #3 but you'll have to define "timely" for me (when's
the next release?). I think when I get my base PBX (for this particular
card) out I won't have any trouble keeping up my end of that. If it
would break in the future, and we can't fix it, and ZapMicro doesn't
update their upstream code or respond back specifically to such problems
- then it'd be dropped like it should. Oh well. It would still exist in
an old version for anybody that has to get the card going in the future.
You'd know how (non)volatile the Zaptel code is, I just use the stuff.
I'm not very able to guess how much of a liability including this driver
would be.
Contacted [EMAIL PROTECTED] , which is the address listed on the
driver. I only got a boilerplate response. I asked them a technical
question and am yet to get an answer.
I do not think it is proper to add a driver that nither of us can
maintain and fix. If you want to get the driver inside, I see three
options:
1. Make it get into Zaptel.
2. (Failing 1) - Get ZapMicro to be able to answer technical questions
and provide timely response to technical issues.
3. (Failing 1 and 2) - if someone with their hardware is willing to at
least test fixes on the driver in a timely manner (before packages are
released), and hopefully also some opinions on fixes.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
