|Deletions are marked like this.||Additions are marked like this.|
|Line 16:||Line 16:|
How do I get involved in the Jython community?
Anyone interested in helping to develop and promote Jython is welcome to get involved. This page will help you get acquainted with how things work.
You're back? Excellent.
To paraphrase GuidoVanRossum, Jython is a language, but it's also a community.
Here's where we're at. Currently Jython is managed by the committers to the sourceforge project notably SamuelePedroni, BrianZimmer, KevinButler and SeanMcGrath. A number of people like JimHugunin, FinnBock, BarryWarsaw and SamuelePedroni have committed significantly to the Jython and even though things have been static, Jython is regarded as a stable language fit for production use.
Over time people have been attracted to help out on Jython. Often this happens first by sending little patches, or suggestions, or helping users on the lists, later by larger code, documentation and advocacy contributions. Now it’s clear more people want to work on Jython.
We're well aware that Jython progress has been static over the last few years - we want to fix that and we will need help from others to do so. An immediate goal is to be able to remove that sentence from this page.
The intention is that when the committers and the community feels that the person had earned it, he or she will be granted commit access to the repository and the website. The intention is to bootstrap the meritocracy approach, common in OSS development and expand the number of active participants. Ultimately Jython will be driven by the people who volunteer for the job - responsibility will lie with those who turn up and contribute.
Discussion mainly happens happens on the the following fora, currently hosted at sourceforge:
jython-users: Discussion of and questions about using Jython; most folks will want this one [http://sourceforge.net/mailarchive/forum.php?forum_id=5586 archive] [http://lists.sourceforge.net/mailman/listinfo/jython-users join]
jython-dev: Discussion of developing and enhancing Jython itself(!) (not how to use Jython) [http://sourceforge.net/mailarchive/forum.php?forum_id=5587 archive] [http://lists.sourceforge.net/mailman/listinfo/jython-dev join]
Please join the mailing lists to get involved. Communication on the mailing lists is important, so if you have something to say, say it, but please try to say it clearly and concisely, and follow netiquette.
Bugs, Bugs, Bugs
We have bugs - if you can help out, that's fantastic. You can see the list of open items on the [http://sourceforge.net/tracker/?group_id=12867 issue tracker]. We're planning going through the list to prioritize them - and once NewStyleClasses are introduced you can expect this list to change. But if you see something you want to fix, take a leap - join the jython-dev list and tell the community what you're going to do. Patches are welcomed and should be sent to jython-dev.
To get started with the code, see the JythonDeveloperGuide.
Jython is incomplete, esepcially when compared to recent version of Python. BrianZimmer has outlined what needs to be done MovingJythonForward. There is a RoadMap and a list of AbsentModules . If there is some aspect of Jython you want to work on, the best thing to do is float the idea on jython-dev, if only to see if anyone else is working on or wants to work that area. Don't be too put off if the discussion doesn't go the way you want or expect; the next step is always to write up a concrete proposal here on the wiki as a JythonExtensionProposal (JEP) (see JepGuidelines). Having something concrete to discuss helps everyone.
see WhosWho for a glimpse of who is involved with Jython.