Differences between revisions 1 and 9 (spanning 8 versions)
Revision 1 as of 2005-02-04 20:14:25
Size: 3836
Editor: BillDehora
Comment:
Revision 9 as of 2005-02-05 02:14:30
Size: 4379
Editor: BillDehora
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
Anyone interested in helping to move the effort to develop and promote Jython is welcome to get involved in the community. This page will help you get acquainted with how the community works.

=== Meritocracy ===

To paraphrase GuidoVanRossum, Jython is a language, but it's also a community. 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 community goal is to be able to remove the previous sentence from this page.
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.
Line 22: Line 18:

Line 24: Line 22:
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 lager code and documentation and advocacy contributions. When the community feels that the person had earned it, he or she will be granted commit access to the repository. This is the ''meritocracy'' approach, common in OSS development. === Meritocracy ===
Line 26: Line 24:
Ultimately we would like Jython to be self-governing and driven by the people who volunteer for the job. The power will lie with those who turn up and contribute. To paraphrase GuidoVanRossum, Jython is a language, but it's also a community.
Line 28: Line 26:
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.
Line 37: Line 42:
Please join the mailing lists to get involved in the discussion.

We would like to get as much value out of the mailing lists as possible. If you have something worth saying, don't be afraid to say it. But please try to write clearly and concisely.
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.
Line 44: Line 46:
We have bugs - if you can help out, that's fantastic. You can the list of open items on the [http://sourceforge.net/tracker/?group_id=12867 issue tracker]. Currently we're 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. 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.
Line 46: Line 48:
To get started with the code, see the JythonDeveloperGuide.
Line 47: Line 50:
=== Features and JEPs === === Features ===
Line 49: Line 52:
Jython is incomplete, esepcially when compared to recent version of Python. BrianZimmer has outlined a roadmap in MovingPythonForward and there is a list of AbsentModules. If you see some aspect of Jython you want to work, 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 for a JythonExtensionProposal (JEP) here on the wiki (see HowToWriteJeps). Having something concrete to discuss helps everyone.



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.
Line 57: Line 56:
see WhosWho for a glimpse of who is involved with Jython, . see WhosWho for a glimpse of who is involved with Jython.


----
CategoryContribute

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.

The first step is to read BrianZimmer's MovingJythonForward, which has put some much needed impetus into Jython.

You're back? Excellent.

Meritocracy

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

Discussion mainly happens happens on the the following fora, currently hosted at sourceforge:

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.

Features

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.

Who's Involved?

see WhosWho for a glimpse of who is involved with Jython.


CategoryContribute

HowToGetInvolved (last edited 2012-03-14 18:52:15 by AlexGrönholm)