Hi All,

I'm considering forking the libxml project. Once again I can't get a
hold of Sean Chittenden. So we can't get any new developers on the
project with commit rights. No one, as far as I know, is actively
patching. And no one is at the helm.

I am not a C coder, so really I'm not the best man for the job. But I
am willing to coordinate and do everything I am able for the project.
I really need a good, fast xml library for Ruby, and AFAIK bindings to
libxml are the best choice. Unfortunately there are some serious
issues with the current bindings --memory leaks and speed issues (I've
seen libxml run slower than rexml, which really threw me for a loop).
So I want to do something...

So if you all agree, that a fork is a good idea, the question arises:
would we be better off starting from scratch? (We can use some of the
old code piecemeal as proves useful, of course.)  If so, who wants to
take up that challenge?

T.
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel

Reply via email to