How about using something like bazaar (http://www.bazaar-vcs.org) to start a branch off the anonymous CVS/SVN head and then whoever has patches can put them on a website (hosting the whole branch). If Trans wants to coordinate pulling in the patches from the other branches and hosting them, then maybe that'd work.
I think people should use whatever SCM they like, but RubyForge is critical for this reason:
gem install libxmlSo in my opinion, RubyForge has to be the hub of the project (in addition, its where people would expect to find the official source code).
Unfortunately, my C is quite rusty, and I'm not in the position to hack on the code myself at the moment, but I'm sure there are those on the list who are. Once they have a way to track their changes, it seems like that's all that's standing in the way of moving the project forward.
Yup, a source repository is the main thing. Failing test cases are also very important...can anyone come up with some?On the bright side, there is a patch from OpenStreetMap that reportedly fixes the memory issues, so this might turn out to be easy. And even if the patch isn't perfect, hopefully it will show the way forward.
Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
