Recently I have been doing a bit of work on libcsoap (the C library for making SOAP XML calls over http) and the libnanohttp library that it depends on. The most important part of my work on it was making it thread-safe with the technique I described in my post about finding thread unsafe code [1]. But I also did some work to make the code faster, reading data one byte at a time is very inefficient.

There has been no upstream release of this software for years, email to one of the maintainers bounced and the other one indicated that they are no longer involved in the project. So I’m thinking of taking over upstream development.

The previous Debian maintainer for the packages in question has recently resigned so I’ve taken over the packaging. But for this one I think I can do better work in an upstream capacity, so I’d like to get a co-maintainer for the Debian package and possibly someone who will help with upstream work. I would appreciate any offers of assistance with these things.

• [1] http://etbe.coker.com.au/2009/06/14/finding-thread-unsafe-code/

Related posts:

1. DomainKeys and OpenSSL have Defeated Me I have previously written about an error that valgrind reported...
2. Debian Work and Upstream Steve Kemp writes about security issues with C programs [1]....
3. Finding Thread-unsafe Code One problem that I have had on a number of...
4. SE Linux in other Distributions Recently a user has been asking about SE Linux support...
5. Comparing Debian and Fedora A common question is how to compare Fedora [1] and...