Re: Beyond wait-and-see

Samuele Pedroni wrote:
>would (more) people consider contributing code?

Not sure what kind of a data point I am because I've already been bugging
the list with patches, but it would certainly be easier if there were other
progress, particularly as thoughtful responses to patches.

>how much: too/otherwise busy VS. what is there is good enough for what I 
>need VS. the code base is too unwelcoming VS. the project admin does not 
>tutor/inspire/give the good example, play a role OTOH?

I think the most important thing that the project needs is a detailed plan
drawn up on the list for dealing with the major steps needed to move the
project forward.  It's particularly disheartening to know that some portion
of the code base is up for radical change and that patches against it might
be useless.

I think it would be great for people to see a brain-dump from people long
on the project about the issues surrounding new-style types, for which the
closest thing to a visible design discussion that I could find was on
python-dev (note the date): 

  http://mail.python.org/pipermail/python-dev/2001-August/017255.html

In short, I don't think the code is opaque, I'm just not sure where people
want it to go.

I would love to help with new-style classes and such, but it seems that
replacing jythonc is the most-avoided open task, so I'm looking into that
now -- partially because I haven't seen inklings of a plan for that,
whereas I'm guessing people have thought longer and harder about the issues
surrounding new-style classes.

  -r


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click