Summary of Paul's post with some comments

Hi Paul,

I didn't want to butcher your wonderful post so I figured I'd
"summarize" it in my reply :)
Please let me know if I missed anything !

- a grant gives the impression that someone or some group is
commissioned to finish a set of requirements. This can have some
risks, such as questionable level of development ownership and
incorrect expectations.

I think that since we decided to ask for a grant there had to be a
perception that there was going to be a leader or a group that
leads....I understand the possiblity that there could have been
unrealistic expectiations, but I was quite excited when it came out
and was anticipating a big year for jython.  I also made the choice to
use jython in our project as a result.  I think that that initial
"feel good" moment is wearing off, and that if there's anything in
"doubt" in regards to what can be done, what can't be done...what we
will do what we won't....let it be made clear.

- Java is not free (as in open source) (eg. the java trap philosophy)
and is a commercial platform as such it is not unreasonable to allude
that jython may require commercial support.  It could be a expense for
your project...

Yes...the JVM is not OSS...but i think that Jython doen't try to make
assumptions that it would eventually be free either...it fills a niche
that would make for more widespread use of the python language in the
enterprise...it started off as an experiment for academic purpose, i
know, but with the JVM as a key player in the enterprise, the benefits
of using jython become quite apparant...as for support, no one is
saying that jython can't have commercial support...just that there's
no one that can provide it at the moment :)  I often like to think of
jython as an ambassador for python into the enterprise :)

Let's say I did have money to spend...how would I spend it on jython? 
I know I need for it to conform with 2.4....what does it take to get
there?


- this has impact on community support/developer mindset

I guess this could be taken care of if we had some sort of "manifesto"
as to what jython is trying to achieve...what it can do, the
philosiphy...etc etc....

- should we wait for pypy? gaining importance...
well...jython is decendant from jpython...which is python for java no?
 if we were to do that with pypy, shouldn't it be a subproject after
pypy gets mature enough?  That in itself has a whole other set of
problems...
- would this eliminate any maintenance overhead?
either way...it wouldn't be jython anymore would it? it would be
pypy--> java bytecode :)

- jvm compatibilty strategy questions...
this should be made clear by the leadership :)


- 50k may be enough for 1 resource to work to get to 2.4.2 in US (2 or
3 off shore..)
(language spec + XML + threads)

Well...let's make sure that there is money to be gotten from PSF...if
not, perhaps even a paypal sponsership scheme would not be
unreasonable...Do you know resources that would be interested ?? (US
and/or offshore)  That should be disccussed :)

- looking at pypy/antlr seem more fun but more risky than working with
current code base
pypy/antlr does seem more fun...but as you said, it would be risky :)


Please read paul's original reply:
http://sourceforge.net/mailarchive/forum.php?thread_id=10058132&forum_id=5586

it has wonderful insight on what goes through a developers mind when
deciding to use/contribute/volunteer for a OSS project.


--
Simplicity--the art of maximizing the amount
of work not done--is essential.
from: http://www.agilemanifesto.org/principles.html


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642