Thanks! That sounds like a nice, clear path forward. Regarding the doc issues being a bit more problematic to work through, I thoroughly understand.
Davin On Jan 8, 2015, at 21:19, R. David Murray <rdmur...@bitdance.com> wrote: > On Thu, 08 Jan 2015 17:08:07 -0800, Ethan Furman <et...@stoneleaf.us> wrote: >> On 01/08/2015 03:21 PM, Davin Potts wrote: >>> >>> I am interested in making some serious ongoing contributions around >>> multiprocessing. >> >> Great! >> >>> Rather than me simply walking through that backlog, offering comments or >>> encouragement here and there on issues, it >>> makes more sense for me to ask: what is the right way for me to proceed? >>> What is the next step towards me helping >>> triage issues? Is there a bridge-keeper with at least three, no more than >>> five questions for me? >> >> I would suggest having at least one, if not two or three, current core-devs >> ready and willing to quickly review your >> work (I believe Raymond Hettinger may be one); then, go ahead and triage, >> improve and/or submit patches, and make >> comments. Once you've got a few of these under your belt, with favorable >> reviews and your patches committed, you may >> get stuck with commit privileges of your own. ;) > > Indeed, the best way to proceed, regardless of any other issues, is in > fact to review, triage, comment on, and improve the issues you are > interested in. Get the patches commit ready, and then get a current > core dev to do a commit review. > > Oddly, the doc issues may be more problematic than the code issues. > Fixing bugs in docs isn't difficult to get done, but restructuring > documentation sometimes gets bogged down in differing opinions. (I > haven't myself looked at your proposals since I don't use > multiprocessing, so I don't know how radical the proposed changes are). > > --David > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/python%2Bpython_dev%40discontinuity.net _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
