Statement on XPathScript

[Matt Sergeant]

OK, there's lots of posts flying about, so I think it's worth clearing this up into one place under a new thread.

For a start, let me say emphatically that XPathScript isn't going away - for anyone using it right now it will still be there in AxKit in the future.

As far as downplaying XPathScript, well if that's how the community wants to play things then we can follow that notion. But it's a documentation issue, and as such it's going to require VOLUNTEERS. This is a free software project and our time is limited (I do this only when my wife isn't looking ;-), and documentation is always the last thing to get written or fixed. Seriously though - I have put an enormous amount of work into this project as have other developers, and we don't get much back from it...

So if you want to help fix the docs the worst thing you can do for this project is to moan about it to us. The axkit core developers want to hear these things in order of preference:

1. "I want to help out any way I can, what can I do?"
2. "Here's a patch"
3. "Everything works great, thanks!"
4. "Here's a bug report" (on http://rt.cpan.org/, thanks)

I hope this gets the message across ;-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]