where to go from here...get the PSF proposal right!

Thanks paul and ray for your comments!

Ray:
It takes an interesting combination of skill sets (javacc, lexer) to
be able to get going on jython development (if we want to understand
how to do the python grammar stuff)

I ask for a roadmap, becuase we were a bit half hearted in our jvm 1.5
integration.

I understand 2.2a works, but our production quality version 2.1 has
issues with it (I know samuel reluctantly compiled a 2.1 jdk1.5
jar....but didn't do anything to the source)

It's hard to get a "alpha" into a production environment at a
financial institution

Product managers at financial institutions don't necessary dislike
OSS, just ones that don't seem active.  This is food for thought...why
do people constantly ask if we're stalled???

We would like to see what the jython leads have to say before we
"jump" in to working on the code.

Paul:

I was hoping that Frank, Sean, Sameul, Oti and gang would have been
able to give some more concrete feed back....they are the leadership
of thiis project no?

If resources are required, I'll see what part my group can play in this....

However it is VERY hard to get a financial institution directly
involved with a OSS that they did not concieve of in the
beginning...I'm not saying that it's impossible though. Contributing
through a vendor for example is something we've done in the past...we
could see if we could get guys from bea or ibm involved.

Frankly I'm surprised why IBM and BEA haven't gotten involved
aready...(jython 2.1 is bundled with their app server product i
think...)

In any case, that's something to worry about after we sort out things
like deliverables, accountablility, metrics, expectation
management...etc...etc...

jython users have queued up an impressive list of requirements, that
should have a timeline, ownership,priority and a delivery date for
this stuff...

I would post on the DEV userlist but that seems to be a bit less
active, and I want to bring these issues to the attention of all
Jython users as well...if you guys feel that I shouldn't be posting
here I'll stop.

The fact remains that we have a PSF grant that we failed to
execute....so money is not the big issue yet (it's always an
issue...even for us :-)

If our original proposal was off, we should correct it and see about
getting a better quote for hours/dev time.

Then publish it and get going...we have a really good product that I
believe is way ahead of the game when compared to groovy, beanshell,
jruby...but for widespread adopment we have a long way to go...

P.S. is 50k even enough to get us to 2.4.2 ?  we should think hard and
long about what 2.4.X means before we say "yes"

Regards,
Walter








--
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