I think quite a few people have patches, just needs a currently active developer to volunteer to keep them all at one single place - or better still make a wiki page for patches.

Also have you guys considered moving the project to www.codehaus.org - several scripting languages are there and the development environmnent/toolset is great - let me know if your intersted.

Automated builds with damage control - http://builds.codehaus.org/public/dashboard
Wiki - http://docs.codehaus.org
Automatic documentation publishing of wiki contents - http://drools.org/ is from http://docs.codehaus.org/display/DROOLS
Source control with CVS/Subversion
CVS view with Fish Eye- http://cvs.drools.codehaus.org/viewrep/drools/
Issue Tracking with Jira - http://jira.codehaus.org
Blogs with Movable Type- http://blogs.codehaus.org/
Web IRC gateway - http://irc.codehaus.org/


Jeremy Hylton wrote:
On Mon, 11 Oct 2004 18:05:30 +0100, Sean McGrath
<sean.mcgrath@propylon.com> wrote:
What needs to be done to get development of Jython re-energised? Count
me in to help out but I fear we need to act fast lest this golden
opportunity pass us by.

What need to be done to get Jython development re-energised? Are we
stuck for some reason? If so, how best to get unstuck?

The best way to unstick it is for some developers to volunteer their
time.  Start submitting patches.  If they don't get accepted, start
complaining to the project admins and ask them to make you a
developer.  If several people take this tack, they can revive the