Package: python-soaplib Version: 0.0+svn44-2 Severity: wishlist Hi,
The development of soaplib seems to have forked to GitHub[0]. The original upstream seems to have stopped, the Trac is full of spam and the google groups page[1] (mentioned in the old upstream) has recently been used only by the forked version developer. At some point there was talk about merging the github fork back into the old upstream, but this seems to have been dropped and the github wiki now mentions "The official home for soaplib is now here". I still haven't contacted the forked version's upstream to ask about this status, but wanted to know what you'd think about switching to this new version? If you're in contact with either upstream and think keeping the old version might be a good idea, I'd probably package the new one as python-soaplib-lxml, but if you're ok with the switch, I'd propose co-maintaining python-soaplib, if it's OK with you. The two versions have AFAICT compatible APIs (I used the old for a few weeks and switched to the new a couple of months ago), so switching shouldn't be disruptive to projects using them. This worry is further mitigated by the fact soaplib wasn't in any stable release yet and has no rdepends. Let me know what you think. Cheers [0] http://github.com/jkp/soaplib [1] http://groups.google.com/group/soapliboptio/ -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
