Hi Marco/List, M> The changelog shows that the isdn part is no more developed since long M> long time, all the patches being made against the vgsm module only. I think this is because Daniele is being sponsored/payed by a company, and AFAIK they are focusing on the vgsm stuff.
M> Hanging without direction this way for so long is not acceptable any M> longer, OMHO, so a decision has to be made. I think so too. I have a couple of unresolved issues (replay-bug etc) which I personally think are _very_ unnerving... M> Would like to know the list opinion on this, and what developing forces M> and competences (and time to dedicate) we have, so we can consider if a M> fork is possible I guess a fork would make sense, but I doubt that the developing competence is high enough/we can find enough active developers. Speaking for myself, I don't have the time nor expertise developing core isdn stuff. As this list is mostly inactive, I guess there are not may active/able developers around. Based on the patches submitted so far, there are only very few people able to cope with the code complexity. M> or if we better go to mISDN instead and leave visdn on M> it's own. Would be certainly a pity, but I see no more options at the M> moment. mISDN is no option for me and all users who are using vISDN with HFC cards in NT mode (internal S0 bus). The only option for this functionality is zapHFC, which is really a crappy piece of software. Regards, Arne _______________________________________________ Visdn-hackers mailing list [email protected] https://mailman.uli.it/mailman/listinfo/visdn-hackers
