<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This is how we suck you in... ;)</blockquote><div><br>I see :-). Funny I didn't see this procedure mentioned in the patch submission guidelines ;-)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You don't have to be an expert to review patches. The following<br>procedure would qualify you:
<br><br>1. Find a patch that it appears no one has ever touched (0 comments,<br>assigned to nobody, etc.)<br><br>2. Pretty much every patch should include a unit test and<br>documentation. If something is missing from the patch you're looking
<br>at, post a comment that says "Incomplete, no docs/tests".</blockquote><div><br>My own patch does not include documentation. I assume documentation would only be needed for patches that add new functionality (as opposed to fixing problems)?
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3. Repeat until you've commented on five patches.<br><br>If you find such clerical work beneath you, you can go further--build
<br>Python from source, apply patches, and verify that they work. It's<br>not hard (google "python developer faq"). But it's not required.<br></blockquote></div><br>I might try to do this, as time permits.
<br><br>Regards,<br>Miguel<br><br>