[Python-Dev] Contributing to Python (original) (raw)

Facundo Batista facundobatista at gmail.com
Fri Jan 4 13:34:22 CET 2008

2008/1/3, Titus Brown <titus at caltech.edu>:

The question is, is reviewing patches a good place to contribute? Also, if I (and others) could have a "core mentor" with commit access, that might streamline things. As it is, I am worried that patch reviews will

For a core_mentor/padawan (wink) relationship to work ok, you need that both parties get interested on working on the same stuff.

For example, Mark has been working a lot on Decimal, and I have been a merely supervisor and committer of his changes, and we could generate successfully a good patch flow.

I don't think that this can be successful when both parties tries to handle wide portions of Python, but I'd love to see a lot of this small sparks of productivity.

Now thinking of how to produce this relationships, I think that I will change my approach to the issues. I'll start to be more aggressive when reviewing a patch or bug. Aggressive in the sense of asking/commenting/proposing even if I don't get the full grasp of the issue. This could lead to a better interaction on the mid/long term, even if in the short it appears to increase the noise a little.

-- . Facundo

Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/

More information about the Python-Dev mailing list