Re: Summary of Paul's post with some comments

Hi Paul,

Excellent thoughts....I'll try to getting some time this weekend to
answer in full over a nice cup of coffee :)

I think that we are already kicking off some of the items that you
were writing about...
- trying to identify where the roadblocks are
- the development process (the howto's, the what you need to get
started on working on the jython core...etc etc)
- source code management tools (Cruisecontrol, KZ's scripts....)
- communication (talking to other projects for advice...etc)

are all things that we want to leverage where we can.

making jython cool and easy to work on is something that I think alot
of people are trying to do in their own way on the list right now :)

I think that being able to do what our big brother CPython does is a
noble goal...and isn't mutually confliciting with some of the other
things we'd like to see happen (new python language features, abilty
to tap into new jvm features...etc etc)

waterfall (and iterative development) allows the people on the project
to show accountability which is very important to some people who want
to use jython "at work" :)

Even if we decide not to have "dates" at least we should have a
"progess bar" of some sort .

but as always your post reminds us to do some introspection :)

I'll have to think about what I'm doing at this point....is it because
"the needs of my group at work" or because I think that jython is a
good initiative and would like to contribute to it...

For now...I think it's more of the latter...:)

Kind Regards,
Walter

> But obviously it would seem the best place to start is with the people
> already sweating it out to make Jython work, and find out what they want
> to do and what they don't want to do, and what they think they think the
> bottlenecks are.
>
> So to summarize, from a stigmergic point of view for investment strategy
> by an open source project manager, you may want to target investments to
> supporting a stigmergic coding process, and that doesn't necessarily mean
> paying for coding but rather removing roadblocks to letting the process
> happen. Or to quote AA Milne through Winnie the Pooh: "Because Poetry  and
>   Hums aren't things which you get, they're things which get you. And all
> you can do is to go where they can find you."
>
> Obviously though, if your only goal for Jython was to track CPython
> (including, say, getting twisted to work out of the box), then one can
> just use a generic waterfall development model and some hired hands, and
> that may be all your group may think it wants. :-) And I can't say that
> would not just by itself be a very nice thing.
>
> Anyway, just some more thoughts. :-)
>
> --Paul Fernhout
>
>
>
> -------------------------------------------------------
> 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?cmdlnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Jython-users mailing list
> Jython-users@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/jython-users
>


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