On 5/18/07, Jeff Rush <jeff@...> wrote:
> Time is short and I'm still looking for answers to some questions about
> Jython, so that it makes a good showing in the Forrester survey.
> 1) How is the project governed? How does the community make decisions on what
> goes into a release?
Jython is very closely related to Python, and takes many of its
behavior from that project -- which is governed by a BDFL (Benevolant
Dictator for Life). Jython does not really have anyone with quite the
longevity to be considered a BDFL, but sort of takes a BDFW
(Benevolent Dictator for a While) kind of approach. When a BDFW moves
on, that person leaves someone else as the next BDFW. I've been that
BDFW for a little over two years. Of course since I haven't been
around from the beginning, I do not command anything like the moral
authority that Guido has over Python, and in fact I would say that, in
many respects the true final word on Jython is Guido's since Jython is
just another implementation of Python. Like any other open source
project, the developers can always take the code and start their own
project if they don't like how things are going here -- so the
"Dictator" stuff has to be pretty light handed.
> 2) How many committers to the Jython source are there?
I believe 16 are listed on the sourceforge project site, but the true
number of active committers is around 5.
> 3) Does Jython have a formal defined release plan? Every 6-months? Whenever
> it feels right?
Jython does not have a formal release plan. Jython is about to put
out its first real release in many years. After that we will try to
get something more predictable going. Having said that, "whenever it
feels right" is probably the fact of the matter for a while to come.
> 4) Some crude idea of how many new major and minor features were added in the
> last release? This is to give some idea of its current rate of
> evolution/stability in features.
This is difficult to say. The really big change is that Jython now
supports the Python 2.2 "new style classes" this is an enormous change
to the codebase, and is the primary reason that the 2.2 release has
taken so long.